MCP gateway: bounded tool shortlists + artifact-backed result firewall. Deterministic, no model.
The MCP context gateway for tool-heavy agents. Drop contextweaver in front of your MCP servers and the model sees a bounded shortlist instead of every tool schema, plus an artifact-backed firewall that swaps a huge raw tool result for a compact summary. Deterministic, no model in the loop, and 42-84 % fewer prompt tokens on the committed benchmarks. Who it's for: anyone whose agent — Claude…
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.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 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”.
The MCP context gateway for tool-heavy agents. Drop contextweaver in front of your MCP servers and the model sees a bounded shortlist instead of every tool schema, plus an artifact-backed firewall that swaps a huge raw tool result for a compact summary. Deterministic, no model in the loop, and 42-84 % fewer prompt tokens on the committed benchmarks. Who it's for: anyone whose agent — Claude Desktop, Cursor, VS Code, or a custom loop — keeps tripping over "too many tools" or "a 16 KB tool result…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.