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.

DimensionRoam Code MCP ServerLet AI coding agents understand code before changing it safely.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS69 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions13 / 2018 / 20
Maintenance16 / 2016 / 20
Documentation17 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Large local repositories used with AI coding agents.
  • Development teams that need change-impact analysis and safer refactoring.
  • Projects requiring architecture governance, code health metrics, and audit evidence.
  • Users who want local code analysis without API keys.
  • 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
  • Real-time type checking; the source recommends an LSP for that purpose.
  • Small scripts with fewer than about 10 files.
  • Simple tasks requiring only raw text search.
  • Treating taint or long-tail detector results as complete security coverage.
  • 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
  • Access to the local repository is needed to discover, parse, and analyze source files.
  • The server creates the local .roam/index.db and related analysis state.
  • Write, persistence, or change-related tools may update .roam control files, run records, or evidence files.
  • API keys and cloud login are not required by default.
  • 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
  • Missing, stale, or interrupted indexes can produce incomplete analysis; inspect returned status and error signals.
  • Static analysis and framework-idiom detection are not substitutes for real-time type checking or deep SAST; some findings are advisory.
  • The full preset exposes 244 tools and may enlarge an agent's prompt surface.
  • The first tree-sitter-language-pack use may download a checksum-verified platform grammar bundle; other network-capable commands and flags are opt-in.
  • Write operations or autonomous-agent modes may create real repository files and run-record changes.
  • 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, Claude Desktop, Cursor, VS Code with CopilotClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools170