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.

DimensionByteAsk Embedded MCPPage-cited evidence retrieval for embedded and firmware coding agents.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS54 / 100 · D79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions8 / 2018 / 20
Maintenance9 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Development scenarios requiring precise, citable embedded documentation facts
  • Users wanting quick integration and the ability to plug in custom retrieval backends
  • 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
  • Applications needing natural-language summaries or non-verbatim answers
  • Scenarios where the full corpus is required but self-hosting is insufficient
  • Users who need authoritative source verification or dedicated support
  • 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
  • Accepts queries and returns retrieval results
  • Can request document additions (logged only)
  • HTTP server and authentication on local network
  • 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
  • Full retrieval capability is only available via the hosted service; self-hosted backend is illustrative and may not cover all documents.
  • The HTTP transport's bearer authentication is a stub; replace with production-grade auth before public deployment.
  • DNS-rebinding protection exists, but additional hardening is needed when exposing publicly.
  • Tool outputs come from documents that may be unofficial or outdated; users should verify facts.
  • 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, CursorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools30