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.

DimensionHTTP MCP ServerHTTP MCP configuration example for REST APIsMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS36 / 100 · D79 / 100 · B
Reliability5 / 2012 / 20
Security and permissions8 / 2018 / 20
Maintenance11 / 2016 / 20
Documentation4 / 2018 / 20
Setup experience8 / 2015 / 20
Best for
  • Developers studying HTTP MCP configuration in Claude Code plugins
  • API integrations that provide a compatible MCP HTTP endpoint and API_TOKEN
  • 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 a verified production service
  • Users needing a documented tool list, concrete API capabilities, or client compatibility
  • Users expecting the example api.example.com endpoint to provide a working business 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
  • Network access to the configured HTTP endpoint
  • An API_TOKEN environment variable or equivalent Bearer credential
  • Permission for requests to use the declared Content-Type, API version, and service-name headers
  • 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
  • api.example.com/mcp is an example URL; the source does not establish that it is operational or belongs to a real service
  • API_TOKEN is sensitive authentication material and should not be exposed in untrusted configuration or logs
  • The README warns users to trust plugins before installing, updating, or using them; Anthropic does not control the MCP servers included in plugins and cannot verify that they work as intended or remain unchanged
  • 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