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.

DimensionHf MCP ServerConnect your LLM to the Hugging Face Hub and thousands of Gradio AI Applications.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS57 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions11 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Developers wanting to integrate Hugging Face ecosystem into LLM tools
  • AI application builders needing access to models, datasets, and Gradio apps
  • 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 not using Hugging Face services
  • Scenarios requiring long-lived connections or stateful MCP servers (STDIO does not expose skills)
  • 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
  • Requires a Hugging Face token (HF_TOKEN) for authentication
  • HTTP transport requires Authorization: Bearer header
  • May access Hugging Face API and Gradio apps
  • 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
  • User-supplied tokens may be misused
  • Proxy tools or external URLs may introduce security risks
  • Local loopback addresses are allowed by default; external access requires allowlist
  • 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, Claude Code, Gemini CLI, VS Code, CursorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00