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.

DimensionOpenAPI Proxy MCP ServerDynamically expose any OpenAPI-defined REST API as MCP tools.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS51 / 100 · D79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions7 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation13 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers and teams who want to integrate existing REST APIs described by OpenAPI into the MCP ecosystem.
  • Scenarios where you need quick conversion of APIs to MCP tools with dynamic tool generation.
  • 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
  • APIs without OpenAPI specifications (would need manual generation or conversion).
  • Use cases requiring fine-grained control over each tool's behavior (this server is generic and spec-driven).
  • APIs with complex authentication flows (e.g., OAuth) unless handled manually via custom headers and EXTRA_HEADERS.
  • 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 OpenAPI spec URL (HTTP or local file).
  • API keys or tokens for the target API (via API_KEY or custom headers).
  • Read/write permissions to the target API depending on exposed tools.
  • 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
  • Exposing many tools may consume tokens or degrade performance; use TOOL_WHITELIST to limit.
  • Credentials are passed via environment variables; ensure secure configuration.
  • Remote spec downloads can be slow or fail, causing startup issues (mitigated by caching).
  • Some clients have incomplete prompts/resources support; features may be limited.
  • 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, Gemini, Qwen, Kilocode, OpenCode, Vibe, LettaClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00