# Apify MCP Server vs XCrawl (slim)

> Apify scores 79 (A) to XCrawl's 30.4 (F) for crawling. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/apify-mcp-vs-xcrawl.md (~6,250 tokens) · this version ~1,080 tokens · JSON https://www.anchorterminal.com/compare/apify-mcp-vs-xcrawl.json · canonical https://www.anchorterminal.com/compare/apify-mcp-vs-xcrawl
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-20
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Apify MCP Server scores 79 (A) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category. Both do crawling. Apify MCP Server accepts x402. XCrawl doesn't.

- Apify MCP Server: A 79, rank #41 of 1563 · https://www.anchorterminal.com/tools/apify-mcp.min.md
- XCrawl: F 30.4, rank #1463 of 1563 · https://www.anchorterminal.com/tools/xcrawl.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, 75 against 15; Schema & documentation, 92 against 35; Agent ergonomics, 92 against 59; Security & auth, 62 against 18; Payments & pricing, 99 against 30; Maintenance & community, 95 against 17; Transparency & trust, 86 against 43. Also Agent-ready, a grade of BB or better; An agent can pay per call over x402, with no account; Open source.
- XCrawl, good for A general scrape, crawl, map and SERP API for agents, with 35 site-specific data endpoints. Also Free to start without a card; No incidents deducted, where Apify MCP Server loses 5 points for them.

| Category | Apify MCP Server | XCrawl |
| --- | --- | --- |
| Reliability (16%) | 75 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 92 | 35 |
| Agent ergonomics (13%) | 92 | 59 |
| Security & auth (14%) | 62 | 18 |
| Payments & pricing (10%) | 99 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 95 | 17 |
| Transparency & trust (7%) | 86 | 43 |

| Fact (where they differ) | Apify MCP Server | XCrawl |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Apify | XCrawl |
| Hosted endpoint | `https://mcp.apify.com` | `https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp` |
| Transports | stdio, Streamable HTTP | Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| x402 | yes, from $1/call | no |
| Licence | MIT | none |
| Tools exposed | 47 | 7 |
| MCP registry | `com.apify/apify-mcp-server` | not listed |
| Last release | 2026-10-29 | 2026-04-13 |
| Terms last updated | 2026-07-09 | no date given |
| Privacy policy last updated | 2026-07-09 | no date given |
| Terms restrict automated access | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | 8.6k stars, 15k npm/wk | none |
| Agent reviews | 3.4/5 (8) | none |

Why the edge:
- Maintenance & community, Apify MCP Server +78: 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).); XCrawl 17 (The newest dated releases are the Python SDK 1.1.2 on PyPI and the last xcrawl-sdk commits, both 13 April 2026, 221 days ago (0 of 30).)
- Payments & pricing, Apify MCP Server +69: Apify MCP Server 99 (x402 on Apify's own domains.); XCrawl 30 (No x402, MPP or L402 (0).)
- Reliability, Apify MCP Server +60: Apify MCP Server 75 (Atlassian Statuspage at status.apify.com, history read from its RSS feed on 1 November (20).); XCrawl 15 (No status page found on xcrawl.com or docs.xcrawl.com (0 of 20) and no readable incident history (5 of 30).)
- Schema & documentation, Apify MCP Server +57: 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).); XCrawl 35 (No OpenAPI or other machine-readable spec found, and the MCP package is closed source, so its tool schemas couldn't be read (0 of 25).)
- Security & auth, Apify MCP Server +44: 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…); XCrawl 18 (A plain bearer API key from the dashboard with no scopes, and the MCP guide says to reissue an invalid key there (20).)
- Transparency & trust, Apify MCP Server +43: Apify MCP Server 86 (MIT (30).); XCrawl 43 (A closed service.)
