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.

DimensionContext7Up-to-date code docs for any promptMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS42 / 100 · D79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions10 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation5 / 2018 / 20
Setup experience10 / 2015 / 20
Best for
  • Developers who need current code documentation
  • Teams using MCP-capable AI agents or clients
  • Users who want to connect through stdio or Streamable HTTP
  • 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 seeking other MCP server capabilities from the Klavis repository
  • Users requiring a documented tool list or documented client compatibility
  • Offline workflows that cannot depend on the external Context7 service
  • 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
  • If authentication is used, provide CONTEXT7_API_KEY
  • Remote usage requires network access to https://mcp.context7.com/mcp
  • Local stdio or MCPB usage requires the appropriate local runtime environment
  • 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 API key is secret and should not be exposed
  • Remote usage depends on network connectivity and Context7 service availability
  • The supplied sources do not specify the tool list, data handling scope, or detailed permissions
  • 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