← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionLLM Checker MCP ServerChoose and manage local LLMs for your hardware.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS50 / 100 · D79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions8 / 2018 / 20
Maintenance8 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers who run LLMs locally
  • Users needing hardware-aware model selection and Ollama management
  • Teams requiring deterministic scoring, calibrated routing, or policy audits
  • Users who want structural checks before running downloaded models
  • 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 without Node.js or local Ollama
  • Cloud-hosted inference workflows rather than local inference
  • Complete guarantees about model behavior, provenance, or poisoned weights
  • Arbitrary system command execution beyond the MCP allowlist
  • 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 local CPU, GPU, memory, and acceleration information
  • Access local Ollama model directories and the running Ollama environment
  • Depending on the tool, download, run, or remove models and execute prompts
  • Read specified project directories or model files for project recommendations and verification
  • Execute allowlisted LLM Checker CLI commands
  • 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
  • ollama_pull downloads models and consumes network bandwidth and disk space.
  • ollama_remove deletes local models and the data they occupy.
  • ollama_run and cli_exec can run local model or CLI workflows, so prompts and arguments should be reviewed.
  • Structural acceptance only indicates that a file is structurally safe to load; it does not establish model behavior, provenance, or absence of poisoned weights.
  • Files above 3 GiB may exceed the WASM32 verification memory ceiling and produce no verdict.
  • 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 Code, Codex, Grok, Kimi Code, Cursor, Windsurf, Gemini CLIClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools280