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.

DimensionMemoryLens MCPOn-demand .NET memory profiling with AI-actionable code fix suggestions.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS51 / 100 · D79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions8 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience11 / 2015 / 20
Best for
  • .NET developers seeking quick, on-demand memory profiling integrated with AI-assisted coding tools.
  • Debugging scenarios that require analyzing running .NET processes by their PID.
  • Teams that want to automate detection of common memory leak patterns like event handler leaks or static collections growing unbounded.
  • 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
  • Non-.NET processes are not supported.
  • Users without .NET 10 SDK or on unsupported platforms (e.g., FreeBSD) will need manual dotMemory setup.
  • Not suitable for fully offline scenarios unless the dotMemory CLI is pre-installed and cached.
  • 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 arbitrary commands to launch profilers (e.g., dotMemory CLI).
  • May access the network to download tools and dependencies.
  • May require ptrace and host PID namespace if running in a container.
  • 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
  • The tool downloads and executes external binaries (dotMemory CLI), introducing supply chain risk.
  • Memory profiling of a target process may impact its performance or stability.
  • Running with elevated privileges could pose security risks.
  • 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, VS Code, Visual Studio, Claude CodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools60