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.

DimensionFrontMCPA production-grade, TypeScript-first MCP framework.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS49 / 100 · D79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions9 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience10 / 2015 / 20
Best for
  • Developers building production MCP servers with TypeScript
  • Teams needing built-in authentication, sessions, transport, and dependency injection
  • Projects deploying one codebase across Node and serverless platforms
  • 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 who only want to consume existing MCP tools
  • Projects that do not use TypeScript or JavaScript
  • Use cases requiring ready-made business tools rather than an MCP server framework
  • 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
  • The source does not specify concrete runtime system permissions, network permissions, or credential scopes.
  • When authentication, OAuth, JWKS, or the credential vault is enabled, required credentials and access scopes depend on the configuration.
  • 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
  • Node.js 24 or later is required; older runtimes may not work.
  • Misconfigured authentication, sessions, or HTTP deployment may create access-control or session-management risks.
  • A mismatch among `@frontmcp/*` package versions causes a boot-time version mismatch error.
  • The framework supports multiple deployment platforms, but the source does not provide platform-specific configuration or security requirements.
  • 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