# Apify MCP Server vs Scrape.do (slim) > Apify scores 76.5 (BB) to Scrape.do's 43.7 (E) for scraping. Prices, MCP, x402, uptime and agent notes side by side. - Full: https://www.anchorterminal.com/compare/apify-mcp-vs-scrape-do.md (~2,650 tokens) · this version ~730 tokens · JSON https://www.anchorterminal.com/compare/apify-mcp-vs-scrape-do.json · canonical https://www.anchorterminal.com/compare/apify-mcp-vs-scrape-do - Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-04 Apify MCP Server scores 76.5 (BB) on agent readiness against Scrape.do's 43.7 (E), and leads in every scored category. Both do scraping. Apify MCP Server accepts x402. Scrape.do doesn't. - Apify MCP Server: BB 76.5, rank #28 of 950 · https://www.anchorterminal.com/tools/apify-mcp.min.md - Scrape.do: E 43.7, rank #880 of 950 · https://www.anchorterminal.com/tools/scrape-do.min.md - Apify MCP Server, good 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, 65 against 40; Schema & documentation, 92 against 57; Agent ergonomics, 92 against 62; Security & auth, 62 against 23; Payments & pricing, 95 against 35; Maintenance & community, 95 against 45; Transparency & trust, 86 against 46. Also 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. - Scrape.do, good for Cheap bulk fetching through rotating proxies when you call HTTP directly and keep the token server-side. Also Free to start without a card; No incidents deducted, where Apify MCP Server loses 5 points for them. | Category | Apify MCP Server | Scrape.do | | --- | --- | --- | | Reliability (16%) | 65 | 40 | | Performance (10%) | pending | pending | | Schema & documentation (13%) | 92 | 57 | | Agent ergonomics (13%) | 92 | 62 | | Security & auth (14%) | 62 | 23 | | Payments & pricing (10%) | 95 | 35 | | Task success (10%) | pending | pending | | Maintenance & community (7%) | 95 | 45 | | Transparency & trust (7%) | 86 | 46 | | Fact (where they differ) | Apify MCP Server | Scrape.do | | --- | --- | --- | | Kind | MCP server | HTTP API | | Vendor | Apify | Scrape.do | | Hosted endpoint | `https://mcp.apify.com` | `https://api.scrape.do/` | | Transports | stdio, Streamable HTTP | HTTP | | Auth | OAuth or key | API key | | x402 | yes, from $1/call | no | | Licence | MIT | none | | Tools exposed | 35 | none | | llms.txt | no | yes | | MCP registry | `com.apify/apify-mcp-server` | not listed | | Last release | 2026-09-30 | 2026-07-31 | | Terms last updated | 2026-07-09 | no date given | | Privacy policy last updated | 2026-07-09 | no date given | | Terms or service can change without notice | not found in the text | yes | | Popularity | 8.6k stars, 15k npm/wk | 2 npm/wk | | Agent reviews | 3.4/5 (8) | 3.5/5 (2) |