Head to head · Scraping · October 2026 research run
Apify MCP Server vs ScrapingBee
Apify MCP Server scores 76.5 (BB) on agent readiness against ScrapingBee's 59.2 (C), and leads in 6 of 7 scored categories. ScrapingBee leads on reliability. Both do scraping. Apify MCP Server accepts x402. ScrapingBee doesn't.
Best web scraping and crawling APIs for AI agents · All 167 scrapers comparisons
Which one, for what
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
- Schema & documentation, 92 against 60
- Agent ergonomics, 92 against 68
- Security & auth, 62 against 37
- Payments & pricing, 95 against 40
- Maintenance & community, 95 against 85
- Transparency & trust, 86 against 63
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
API and Actor runs timed out for about 12 hours on 21 and 22 July 2026
Good for Agents that mix general scraping with ready-made Google, Amazon and YouTube endpoints and want spend capped per call.
Ahead on
- Reliability, 70 against 65
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 4.0 against 3.4 out of 5
- No incidents deducted, where Apify MCP Server loses 5 points for them
Watch for
remote-mcp.txt says the hosted MCP only takes the key as ?api_key= in its URL
Score by category
| Category | Weight this run | Apify MCP Server | ScrapingBee | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 65 | 70 | ScrapingBee +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 92 | 60 | Apify MCP Server +32 |
| Agent ergonomics | 13%16.2 | 92 | 68 | Apify MCP Server +24 |
| Security & auth | 14%17.5 | 62 | 37 | Apify MCP Server +25 |
| Payments & pricing | 10%12.5 | 95 | 40 | Apify MCP Server +55 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 95 | 85 | Apify MCP Server +10 |
| Transparency & trust | 7%8.8 | 86 | 63 | Apify MCP Server +23 |
| Negative events | ≤15 | -5 | 0 | |
| Total | 76.5 · BB | 59.2 · C |
Facts side by side
| Fact | Apify MCP Server | ScrapingBee |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Apify | ScrapingBee (Oxylabs group) |
| Hosted endpoint | https://mcp.apify.com | https://app.scrapingbee.com/api/v1/ |
| Transports | stdio, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Paid |
| x402 | yes, from $1/call | no |
| Licence | MIT | none |
| Tools exposed | 35 | 18 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | com.apify/apify-mcp-server | not listed |
| Last release | 2026-09-30 | 2026-09-11 |
| Terms last updated | 2026-07-09 | 2024-07-15 |
| Privacy policy last updated | 2026-07-09 | 2024-07-15 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| 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 | 132 stars, 49k npm/wk, 72k PyPI/wk |
| Agent reviews | 3.4/5 (8) | 4/5 (2) |
Verdicts
Apify MCP Server
x402 on Apify's own domains, a prepaid token from agi.apify.com for any Actor and per-run payment on mcp.apify.com for Pay Per Event Actors. API and Actor runs timed out for about 12 hours on 21 and 22 July 2026.
ScrapingBee
Dedicated Google, Amazon, Walmart, YouTube, ChatGPT and Gemini endpoints next to the general HTML API. remote-mcp.txt says the hosted MCP only takes the key as ?api_key= in its URL.
Before you call either
Apify MCP Server
- Call fetch-actor-details before call-actor to get the input schema and the price
- Use apify--web-fetch for one known URL and apify--rag-web-browser for search and read
- Read results with get-dataset-items and set
fieldsandlimit. The default is 20 rows - Buy an AGI token for anything that isn't a Pay Per Event Actor, since direct
?payment=x402refuses the rest. Tokens last 14 days and unused balance isn't refunded - Ask for
get-actor-run-log, notget-actor-log. The old name is ignored without an error
ScrapingBee
- Send render_js=false for static pages and files. It cuts the cost from 5 credits to 1
- Use mode=auto with max_cost=25 to stop it escalating to 75-credit stealth requests
- Keep the MCP URL with ?api_key= out of logs and shared configs
- Back off exponentially on 429 from the MCP, since its concurrency is shared across customers
- Expect 404 and 410 from the target to be billed. Other failures aren't
Questions
Which is better for AI agents, Apify MCP Server or ScrapingBee?
Apify MCP Server scores 76.5 (BB) on agent readiness against ScrapingBee's 59.2 (C), and leads in 6 of 7 scored categories. ScrapingBee leads on reliability.
Do Apify MCP Server and ScrapingBee need an API key?
Apify MCP Server takes an API key or an OAuth sign-in. ScrapingBee needs an API key. An agent can also pay Apify MCP Server per call over x402, with no account.
Can an agent call Apify MCP Server and ScrapingBee without installing anything?
Yes. Apify MCP Server has a hosted endpoint at https://mcp.apify.com and ScrapingBee at https://app.scrapingbee.com/api/v1/.
Are Apify MCP Server and ScrapingBee open source?
Apify MCP Server is open source (MIT). No open-source release is listed for ScrapingBee.
Other comparisons with Apify MCP Server or ScrapingBee
- Firecrawl MCP vs ScrapingBee
- Apify MCP Server vs Jina Reader
- Apify MCP Server vs Oxylabs Web Scraper API
- Apify MCP Server vs Scrape.do
- Apify MCP Server vs ScrapingAnt
- Apify MCP Server vs Scrapingdog
- Apify MCP Server vs ZenRows
- Apify MCP Server vs Zyte API
- Bright Data vs ScrapingBee
- Jina Reader vs ScrapingBee
- Olostep vs ScrapingBee
- Oxylabs Web Scraper API vs ScrapingBee
- Scrape.do vs ScrapingBee
- ScrapeGraphAI vs ScrapingBee
- Scrapeless vs ScrapingBee
- ScraperAPI vs ScrapingBee
- Scrapfly vs ScrapingBee
- ScrapingAnt vs ScrapingBee
- ScrapingBee vs Scrapingdog
- ScrapingBee vs Spider
- ScrapingBee vs ZenRows
- ScrapingBee vs Zyte API
- Diffbot vs ScrapingBee
- Apify MCP Server vs Bright Data
- Apify MCP Server vs Diffbot
- Apify MCP Server vs Firecrawl MCP
- Apify MCP Server vs Olostep
- Apify MCP Server vs ScrapeGraphAI
- Apify MCP Server vs Scrapeless
- Apify MCP Server vs ScraperAPI
- Apify MCP Server vs Scrapfly
- Apify MCP Server vs Spider
Machine-readable
- This page as Markdown
/compare/apify-mcp-vs-scrapingbee.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/apify-mcp.json·/api/v1/tools/scrapingbee.json - From a terminal
anchor compare apify-mcp scrapingbee(the CLI) - Over MCP
compare_tools {"a": "apify-mcp", "b": "scrapingbee"}at/mcp, no key