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.

DimensionTrinitySovereign AI Agents Platform supporting Claude Code, Codex, Gemini agents. Apache 2.0.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS62 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance15 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Organizations needing self-hosted AI agent deployment with data residency and audit.
  • Development teams wanting to run agents with Claude Code, Codex, or Gemini.
  • Production-grade agent orchestration with isolation, scheduling, and observability.
  • 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 needing zero-configuration hosted solutions (requires Docker and self-hosting).
  • Those seeking a lightweight agent framework without Docker.
  • Teams not interested in managing the platform themselves.
  • 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
  • MCP server requires an API key (Bearer token) for authentication.
  • Agents themselves run in Docker containers and may require network access to APIs and external endpoints.
  • The platform stores credentials (encrypted) and Git data.
  • Admins and users control access through role hierarchy (admin, creator, operator, user).
  • 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
  • Self-hosting requires infrastructure management; misconfigurations could lead to security issues.
  • Agent-run code may be untrusted; Docker isolation is essential.
  • Credentials are stored via Git and encrypted, but need proper protection.
  • Webhooks may expose public endpoints, mitigated with HMAC signatures.
  • 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 CodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools770