| FMRS | 62 / 100 · C | 80 / 100 · B | 79 / 100 · B |
|---|
| Reliability | 8 / 20 | 14 / 20 | 12 / 20 |
|---|
| Security and permissions | 12 / 20 | 16 / 20 | 16 / 20 |
|---|
| Maintenance | 13 / 20 | 17 / 20 | 18 / 20 |
|---|
| Documentation | 16 / 20 | 15 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 18 / 20 | 15 / 20 |
|---|
| Best for | - Developers and teams that need a unified, secure entry point in front of many MCP servers
- Security-conscious users worried about Tool Poisoning Attacks who want new servers quarantined by default
- AI agent users limited by context windows or client tool caps who want large token savings
| - Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
- Scenarios wanting zero-config documentation lookup
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| Not for | - Users who want a fully cloud-hosted setup and will not run a local proxy
- Lightweight setups connecting only one or two simple MCP servers where discovery, quarantine and auditing add no value
- Environments where running a Go binary or local service is not possible
| - Looking up internal/private codebase documentation (Context7 targets publicly published open-source libraries)
- Cases needing very high coverage of obscure, niche libraries (coverage depends on what Context7's platform has indexed)
| - Projects outside the NPM ecosystem (e.g., pure Python/Go)
- Environments without network access to deps.dev, OSV.dev, and the npm registry
- Scenarios requiring maintenance by an official upstream vendor
|
|---|
| Required permissions | - Read and write the local config directory ~/.mcpproxy/ (mcp_config.json, certificates, activity logs)
- Listen on a local HTTP port (127.0.0.1:8080 by default)
- Spawn local stdio upstream MCP servers using the commands in your configuration
- Connect to remote HTTP upstream servers as configured, potentially including OAuth login
- If HTTPS is enabled, add a self-signed CA certificate to the system keychain via mcpproxy trust-cert
- If third-party scanners are enabled, a working Docker environment is required
| - Usable without an API key (subject to a free-tier rate limit); CONTEXT7_API_KEY is an optional credential for higher quota
- Read-only documentation lookup — no code execution or local filesystem access involved
| - Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
- Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
|
|---|
| Risks and side effects | - The proxy becomes the single channel for all upstream tools, so a misconfiguration could expose tools the agent should not reach
- The proxy inspects tool arguments and responses for sensitive data, and sensitive content may end up in the local activity log
- Quarantine blocks new servers, but an already-approved server that later changes still requires re-approval (the README notes tool changes trigger blocking)
- Spawning stdio upstreams means the proxy can execute the commands in your config, so the config source must be trusted
- HTTPS uses self-signed certificates that must be manually trusted, otherwise clients fail to connect
| - The free tier has limited quota — high-frequency use may hit rate limits
- Documentation content comes from Context7's platform index, so its accuracy and freshness depend on that platform's crawl cadence
| - Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
- Depends on availability and accuracy of external services
- Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
- Third-party open source project, not officially maintained by NPM or Anthropic
|
|---|
| Supported clients | Cursor, Claude Desktop, VS Code, Goose | Claude Code, VS Code, Cursor, Cline, Amp | Claude Desktop, VS Code, Cursor, Smithery.ai |
|---|
| Tools | 5 | 2 | 19 |
|---|