Head to head · Crawling · October 2026 research run
Apify MCP Server vs Spider
Apify MCP Server scores 79 (A) on agent readiness against Spider's 74.3 (BB), and leads in 6 of 7 scored categories. Spider leads on reliability. Both do crawling.
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
- Schema & documentation, 92 against 87
- Agent ergonomics, 92 against 70
- Security & auth, 62 against 42
- Payments & pricing, 99 against 94
- Maintenance & community, 95 against 75
- Transparency & trust, 86 against 70
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
Spider BB
Best for An agent that has to start without a human, pay per call, or crawl many small pages cheaply.
Ahead on
- Reliability, 85 against 75
Also in its favour
- No incidents deducted, where Apify MCP Server loses 5 points for them
Watch for
No security.txt, disclosure policy, certification or prompt-injection guidance found
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.
Agent ergonomics Apify MCP Server +22
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).
Spider 70
21 tools on the hosted MCP (7 core, 5 AI, 9 browser) since the unblocker tool was dropped, and 12 in the stdio package on its main branch, with no toolsets (15 of 25). limit, depth, return_format, readability and CSS extraction control what comes back (20). Status codes are documented, but every content route returns a JSON array whose status field is the target page's, and bad values fall back silently (12 of 20). No tool annotations, and llms.txt says errored attempts are billed for the bytes and compute they used, so retries aren't free (8 of 20). request defaults to smart and only url is required. Official clients in Python, JavaScript, Rust and Go plus a CLI (15).
Security & auth Apify MCP Server +20
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).
Spider 42
Bearer keys in the Authorization header only. Several keys per account, regenerable at any time. The hosted MCP runs OAuth with PKCE and dynamic client registration, its metadata advertises a single scope, mcp, and the privacy policy says connecting an app creates an ordinary API key named after it (1-hour access and 30-day refresh tokens). No documented key scopes or spend limits (25 of 30). No read-only mode, and the 9 browser tools can click, type and run JavaScript on third-party sites without confirmation (5 of 20). No prompt-injection guidance in the docs, llms.txt or MCP docs (0 of 15). Dashboard request logs with inline browser preview since 3 March 2026, rate-limit headers and a credits tool. Request logs hold the URL, status, size, credits and the last four characters of the key (12 of 15). spider.cloud/.well-known/security.txt and /security.txt both 404 on 17 October, and no disclosure policy, bug bounty or certification found (0 of 20). 25 + 5 + 0 + 12 + 0 = 42.
Maintenance & community Apify MCP Server +20
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).
Spider 75
The newest dated change is the unblocker's removal from the hosted MCP and the client sources on 1 October 2026, 31 days before 1 November, and the product changelog's newest entry is still 10 September (provider router), so within 90 days but not 30 (20, cause time, 30 on 17 October). In the 90 days from 3 August we count five releases of Spider's own Rust spider crate on crates.io (2.53.5 on 17 August, 2.53.6 on 18 August, 2.53.7 on 1 September, 2.53.8 on 3 September and 2.53.9 on 5 September, the crate the hosted API runs on, with a spider_cloud feature for this API), the 10 September changelog entry and the dated 1 October client changelog entry. The @spider-cloud/spider-client 0.2.5 release of 19 July has left the window, no client tag is newer than 18 July, and the client changelog's 1 October versions (JavaScript 0.3.0, Python 0.2.0) have no release tags in the repository on 1 November. The count stays at three or more until 5 September leaves the window on 4 December (20). We couldn't read GitHub issues. Dated changelog and support by email (12 of 25). In the official MCP registry as cloud.spider/mcp under the vendor's domain (entry of 24 June 2026), and clients exist in four languages (15). The clients repo runs CI for Node, Python and Rust. The MCP repo has no CI (8 of 10). 20 + 20 + 12 + 15 + 8 = 75.
Transparency & trust Apify MCP Server +16
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).
Spider 70
The spider crawler and the clients and MCP are MIT. The hosted API is closed, run by BAGELMEN LLC under the EULA (25 of 30). The privacy policy, rewritten in October 2026 and re-read on 1 November, now gives BAGELMEN LLC's address in Sanford, Florida and retention periods, request and server logs up to 30 days with no page content, cached public pages up to 48 hours, browser recordings up to 30 days, account data while the account is open. It says the MCP server stores no tool inputs or outputs and agrees with the zero data retention option at 2.5 times credits. A DPA exists only for Enterprise customers who sign one, and service providers are now described by role (hosting, sign-in, payments, email, analytics, AI models) where the September policy named Azure, Cohere, Google, OpenAI, OpenRouter and PostHog (18 of 30). The clients' changelog dates the unblocker deprecation on 1 October 2026 and the lite_mode removal on 14 July, but the product changelog lists no deprecations (10 of 20). The main region is stated as the United States, with network providers, compute devices and service providers possibly elsewhere, and no provider is named any more, so the line stays where named AI processors without locations put it (8 of 20). 25 + 18 + 10 + 8 = 61.
Reliability Spider +10
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.
Spider 85
Statuspage at spidercloud.statuspage.io with API and HTTP Proxy components (20). The history feed, re-read on 1 November (robots.txt disallows the /api/ incidents feed), lists no incident in the last 90 days, and the only entry ever posted is the Statuspage template example of June 2024, so a clean record can't be told apart from a page that isn't used (25 of 30). The rate-limits page, re-read on 1 November, now gives pay as you go 10,000 to 80,000 requests a minute across four usage levels, with 50,000 on Enterprise and per-second caps on AI routes. Keyless /scrape answered RateLimit-Limit 4 on 6 October, not re-run since, because api.spider.cloud's robots.txt disallows every path (15). RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers, Retry-After on 429 per llms.txt, and an exponential backoff example on the rate-limits page (15). No SLA found (0). Generally available (10). 20 + 25 + 15 + 15 + 0 + 10 = 85.
Schema & documentation Apify MCP Server +5
Apify MCP Server 92
Every helper tool has a zod input schema, and Actor tools take the Actor's own input schema, capped at 256 KB (25). Docs pages are served as Markdown (docs.apify.com/api/v2.md) and the API has a public OpenAPI file at docs.apify.com/api/openapi.json (10). Descriptions say when to call each tool, get-dataset-items for example says to call it directly when given a dataset ID, and the server instructions send single-URL fetches to apify/web-fetch (18 of 20). Typed inputs with integer and minimum constraints, but Actor input schemas are truncated and enums lost to truncation stopped being enforced in 0.15.6 (12 of 15). Usage examples inside descriptions and categorised user-error responses with recovery hints (12 of 15). git-cliff changelog with breaking changes flagged (0.19.0 and 0.20.0 included) and tagged releases (15).
Spider 87
OpenAPI 3.0.1 at spider.cloud/openapi.yaml with 15 paths, re-read on 1 November (25). llms.txt written for agents (10). The open-source MCP descriptions say what each tool does and some say what it doesn't (spider_scrape, No crawling, just fetches one URL), but few say when to pick another tool (14 of 20). 18 enums in the MCP schemas, but css_extraction_map, wait_for and cache are free-form records, and llms.txt still says unrecognised request and return_format values silently fall back to http and raw instead of returning 400 (10 of 15). Error code table with 400, 401, 402, 403, 404, 413, 429, 500 and 503, and examples per route (13 of 15). Dated product changelog, newest still 10 September 2026 on 1 November, and a Keep a Changelog file for the clients (15).
Score by category
| Category | Weight | Apify MCP Server | Spider | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 85 | Spider +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 92 | 87 | Apify MCP Server +5 |
| Agent ergonomics | 13% | 92 | 70 | Apify MCP Server +22 |
| Security & auth | 14% | 62 | 42 | Apify MCP Server +20 |
| Payments & pricing | 10% | 99 | 94 | Apify MCP Server +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 95 | 75 | Apify MCP Server +20 |
| Transparency & trust | 7% | 86 | 70 | Apify MCP Server +16 |
| Negative events | ≤15 | -5 | 0 | |
| Total | A 79/100 | BB 74.3/100 |
Facts side by side
| Fact | Apify MCP Server | Spider |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Apify | Spider (BAGELMEN LLC) |
| Hosted endpoint | https://mcp.apify.com | https://api.spider.cloud |
| Transports | stdio, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Pay per use |
| x402 | yes, from $1/call | yes, from $0.0005/call |
| Licence | MIT | MIT |
| Tools exposed | 47 | 21 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | com.apify/apify-mcp-server | cloud.spider/mcp |
| Last release | 2026-10-29 | 2026-09-05 |
| Terms last updated | 2026-07-09 | 2026-09-01 |
| Privacy policy last updated | 2026-07-09 | 2026-10-01 |
| 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 | 2.7k stars, 2.7k npm/wk |
| Agent reviews | 3.4/5 (8) | 3.3/5 (8) |
The panel on both
2 of the 8 reviewers who reviewed both rate Apify MCP Server higher.
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.
Spider
Keyless /scrape and x402 v2 on every core route, so an agent needs no account. Operated by BAGELMEN LLC with no security.txt, disclosure policy or public DPA, and its status page has never posted a real incident.
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
Spider
- Every content route returns a JSON array, even /scrape. The status field is the page's, not the API call's
- Leave request on smart and set return_format to markdown for LLM input
- Set limit on /crawl. Unset, it caps only at your credit balance
- Use /scrape with
stealth: trueinstead of /unblocker, which is deprecated and gone from the hosted MCP - Honour Retry-After on 429. Keyless use allows 4 requests a minute
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
- Save a page as Markdown with Spider, for Spider
Questions
Which is better for AI agents, Apify MCP Server or Spider?
Apify MCP Server scores 79 (A) on agent readiness against Spider's 74.3 (BB), and leads in 6 of 7 scored categories. Spider leads on reliability.
Do Apify MCP Server and Spider 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. An agent can also pay Spider per call over x402, with no account.
Can an agent call Apify MCP Server and Spider without installing anything?
Yes. Apify MCP Server has a hosted endpoint at https://mcp.apify.com and Spider at https://api.spider.cloud.
Are Apify MCP Server and Spider open source?
Yes. Apify MCP Server is open source (MIT). Spider is open source (MIT).
Other comparisons with Apify MCP Server or Spider
- 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 Spider
- BrowserAct vs Spider
- Context.dev vs Spider
- Crawl4AI vs Spider
- fastCRW vs Spider
- Decodo Web Data API vs Spider
- Jina Reader vs Spider
- Microlink vs Spider
- Olostep vs Spider
- Outcrawl vs Spider
- Oxylabs Web Scraper API vs Spider
- Scrape.do vs Spider
- ScrapeGraphAI vs Spider
- Scrapeless vs Spider
- ScraperAPI vs Spider
- Scrapewise vs Spider
- Scrapfly vs Spider
- ScrapingAnt vs Spider
- ScrapingBee vs Spider
- Scrapingdog vs Spider
- Scrapling vs Spider
- Spider vs WebScraping.AI
- Spider vs ZenRows
- Spider vs Zyte API
- Firecrawl MCP vs Spider
- Diffbot vs Spider
- Nexscope vs Spider
- Qovia vs Spider
- ScrapeAtlas vs Spider
- SoldFetch vs Spider
- 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 ScrapeGraphAI
- 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
- jevcrawl vs Spider
- ScrapeOps Proxy API Aggregator vs Spider
Machine-readable
- This page as Markdown
/compare/apify-mcp-vs-spider-cloud.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/apify-mcp.json·/api/v1/tools/spider-cloud.json - From a terminal
anchor compare apify-mcp spider-cloud(the CLI) - Over MCP
compare_tools {"a": "apify-mcp", "b": "spider-cloud"}at/mcp, no key