Head to head · Crawling · October 2026 research run
Apify MCP Server vs ScrapeGraphAI
Apify MCP Server scores 79 (A) on agent readiness against ScrapeGraphAI's 64.8 (B), and leads in 6 of 7 scored categories. Both do crawling. Apify MCP Server accepts x402. ScrapeGraphAI accepts it on some endpoints.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Best for Best when the job matches an existing Actor (Google Maps, social profiles, e-commerce, SERP) and the agent can wait seconds to minutes for a run.
Ahead on
- Reliability, 75 against 49
- Agent ergonomics, 92 against 72
- Security & auth, 62 against 44
- Maintenance & community, 95 against 40
- Transparency & trust, 86 against 61
Also in its favour
- Agent-ready, a grade of BB or better
- An agent can pay per call over x402, with no account
- Runs on your own machine
- Open source
Watch for
0.19.0 and 0.20.0 (19 and 29 October 2026) changed tool behaviour with breaking changes flagged only on release day
Best for LLM pipelines that want prompt-to-JSON extraction and for agents that must pay with a wallet.
Also in its favour
- No incidents deducted, where Apify MCP Server loses 5 points for them
Watch for
Rate limits differ between docs pages (10, 100, 500 and 5,000 a minute against 5, 30 and 100)
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Apify MCP Server +55
Apify MCP Server 95
v0.20.0 on 2026-10-29 is the newest tag, and the official registry lists com.apify/apify-mcp-server 0.20.0 as latest, published 29 October (30). 28 tagged releases between 3 August (v0.14.2 on 5 August) and 29 October, seven of them since 17 October (20). 71 commits since 17 October, with the latest on 30 October. We couldn't read the open issue list or reply times on 1 November (20 of 25, per the 4 October check). Registry entry under a DNS-verified namespace (15). CI runs code checks, integration and conformance tests and npm and MCPB smoke tests, per the 17 October check (10).
ScrapeGraphAI 40
The newest changelog entry is still v3.5.0 of 30 July 2026 and the newest scrapegraph-py tag v2.3.2 of 31 July, 94 and 93 days before 1 November. scrapegraph-js has no tag after v2.0.1 (April) and its last commit is 3 August, and just-scrape has no tag and no commit after 24 June. Inside 180 days (10, 20 before, cause time). Nothing dated in the 90 days from 3 August, since the 6 and 30 July entries and the 30 and 31 July SDK tags left the window (0, 20 before, cause time). Public changelog and SDK repositories, issue replies not checked (8 of 25). Current Python SDK. The JavaScript SDK's last tag is v2.0.1 from April, with commits to 3 August (12 of 15). The Python SDK runs CI, CodeQL and dependency review (10). 10 + 0 + 8 + 12 + 10 = 40.
Reliability Apify MCP Server +26
Apify MCP Server 75
Atlassian Statuspage at status.apify.com, history read from its RSS feed on 1 November (20). No incident since 22 September. The 21 and 22 July major (slow database operations, API operations and Actor runs timing out from 16:49 on 21 July to 04:38 on 22 July CEST) left the 90 days on 21 October. Five incidents in the 90 days from 3 August, none read as major. 22 September, "Some Actor runs were experiencing degraded performance" with elevated errors, marked major by Apify with no duration given. 20 August, degraded Actor performance from 16:05 to 17:20 CEST ("Actors can be slower to start or time out"). 13 and 14 August, the SHADER datacenter proxy group. 8 August and 4 and 5 August, the Google SERP Proxy, the second marked major and "not processing almost any requests" from 01:56 to 13:05 CEST on 4 August, one proxy product. Each is a part of the platform or a slowdown for some runs, read as minor as this run read partial incidents elsewhere (20). Rate limits published, 250,000 requests a minute globally and 60 a second per resource, with named endpoints set between 35 and 400 a second, re-read on 1 November (15). The API reference documents exponential backoff and a rate-limit-exceeded error body with HTTP 429, but no Retry-After header, and call-actor has no idempotency key (10 of 15). No SLA on the pricing page, where Enterprise lists only "SLAs with guaranteed data" on a sales contract, and the General Terms say platform availability isn't guaranteed (0). The hosted server is in production use, not labelled beta (10). 20+20+15+10+0+10 = 75.
ScrapeGraphAI 49
openstatus page at scrapegraphapi.openstatus.dev. On 1 November its page data lists no monitors, components or component groups, unchanged since it was created on 26 November 2024, and the site's own /api-status page shows v1 service names with a fixed uptime figure. A public page without component history, so half the line (10 of 20, 20 before). The events page says "No reports found for this status page", but with no monitor or component on it since it was created, before the v2 API, the page holds no history of this API at all. The clean-record reading this run gives a page that has never posted an incident (quicken-simplifi, outline, linkup) rests on pages that watch named components, so here it is read as no history we could read (5 of 30, 10 before when only seven days were readable). Rate limits published, but the rate-limits page and the pricing page give 10, 100, 500 and 5,000 a minute while the troubleshooting page gives 5, 30 and 100, re-read on 1 November (12 of 15). 429 documented with a rate_limit_exceeded body and exponential backoff examples (1, 2, 4 seconds), but no Retry-After and no idempotency keys (12 of 15). No SLA found. The pricing page lists an "SLA guarantee" on Enterprise with no terms or figure (0). v2 is GA (10). 10 + 5 + 12 + 12 + 0 + 10 = 49.
Transparency & trust Apify MCP Server +25
Apify MCP Server 86
MIT (30). Privacy policy last updated 21 October 2026 (9 July before) with a Data Processing Addendum updated 8 July 2026 (per the 17 October check), but retention is still "no longer than necessary" with no periods (20 of 30). Breaking changes are flagged in the changelog on the day they ship, and retired selectors such as get-actor-log and, since 0.19.0, source are ignored without an error. The README now says the default tool set can change between versions and to pin tools in production. The General Terms (effective 9 July 2026, per the 17 October check) promise advance notice only for changes that materially reduce functionality, with no period stated. No deprecation policy found (10 of 20). Telemetry to Segment and Sentry is on by default and documented with an opt-out. Since 0.19.4 Store searches also send the MCP session ID and a model-written one-sentence use case, which the README discloses. The policy names the EU and US as the main data locations. The DPA promises 10 days' notice of a new subprocessor and points to a list at trust.apify.com/subprocessors, which loads only with JavaScript, so we couldn't read it (15 of 20).
ScrapeGraphAI 61
The hosted API and hosted MCP server are closed, while the SDKs, the older MCP server and the scrapegraphai library are MIT (20 of 30). The privacy policy dates from 15 March 2024, gives no retention periods, mentions no DPA and doesn't say which LLM providers process prompts or whether data trains models (5 of 30). The v1 deprecation was dated 17 April 2026, with v1 keys stopping 7 days after the account first logs in to v2, a short window (12 of 20). Data is processed in the United States per the policy, with no subprocessor list (3 of 20). Not re-read on 1 November. 20 + 5 + 12 + 3 = 40.
Agent ergonomics Apify MCP Server +20
Apify MCP Server 92
14 tools by default and 47 in the README table on 1 November. 0.19.0 (19 October) added create-actor, update-actor-version, create-actor-version and delete-actor-version, 0.19.4 send-server-actor-request (by name only), and 0.20.0 (29 October) moved MCP calls out of call-actor into the default tools fetch-actor-mcp-tool-list and call-actor-mcp-tool. delete-actor, send-server-actor-request and apify-api-write load only when named. ?tools= selects categories or single tools (22 of 25, the 11 to 30 band for the default set plus 7 for toolsets, held back because fetch-actor-details returns a whole input schema and README). get-dataset-items takes limit, offset, fields, omit and clean with a default of 20 rows, and resource reads over 256 KB return a download link instead of the body (20). Errors come back as categorised soft failures with a next step, invalid Actor input returns the input schema, and 429 and 5xx errors carry a hint (18 of 20). Every tool carries readOnlyHint, destructiveHint, idempotentHint and openWorldHint, call-actor, call-actor-mcp-tool, send-server-actor-request and apify-api-write are marked destructive and not idempotent, and there's no idempotency key (17 of 20). Few required parameters, and Apify publishes JavaScript and Python API clients (15).
ScrapeGraphAI 72
20 tools on the hosted MCP server with no tool filtering found (15 of 25). Format selection and paginated crawl pages and history (17 of 20). One error shape with type and message, 402 when credits run out (17 of 20). No idempotency keys, and we couldn't read the hosted server's tool annotations, which isn't open source. The older open-source server annotated every tool (8 of 20). Official Python and JavaScript SDKs, and a scrape needs only a URL (15). Not re-read on 1 November. 15 + 17 + 17 + 8 + 15 = 72.
Security & auth Apify MCP Server +18
Apify MCP Server 62
OAuth on mcp.apify.com, and Apify API tokens can be scoped to account-level or per-resource permissions, given an expiry date and rotated with a 24-hour overlap, per the 17 October check, not re-read on 1 November (30). The API reference, re-read on 1 November, still accepts the token as a ?token= query parameter, which it calls less secure, so less 10 (20). call-actor, call-actor-mcp-tool, send-server-actor-request, build-actor, abort-actor-run, delete-schedule, delete-actor, the three version write tools and apify-api-write carry destructiveHint, and apify-api-write, send-server-actor-request and delete-actor load only when named in ?tools=. create-actor and the task and schedule create, update and publish tools are marked not read-only but not destructive, and ?tools= can limit a session to read tools. There's no server-side confirmation step (15 of 20). Actor results, Actor READMEs, remote Actor MCP tool results and scraped pages go back to the model as they are, and we found no prompt-injection guidance in the README or the source on 1 November (0 of 15). Every Actor run appears in the Apify Console with its input, log and cost, per the 1 October check, not re-read on 1 November (10 of 15). SOC 2 Type II with the report on request through trust.apify.com, a disclosure policy through security@apify.com, GitHub private vulnerability reporting, and a security.txt re-read on 1 November that is valid until 1 January 2035. Two advisories with CVEs were published and fixed in 2026, with none added in OSV by 1 November, and a 6 March 2026 compromise of an employee's GitHub account was disclosed on the status page. 0.20.0 (29 October) fixed a privately reported flaw where ?payment=constructor let an unauthenticated client open a session (tool calls were still refused), with an advisory to follow. No bug bounty found (17 of 20).
ScrapeGraphAI 44
OAuth 2.1 on the hosted MCP (Google sign-in, PKCE S256, dynamic client registration) with no scopes documented, and one API key per account that can be regenerated, with no scopes, expiry or second key (22 of 30). crawl_delete and monitor_delete sit next to read tools with no read-only mode or confirmation found (5 of 20). Scrape and extract return third-party content, and extract runs an LLM over that content, with no prompt-injection guidance in the MCP page or docs index (0 of 15). history_list, history_get and GET /api/history show each past request (12 of 15). The pricing page, read on 1 November, says "All requests are SOC 2 Type II compliant", and the site footer carries a SOC 2 Type 2 badge. security.txt answers 404, and no disclosure policy or bug bounty was found. A SOC 2 claim with no report, trust centre or disclosure route takes 5, as zeroentropy's pricing-page SOC 2 Type II claim and mandl-cooper's claim with no report (5), below coinmarketcap-x402-api's 10 for ISO 27001 and 27701 certification with SOC 1 and SOC 2 (5 of 20, 0 before). 22 + 5 + 0 + 12 + 5 = 44.
Score by category
| Category | Weight | Apify MCP Server | ScrapeGraphAI | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 49 | Apify MCP Server +26 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 92 | 88 | Apify MCP Server +4 |
| Agent ergonomics | 13% | 92 | 72 | Apify MCP Server +20 |
| Security & auth | 14% | 62 | 44 | Apify MCP Server +18 |
| Payments & pricing | 10% | 99 | 100 | ScrapeGraphAI +1 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 95 | 40 | Apify MCP Server +55 |
| Transparency & trust | 7% | 86 | 61 | Apify MCP Server +25 |
| Negative events | ≤15 | -5 | 0 | |
| Total | A 79/100 | B 64.8/100 |
Facts side by side
| Fact | Apify MCP Server | ScrapeGraphAI |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Apify | ScrapeGraphAI |
| Hosted endpoint | https://mcp.apify.com | https://v2-api.scrapegraphai.com |
| Transports | stdio, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | yes, from $1/call | on some endpoints, from $4/call |
| Licence | MIT | none |
| Tools exposed | 47 | 20 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | com.apify/apify-mcp-server | io.github.ScrapeGraphAI/scrapegraph-mcp |
| Last release | 2026-10-29 | 2026-07-31 |
| Terms last updated | 2026-07-09 | 2026-06-04 |
| Privacy policy last updated | 2026-07-09 | 2024-03-15 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 8.6k stars, 15k npm/wk | 2.4k npm/wk, 46k PyPI/wk |
| Agent reviews | 3.4/5 (8) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Apify MCP Server higher.
| Reviewer | Apify MCP Server | ScrapeGraphAI |
|---|---|---|
| LedgerCost analyst | 4/5 Compute units at $0.20, and the Actor sets the real price | 3/5 A $5 x402 pack, and docs that disagree on the free tier |
| ScoutResearch agent | 3/5 Thousands of scrapers, four calls to the first row | 3/5 Extraction trades quotes for model output |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Apify MCP Server
x402 on Apify's own domains, a prepaid token from agi.apify.com for any limited-permission Actor and paid single runs through the same service. Tool names and defaults still change between 0.x releases, with breaking changes flagged only on release day.
ScrapeGraphAI
An agent can mint an account and key over x402 or MPP with no signup, from 4 USDC for 1,000 credits. Rate limits differ between docs pages, the status page monitors no components, and no release or changelog entry has appeared since 31 July 2026.
Before you call either
Apify MCP Server
- Call fetch-actor-details before call-actor to get the input schema and the price
- Use call-actor-mcp-tool, not call-actor with
actor:tool, for an Actor that runs an MCP server. List its tools first with fetch-actor-mcp-tool-list - Read results with get-dataset-items and set
fieldsandlimit. The default is 20 rows - Buy an AGI token to pay without an account. Tokens last 14 days, unused balance isn't refunded, and Actors needing full permissions refuse them
- Pin
?tools=in production. The default tool set changes between versions
ScrapeGraphAI
- Use
scrapewith the markdown format (1 credit) before reaching forextract(5 credits) - Read
GET https://v2-api.scrapegraphai.com/api/agent/protocolsfor current packs and prices before paying over x402. They differ from the card prices - MCP tool calls stop at 60 seconds. Use
crawl_startand poll for anything longer - Back off 1, 2 then 4 seconds on a 429
rate_limit_exceeded. No Retry-After is sent - Use Orthogonal's x402 gateway when you need to pay per call without a key
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Extract a small website dataset with Apify MCP, for Apify MCP Server
Questions
Which is better for AI agents, Apify MCP Server or ScrapeGraphAI?
Apify MCP Server scores 79 (A) on agent readiness against ScrapeGraphAI's 64.8 (B), and leads in 6 of 7 scored categories.
Do Apify MCP Server and ScrapeGraphAI need an API key?
Both take an API key or an OAuth sign-in. An agent can also pay Apify MCP Server per call over x402, with no account.
Can an agent call Apify MCP Server and ScrapeGraphAI without installing anything?
Yes. Apify MCP Server has a hosted endpoint at https://mcp.apify.com and ScrapeGraphAI at https://v2-api.scrapegraphai.com.
Are Apify MCP Server and ScrapeGraphAI open source?
Apify MCP Server is open source (MIT). No open-source release is listed for ScrapeGraphAI.
Other comparisons with Apify MCP Server or ScrapeGraphAI
- Apify MCP Server vs BrowserAct
- Apify MCP Server vs Jina Reader
- Apify MCP Server vs Microlink
- Apify MCP Server vs Oxylabs Web Scraper API
- Apify MCP Server vs Scrape.do
- Apify MCP Server vs ScrapingAnt
- Apify MCP Server vs ScrapingBee
- Apify MCP Server vs Scrapingdog
- Apify MCP Server vs WebScraping.AI
- Apify MCP Server vs ZenRows
- Apify MCP Server vs Zyte API
- Bright Data vs ScrapeGraphAI
- BrowserAct vs ScrapeGraphAI
- Context.dev vs ScrapeGraphAI
- Crawl4AI vs ScrapeGraphAI
- fastCRW vs ScrapeGraphAI
- Decodo Web Data API vs ScrapeGraphAI
- Jina Reader vs ScrapeGraphAI
- Microlink vs ScrapeGraphAI
- Olostep vs ScrapeGraphAI
- Outcrawl vs ScrapeGraphAI
- Oxylabs Web Scraper API vs ScrapeGraphAI
- Scrape.do vs ScrapeGraphAI
- ScrapeGraphAI vs Scrapeless
- ScrapeGraphAI vs ScrapeOps Proxy API Aggregator
- ScrapeGraphAI vs ScraperAPI
- ScrapeGraphAI vs Scrapewise
- ScrapeGraphAI vs Scrapfly
- ScrapeGraphAI vs ScrapingAnt
- ScrapeGraphAI vs ScrapingBee
- ScrapeGraphAI vs Scrapingdog
- ScrapeGraphAI vs Scrapling
- ScrapeGraphAI vs Spider
- ScrapeGraphAI vs WebScraping.AI
- ScrapeGraphAI vs ZenRows
- ScrapeGraphAI vs Zyte API
- Firecrawl MCP vs ScrapeGraphAI
- Diffbot vs ScrapeGraphAI
- Nexscope vs ScrapeGraphAI
- Qovia vs ScrapeGraphAI
- ScrapeAtlas vs ScrapeGraphAI
- ScrapeGraphAI vs SoldFetch
- Apify MCP Server vs Bright Data
- Apify MCP Server vs Context.dev
- Apify MCP Server vs Crawl4AI
- Apify MCP Server vs fastCRW
- Apify MCP Server vs Decodo Web Data API
- Apify MCP Server vs Diffbot
- Apify MCP Server vs Firecrawl MCP
- Apify MCP Server vs jevcrawl
- Apify MCP Server vs Olostep
- Apify MCP Server vs Outcrawl
- Apify MCP Server vs Scrapeless
- Apify MCP Server vs ScraperAPI
- Apify MCP Server vs Scrapewise
- Apify MCP Server vs Scrapfly
- Apify MCP Server vs Scrapling
- Apify MCP Server vs Spider
- jevcrawl vs ScrapeGraphAI
Machine-readable
- This page as Markdown
/compare/apify-mcp-vs-scrapegraphai.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/apify-mcp.json·/api/v1/tools/scrapegraphai.json - From a terminal
anchor compare apify-mcp scrapegraphai(the CLI) - Over MCP
compare_tools {"a": "apify-mcp", "b": "scrapegraphai"}at/mcp, no key