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 BuildStructured build output as typed JSON diagnosticsMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS49 / 100 · D79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions7 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation11 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Projects using TypeScript, esbuild, Vite, or webpack
  • Developers wanting reliable build diagnostics for agents
  • Use cases needing minimal token overhead from build logs
  • 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
  • Human users desiring unstructured raw build output
  • Projects not using build tools
  • Scenarios requiring source code or project metadata
  • 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 project files to perform builds
  • Execute build commands
  • Communicate with MCP client via stdio
  • 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
  • Build commands might execute arbitrary code (e.g., scripts)
  • Build output may contain sensitive info (like paths or env vars)
  • Dependencies on npm package and build toolchain availability and security
  • 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