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.

DimensionScrapeGraph MCP ServerAI-powered web scraping and data extraction with enterprise reliability via ScrapeGraph API.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS52 / 100 · D79 / 100 · B
Reliability5 / 2012 / 20
Security and permissions9 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • AI assistant developers who need natural-language-driven web scraping and structured data extraction.
  • Crawler and data analysis workflows that need automated extraction from multiple pages.
  • Users who need to monitor website changes and extract information on a schedule.
  • 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
  • Developers who don't need AI-assisted scraping and just want simple direct HTTP requests.
  • Users without a ScrapeGraph AI paid subscription or with limited credits, as API calls may incur costs.
  • Users needing local JavaScript rendering without using ScrapeGraph API's rendering capabilities.
  • 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 ScrapeGraph API key (SGAI_API_KEY) to access ScrapeGraph services.
  • Requires network access to reach the ScrapeGraph API (default https://v2-api.scrapegraphai.com/api).
  • API key passed via environment variable or MCP config, which may involve secret management.
  • 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
  • API key leakage could lead to unauthorized usage and credit loss.
  • API calls are subject to rate limiting and quota management; exceeding may incur extra costs.
  • Scraping websites may violate their terms of service or laws; use responsibly.
  • 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
Tools170