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.

DimensionDelimit MCP ServerThe merge gate for AI-written code, with signed, replayable attestation.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS48 / 100 · D79 / 100 · B
Reliability6 / 2012 / 20
Security and permissions8 / 2018 / 20
Maintenance9 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience10 / 2015 / 20
Best for
  • Teams using multiple AI coding assistants
  • Organizations wanting to enforce API compatibility
  • Compliance workflows needing verifiable audit trails of AI changes
  • 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 not using AI coding tools
  • Teams seeking a full CI/CD replacement rather than a governance layer
  • 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 repository files (for scanning, linting, diffing)
  • Write to local .git directory and .delimit directory (for hooks, configs, memory)
  • Execute commands (e.g., tests, security audit)
  • Network access (for model deliberation, cloud sync if enabled)
  • 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 server can execute code (e.g., tests, security audit), which could pose security risks.
  • Credentials or sensitive data could be stored in memory or ledger; ensure proper access control.
  • If cloud sync is enabled, event data may be sent to external services (user-provided Supabase).
  • 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, Codex, Cursor, Gemini CLIClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools130