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.

DimensionPare TestTest runner MCP server that auto-detects test frameworks (pytest, jest, vitest, mocha) and returns typed JSON.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS30 / 100 · D79 / 100 · B
Reliability3 / 2012 / 20
Security and permissions5 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation5 / 2018 / 20
Setup experience7 / 2015 / 20
Best for
  • AI coding assistants that use MCP (e.g., Claude Code, Cursor)
  • Developers who need to automate workflows around test suites
  • Teams looking to reduce token usage while maintaining reliable parsing
  • 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
  • Scenarios requiring non-Node.js native integration or HTTP/SSE transport
  • Users needing support for test frameworks not listed in this profile (e.g., Maven)
  • Developers who prefer to parse terminal output directly without structured data
  • 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
  • File system access: to run test commands and read test output
  • Subprocess execution: to run test runners (pytest, jest, etc.)
  • Network access: potentially for installing packages via npm
  • 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
  • Test commands may execute arbitrary code; risk depends on project scripts
  • Performance impact if test runners consume significant system resources
  • Misconfiguration or failing tests may lead to partial output
  • 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