io.github.kira-autonoma/context-proxy

MCPcommunity
v0.2.0io.github.kira-autonomaUnknownUpdated 6mo agonpmGitHub

MCP proxy that lazy-loads tool schemas to cut context token overhead by 6-7x

Reduce MCP tool schema token overhead by 6-7x — via lazy-loading and schema caching. Verified, not claimed. Every session writes a proof log to . Run to see your actual savings, not marketing estimates. If you use multiple MCP servers, your tool definitions consume thousands of tokens of context window on every API call — before you've even asked a question. With 10 servers × 10 tools × ~344…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
6mo agoLast update
Package
Authorio.github.kira-autonoma
LicenseUnknown
Version0.2.0
Sourcemcp-registry
npmmcp-lazy-proxy
GitHubkira-autonoma/mcp-context-proxy
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ 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>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
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 surface—
Security scan✓ Cleanv0.2.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 16 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Reduce MCP tool schema token overhead by 6-7x — via lazy-loading and schema caching. Verified, not claimed. Every session writes a proof log to . Run to see your actual savings, not marketing estimates. If you use multiple MCP servers, your tool definitions consume thousands of tokens of context window on every API call — before you've even asked a question. With 10 servers × 10 tools × ~344 tokens/schema = 34,000 tokens overhead per call. At $3/MTok (Claude Sonnet): $0.10 wasted per call, or…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.