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.

DimensionSupergatewayRun MCP stdio servers over SSE or WebSocket with one command.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS63 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions10 / 2018 / 20
Maintenance14 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Developers who need to expose stdio MCP servers to web or remote clients.
  • Users who want to integrate remote MCP servers into local CLI tools or desktop apps like Claude Desktop or Cursor.
  • Users who want to quickly deploy an MCP proxy via Docker.
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Users looking for MCP server management features (e.g., monitoring, auditing).
  • Users expecting zero configuration; they need to understand and set transport parameters.
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Executes arbitrary commands (via --stdio argument).
  • Network access: can listen on ports (--port) and connect to remote URLs.
  • May read and write file systems (depending on the proxied MCP server).
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • Using --stdio to run arbitrary commands can be a security risk if the command source is untrusted.
  • Exposing an MCP server to the network without authentication (e.g., using --header or --oauth2Bearer) may allow unauthorized access.
  • Sensitive information (e.g., tokens) in configuration files may be exposed.
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude Desktop, CursorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00