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.

DimensionDecodo MCP ServerEnable your AI agents to scrape and parse web content dynamically, including geo-restricted sitesMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS57 / 100 · C79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance9 / 2016 / 20
Documentation16 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers who need real-time web data for LLMs and RAG pipelines
  • Teams building eCommerce intelligence, social monitoring, or price aggregation tools
  • AI agent projects that want production scraping without maintaining proxy infrastructure
  • 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 cannot rely on a third-party paid scraping service or hosted endpoint
  • Workflows needing only local file or internal data access
  • Privacy-sensitive cases where sending target URLs and prompts to Decodo's servers is unacceptable
  • 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
  • Requires a Decodo Web Scraping API basic auth token (SCRAPER_API_TOKEN)
  • Downloads and runs the @decodo/mcp-server package via npx from npm
  • Requires network access to call Decodo's hosted scraping service
  • 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
  • All target URLs and prompts pass through a third-party (Decodo) server
  • API usage costs apply once the free quota is exhausted
  • Scraping target sites may violate their terms of service; verify compliance yourself
  • Dependency on an external npm package and hosted API introduces supply-chain and availability 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, Cursor, Windsurf, Claude CodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools300