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 DotnetStructured .NET CLI operations as typed JSON for AI agents.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS42 / 100 · D79 / 100 · B
Reliability4 / 2012 / 20
Security and permissions6 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation9 / 2018 / 20
Setup experience11 / 2015 / 20
Best for
  • .NET developers needing reliable structured data.
  • Workflows that automate .NET projects with AI agents.
  • Users of AI tools looking to reduce token consumption.
  • 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 requiring raw terminal format output.
  • Simple manual CLI use where structured data is unnecessary.
  • 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
  • Executes dotnet CLI commands, potentially reading/writing file system (e.g., build outputs, package caches).
  • May require network access for operations like restoring NuGet packages.
  • 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
  • Executing dotnet commands may modify project files or system state, such as installing packages or generating files.
  • Misuse could accidentally run destructive commands (e.g., force cleanup).
  • Depends on the .NET SDK; failure occurs if not installed.
  • 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, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00