# Apify MCP Server vs ScrapingBee (slim)

> Apify scores 76.5 (BB) to ScrapingBee's 59.2 (C) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingbee.md (~2,750 tokens) · this version ~780 tokens · JSON https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingbee.json · canonical https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingbee
- 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 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.

- Apify MCP Server: BB 76.5, rank #28 of 950 · https://www.anchorterminal.com/tools/apify-mcp.min.md
- ScrapingBee: C 59.2, rank #557 of 950 · https://www.anchorterminal.com/tools/scrapingbee.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 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 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.
- ScrapingBee, 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 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.

| Category | Apify MCP Server | ScrapingBee |
| --- | --- | --- |
| Reliability (16%) | 65 | 70 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 92 | 60 |
| Agent ergonomics (13%) | 92 | 68 |
| Security & auth (14%) | 62 | 37 |
| Payments & pricing (10%) | 95 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 95 | 85 |
| Transparency & trust (7%) | 86 | 63 |

| Fact (where they differ) | 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 |
| 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 |
| Terms restrict automated access | yes | 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) |