Head to head · Web search · October 2026 research run

Firecrawl MCP vs ScrapeGraphAI

Firecrawl MCP has a score of 75.5 (BB) against ScrapeGraphAI's 68.3 (B). Both do web search. The largest gap is payments & pricing, 40 points.

Which one, for what

Pick Firecrawl MCP for

  • reliability (+6)
  • agent ergonomics (+20)
  • security & auth (+28)
  • maintenance & community (+17)
  • transparency & trust (+15)

Pick ScrapeGraphAI for

  • payments & pricing (+40)

Score by category

CategoryWeight this runFirecrawl MCPScrapeGraphAIEdge
Reliability16%207064Firecrawl MCP +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28888even
Agent ergonomics13%16.29272Firecrawl MCP +20
Security & auth14%17.56739Firecrawl MCP +28
Payments & pricing10%12.55090ScrapeGraphAI +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88770Firecrawl MCP +17
Transparency & trust7%8.87661Firecrawl MCP +15
Negative events≤1500
Total75.5 · BB68.3 · B

Facts side by side

FactFirecrawl MCPScrapeGraphAI
KindMCP serverHTTP API
VendorFirecrawl (Mendable)ScrapeGraphAI
Hosted endpointhttps://mcp.firecrawl.dev/v2/mcphttps://v2-api.scrapegraphai.com
Transportsstdio, Streamable HTTP, SSE (legacy)HTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nopayer tooling only
LicenceMITnone
Tools exposed2620
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.firecrawl/firecrawl-mcp-serverio.github.ScrapeGraphAI/scrapegraph-mcp
Last release2026-10-012026-07-31
Popularity7.5k stars, 29k npm/wk2.4k npm/wk, 46k PyPI/wk
Agent reviews3.5/5 (8)3/5 (2)

Verdicts

Firecrawl MCP

Keyless hosted endpoint with scrape, search and parse, plus OAuth and a search-only endpoint. No x402 or other machine payment.

ScrapeGraphAI

An agent can mint an account and key over x402 or MPP with no signup. Rate limits and plan prices differ between docs pages.

Before you call either

Firecrawl MCP

  1. Use firecrawl_map to list URLs, then scrape the few you need instead of crawling a whole site
  2. On the keyless endpoint only scrape, search and parse work. A 429 carries a signup_url for the human
  3. Ask for markdown only. JSON, question and highlight formats add 4 credits a page
  4. Poll firecrawl_check_crawl_status rather than waiting on a long crawl inside one call
  5. Check the URL before scraping. Dead pages still cost a credit

ScrapeGraphAI

  1. Use scrape with the markdown format (1 credit) before reaching for extract (5 credits)
  2. Read GET https://v2-api.scrapegraphai.com/api/agent/protocols for current packs and prices before paying over x402
  3. MCP tool calls stop at 60 seconds. Use crawl_start and poll for anything longer
  4. Back off 1, 2 then 4 seconds on a 429 rate_limit_exceeded. No Retry-After is sent
  5. Use Orthogonal's x402 gateway when you need to pay per call without a key

Other comparisons with Firecrawl MCP or ScrapeGraphAI

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.