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 InspectorVisual testing tool for MCP serversMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS73 / 100 · B79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions15 / 2018 / 20
Maintenance17 / 2016 / 20
Documentation18 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Engineers building or maintaining an MCP server who need to verify protocol behavior
  • Teams that want automated regression checks of an MCP server in CI
  • Advanced users debugging low-level request/response details, such as custom headers or error codes
  • 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
  • End users who just want to chat with an AI assistant and don't care about the underlying protocol
  • Teams wanting a hosted, zero-setup inspection service (it must be run locally or self-hosted)
  • Anyone looking for an MCP server that provides business-facing tools to an AI client — Inspector is itself a client/testing tool, not a callable tool server
  • 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
  • Runs Node.js and may spawn a target MCP server as a subprocess when using stdio transport
  • Makes outbound network connections to reach MCP servers over streamable-HTTP
  • In Web mode, binds a local port (default 6274) and runs a backend capable of spawning processes
  • Reads and writes local configuration files (e.g. `--config`/`--catalog` JSON)
  • 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
  • The Web backend can spawn processes; setting `DANGEROUSLY_BIND_ALL_INTERFACES=true` exposes it to the local network, so pair it with an auth token
  • Setting `DANGEROUSLY_OMIT_AUTH=true` disables authentication and should only be used in fully trusted environments
  • When pointed at an untrusted or malicious MCP server, its responses are proxied and displayed as-is, so the trustworthiness of the server under inspection matters
  • 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 Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00