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.

DimensionSpline.design MCP ServerMCP server for generating runtime code for Spline 3D design tool (archived)MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS8 / 100 · D79 / 100 · B
Reliability0 / 2012 / 20
Security and permissions4 / 2018 / 20
Maintenance0 / 2016 / 20
Documentation4 / 2018 / 20
Setup experience0 / 2015 / 20
Best for
  • Developers who want to quickly generate @splinetool/runtime code.
  • Users of Claude Desktop who need example code snippets.
  • 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 direct control over Spline editor or scene creation (Spline has no public REST API).
  • Users needing a stable, maintained MCP server (project is archived).
  • 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
  • No special permissions; tools only generate code.
  • Network access required to run npm install.
  • 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
  • Server is archived; some tools may be non-functional.
  • Generated code relies on Spline runtime API; ensure Spline scene is exported and loaded correctly.
  • Potential unpatched bugs or security issues.
  • 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 DesktopClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools30