M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionMCPProxyLocal-first MCP proxy with BM25 tool discovery, security scanning, quarantine & ~99% token savingsContext7Upstash's official server providing up-to-date third-party library docs for AI coding assistants
FMRS62 / 100 · C80 / 100 · B
Reliability8 / 2014 / 20
Security and permissions12 / 2016 / 20
Maintenance13 / 2017 / 20
Documentation16 / 2015 / 20
Setup experience13 / 2018 / 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
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)
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
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
Supported clientsCursor, Claude Desktop, VS Code, GooseClaude Code, VS Code, Cursor, Cline, Amp
Tools52