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.

DimensionJSHookMCPAn MCP server giving AI agents 600+ tools across 34 domains for JavaScript analysis and security research — browser automation, CDP debugging, network interception, JS hooks, LLM-powered code analysis, and workflow orchestration.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS44 / 100 · D79 / 100 · B
Reliability5 / 2012 / 20
Security and permissions5 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Security researchers specializing in JavaScript and reverse engineering
  • Developers needing browser automation and network debugging
  • Teams leveraging AI agents for dynamic code analysis
  • MCP users needing progressive tool profiles to optimize context
  • 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
  • General applications needing simple API access
  • Users uninterested in reverse engineering or browser automation
  • Those needing a minimal server without extra dependencies (use the search profile to reduce resource usage)
  • 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
  • Access to browser debugging interfaces (CDP)
  • Starting a local HTTP server bound to 127.0.0.1
  • Generating and managing local HTTPS certificates for traffic interception
  • Optional download of heavy dependencies (e.g., ONNX, Z3) when using full profiles
  • 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
  • Anti-detection and CAPTCHA features may violate third-party terms of service
  • Network interception could be misused; ensure lawful use
  • Running many tools may consume significant system resources
  • Exposing the HTTP endpoint without MCP_AUTH_TOKEN could allow unauthorized access
  • 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
Tools50