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 savingsNPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS62 / 100 · C79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions12 / 2016 / 20
Maintenance13 / 2018 / 20
Documentation16 / 2018 / 20
Setup experience13 / 2015 / 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 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
  • 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
  • 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
  • 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 clientsCursor, Claude Desktop, VS Code, GooseClaude Desktop, VS Code, Cursor
Tools519