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.

DimensionMCP BoilerplateA remote Cloudflare MCP server boilerplate with user authentication and Stripe for paid tools.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS48 / 100 · D79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions8 / 2018 / 20
Maintenance7 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience11 / 2015 / 20
Best for
  • Developers needing a remote MCP server on Cloudflare quickly
  • Developers wanting to monetize MCP tools
  • Projects requiring user authentication
  • 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
  • Local MCP servers
  • Developers preferring non-Cloudflare platforms
  • Simple projects without auth or payments
  • 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
  • Cloudflare account access
  • Google or GitHub OAuth credentials
  • Stripe API keys
  • 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 keys and encryption keys must be kept secure
  • Incorrect Stripe configuration can cause payment issues
  • Cloudflare deployment may incur costs
  • 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, Cursor, Cloudflare AI Playground, MCP InspectorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools40