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.

DimensionPare LintStructured linting and formatting (ESLint, Prettier, Biome, Oxlint) as typed JSON.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS40 / 100 · D79 / 100 · B
Reliability6 / 2012 / 20
Security and permissions6 / 2018 / 20
Maintenance9 / 2016 / 20
Documentation8 / 2018 / 20
Setup experience11 / 2015 / 20
Best for
  • AI coding agents that need reliable, structured lint output
  • Developers who want to avoid parsing complex terminal text
  • Projects using ESLint, Prettier, Biome, or Oxlint
  • 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
  • Scenarios where structured output is not needed, such as simple lint checks for human reading
  • Projects that do not use common lint/format tools
  • 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
  • Read project files for linting and formatting
  • May write files if auto-fix is enabled
  • 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
  • Wrapped tools (e.g., ESLint) may have security vulnerabilities; keep them updated
  • Structured output may become inaccurate if tool output formats change
  • Requires Node.js >= 20
  • 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
Tools00