← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionClaude Code Explorer MCPClaude Code Explorer MCP - Explore the leaked source of Claude Code CLIMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS18 / 100 · D79 / 100 · B
Reliability3 / 2012 / 20
Security and permissions4 / 2018 / 20
Maintenance5 / 2016 / 20
Documentation4 / 2018 / 20
Setup experience2 / 2015 / 20
Best for
  • Developers who want to deeply understand Claude Code internals
  • Technical writers or bloggers writing about Claude Code source
  • Contributors needing to debug or extend Claude Code
  • 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 interested in Claude Code
  • Developers who need to interact with Claude Code, not just read its source
  • Users looking for an officially supported or maintained server
  • 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
  • Reads environment variable CLAUDE_CODE_SRC_ROOT if set to locate source
  • Runs local Node.js processes
  • Accesses network to download npm package (if using npx)
  • 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
  • This server is based on unofficial leaked source, which may contain unreleased or unauthorized code
  • Using third-party npm packages presents supply chain risks
  • The source may be inaccurate or outdated as it is not an official release
  • 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, Claude Code, VS Code, CursorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools80