io.github.steveweltman/4q-tokenz

MCPcommunity
v1.14.1io.github.steveweltmanUnknownUpdated 1mo agonpmGitHub

Intelligent MCP proxy that reduces token usage by exposing only mcp_search and mcp_call.

A context-aware MCP proxy that reduces token usage by exposing only 3 tools (, , ) to LLMs instead of the full catalog. When you connect multiple MCP servers to an LLM, every tool from every server is listed in the LLM's context window. For a typical workspace with 50-100 tools across multiple MCP servers, that's thousands of tokens of schema documentation on every request. MCP Proxy Gateway sits…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.steveweltman
LicenseUnknown
Version1.14.1
Sourcemcp-registry
npm4q-tokenz
GitHubsteveweltman/4q-tokens
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface3 tools · none privileged
Security scan✓ Cleanv1.19.0 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

A context-aware MCP proxy that reduces token usage by exposing only 3 tools (, , ) to LLMs instead of the full catalog. When you connect multiple MCP servers to an LLM, every tool from every server is listed in the LLM's context window. For a typical workspace with 50-100 tools across multiple MCP servers, that's thousands of tokens of schema documentation on every request. MCP Proxy Gateway sits between your LLM and your MCP servers, offering: JIT tool loading — tools from upstream servers are…

Keywords
mcp