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.

DimensionAnything Analyzer MCP ServerCross-scenario traffic capture and protocol analysis for AI agents.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS27 / 100 · D79 / 100 · B
Reliability3 / 2012 / 20
Security and permissions5 / 2018 / 20
Maintenance4 / 2016 / 20
Documentation9 / 2018 / 20
Setup experience6 / 2015 / 20
Best for
  • Developers who need one workflow for browser, application, terminal, and mobile traffic
  • Researchers conducting authorized protocol reverse engineering, API debugging, or security audits
  • Users who want an AI agent to help interpret HTTP traffic
  • 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
  • Unauthorized intrusion, data acquisition, or system control
  • Active proxy workflows that require modifying requests or responses
  • Use cases requiring decrypted WebSocket contents
  • Users seeking a built-in AI model without configuring an external model API
  • 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
  • AI analysis requires an API key for OpenAI, Anthropic, or a compatible API
  • HTTPS MITM capture requires installing and managing a local CA certificate
  • Changing system proxy settings may require operating-system permissions
  • The proxy can access request and response headers and bodies, plus Cookie, localStorage, and sessionStorage snapshots
  • 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
  • Captured traffic may contain tokens, cookies, credentials, or other sensitive data
  • Installing a local CA certificate and enabling a system proxy increases the visibility of local traffic
  • Sending captured data to an external LLM service can create privacy and compliance risks
  • Bodies are limited to 1 MB and binary content is skipped; WebSocket traffic is tunneled rather than decrypted
  • 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, CursorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00