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.

DimensionCRW Web ScraperOpen-source web scraping MCP server for AI agents with scrape, crawl, and map capabilitiesMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS54 / 100 · D79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions11 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation10 / 2018 / 20
Setup experience11 / 2015 / 20
Best for
  • Teams that want self-hosted web scraping with data control
  • Developers using Claude Code, Cursor, Codex, Gemini CLI, OpenCode, or Windsurf
  • Scenarios needing a low-resource single Rust binary
  • Migration projects requiring a Firecrawl-compatible REST API
  • 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 who need official Firecrawl, Tavily, or Anthropic backing or support
  • Scraping needs that will not respect site policies and robots.txt
  • Teams needing a fully managed SaaS without deploying anything themselves
  • 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
  • Network access: outbound HTTP/HTTPS requests to scrape, crawl, and search the web
  • Local filesystem read/write: to store configuration such as ~/.config/crw/config.toml
  • The install script may modify MCP configuration of detected AI tools
  • A CRW_API_KEY credential is required when using the managed cloud
  • 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
  • Scraping third-party sites may conflict with their terms of service, copyright, or robots.txt rules; the project states crawl and map follow robots.txt by default
  • The one-command install downloads and executes a remote script, which carries supply-chain risk
  • The API key is stored in ~/.config/crw/config.toml, so local file permissions and leakage matter
  • The container image uses the latest tag, which may make versions non-reproducible
  • Managed cloud and local capabilities or response shapes can differ; check /v1/capabilities and response shapes before migrating
  • 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