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.

DimensionMCP HubA central coordinator for managing multiple MCP servers behind one unified endpointMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS63 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions9 / 2018 / 20
Maintenance14 / 2016 / 20
Documentation16 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Developers orchestrating several MCP servers at once
  • Users who want a single endpoint configured in their MCP clients
  • Automation that needs live status and capability-change notifications
  • 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 who only need one simple MCP server and no middle layer
  • Clients requiring Roots, Sampling or Completion capabilities (not supported)
  • Environments without Node.js 18+
  • 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
  • Read and parse the specified JSON configuration files
  • Execute local commands through ${cmd:} placeholders while resolving configuration
  • Inject MCP_HUB_ENV and per-server env variables into managed child processes
  • Spawn stdio child processes using the configured command/args
  • Make network requests to configured remote URLs with custom auth headers
  • Write log and workspace cache files under the XDG state directory
  • 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
  • ${cmd: command args} executes arbitrary local commands during config resolution, which is risky if the config is tampered with
  • Starting local stdio servers is equivalent to running arbitrary commands with your user privileges
  • MCP_HUB_ENV and server env values may hold secrets that can leak if configs or logs are readable by others
  • Remote server credentials (OAuth, Bearer tokens) must be stored securely
  • Misconfigured --auto-shutdown can terminate the hub unexpectedly
  • 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, Cline, NeovimClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00