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 InterviewerCatch MCP server issues before your agents do.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS52 / 100 · D79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions8 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience11 / 2015 / 20
Best for
  • Developers who want to catch MCP server configuration and constraint problems before deployment
  • Teams that need MCP server quality checks in CI/CD
  • Researchers willing to run the tested server isolated in a container and manually inspect the output
  • 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 want to run arbitrary server commands in production without isolation
  • Users expecting fully validated, commercially ready conclusions
  • Users unwilling to set up container isolation or an LLM model client
  • 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 the MCP server command you provide (run in a child process; the MCP Python SDK executes arbitrary commands on the host)
  • Calls the server's tools when functional testing (--test) is enabled
  • Reaches the specified OpenAI-compatible API (possibly a local Ollama endpoint) when LLM features are used
  • 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 tested server command runs on the host; without container isolation it can endanger the host system, sensitive data, or files
  • Enabling --test actually invokes server tools and may cause unintended side effects
  • A server may carry malicious or misleading tool metadata that produces inaccurate MCP Interviewer output
  • LLM-generated test plans and evaluations can contain errors; the documentation says all LLM evaluations should be manually inspected
  • The tool is research and experimental in nature and has not been fully tested and validated
  • 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