On-demand tool discovery for all your MCPs and per-subagent MCP controls to preserve context window.
A Model Context Protocol (MCP) gateway that aggregates multiple MCP servers and provides policy-based access control for agents and subagents. Solves Claude Code's MCP context window waste by enabling on-demand tool discovery instead of loading all tool definitions upfront. ✅ M0: Foundation - Configuration, policy engine, audit logging, tool ✅ M1: Core - Proxy infrastructure, , , middleware,…
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”.
A Model Context Protocol (MCP) gateway that aggregates multiple MCP servers and provides policy-based access control for agents and subagents. Solves Claude Code's MCP context window waste by enabling on-demand tool discovery instead of loading all tool definitions upfront. ✅ M0: Foundation - Configuration, policy engine, audit logging, tool ✅ M1: Core - Proxy infrastructure, , , middleware, metrics, hot reload, OAuth support 🚧 M2: Production - HTTP transport, health checks (planned) 🚧 M3: DX…
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.