Head to head · Scraping · October 2026 research run
Scrapling vs XCrawl
Scrapling scores 68.5 (B) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category. Both do scraping.
Best web scraping and crawling APIs for AI agents · All 601 scrapers comparisons
Which one, for what
Best for Agents that need to fetch and drive pages locally, including JavaScript-heavy or bot-protected ones, without a hosted scraping bill.
Ahead on
- Reliability, 65 against 15
- Schema & documentation, 81 against 35
- Agent ergonomics, 71 against 59
- Security & auth, 39 against 18
- Payments & pricing, 90 against 30
- Maintenance & community, 93 against 17
- Transparency & trust, 52 against 43
Also in its favour
- No key needed to call it
- Open source
Watch for
Version 0.5.1 with a Beta classifier. v0.4.15, v0.5 and v0.5.1 each carried breaking changes, the last in a patch release
XCrawl F
Best for A general scrape, crawl, map and SERP API for agents, with 35 site-specific data endpoints.
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
Xcrawl LLC is named with no state, registration number or address, and the terms name no governing law
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.
Maintenance & community Scrapling +76
Scrapling 93
v0.5.1 tagged and released on 4 November 2026, 14 days before 18 November (30). v0.4.15 (23 August), v0.5 (17 October in the changelog, tagged 18 October) and v0.5.1 (4 November), three in the 90 days (20). The v0.5.1 notes credit about a dozen pull requests from outside contributors. Five issues and 18 pull requests were open on 18 November, and the issue template points to GitHub Discussions and a Discord (20 of 25). The official MCP registry lists io.github.D4Vinci/Scrapling as active, with versions from 0.4.1 (27 February 2026) to 0.5.1 (4 November 2026) (15). Tests and code-quality workflows, PyPI trusted publishing, and current dependencies such as Playwright 1.62. Run results unread (8 of 10). 30 + 20 + 20 + 15 + 8 = 93.
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). Nothing dated in the 90 days from 22 August 2026 (0 of 20). We couldn't read GitHub issues. There is no public changelog, and support is by email, Telegram, WhatsApp and Microsoft Teams, with a 24-hour reply promised in the footer (5 of 15). Official Python and Node.js SDKs, unchanged for seven months (10 of 15). The SDK repository has 3 commits, no tests and no CI. Dependencies are current (2 of 10). Total 17.
Payments & pricing Scrapling +60
Scrapling 90
Free, self-hosted software under BSD-3-Clause with nothing to buy, read with the self-hosted rule. No payment protocol (0), nothing to price (30), free (30), no signup or key (30). 0 + 30 + 30 + 30 = 90.
XCrawl 30
No x402, MPP or L402 (0). The pricing page's plan table and credit table did not appear in the served page, and the docs give credit costs only in examples (1 for a plain scrape, 2 for a search), so pricing is scored absent (0 of 30, unchecked). 1,000 free credits on signup with no card (30). A person signs up in a browser at dash.xcrawl.com to get a key (0). Total 30.
Reliability Scrapling +50
Scrapling 65
Read on the local-software lines, since the MCP server runs on the user's machine over stdio or a self-run HTTP port. Installs from PyPI (scrapling[ai]) or Docker (pyd4vinci/scrapling, ghcr.io/d4vinci/scrapling), with Python 3.10 or later and 3.10 to 3.13 in the classifiers (20). tests.yml runs tox on Python 3.10 to 3.13 on macOS for pushes and pull requests to main and dev, and the repository holds about 1,390 test functions, 19 test files for the MCP tools among them. Run results on GitHub couldn't be read on 18 November, so passing on main is unchecked (15 of 25). Five issues were open on 18 November 2026 against 104,200 stars, the oldest from 24 October 2025, and two of them had a reply. The v0.5.1 notes credit fixes from outside contributors and close reported issues such as #540 (20 of 25). Breaking changes carry a warning and a migration guide in the changelog, but v0.5.1 broke remote browser connections in a patch release (10 of 15). Version 0.5.1 with a Development Status 4 Beta classifier (0). 20 + 15 + 20 + 10 + 0 = 65.
XCrawl 15
No status page found on xcrawl.com or docs.xcrawl.com (0 of 20) and no readable incident history (5 of 30). No rate limits with numbers. The pricing page says only that Scale plans get higher rate limits (0 of 15). No 429 or overload guidance in the docs. The Python SDK retries 500, 502, 503 and 504 with backoff, but not 429 (0 of 15). The terms mention a Service Level Agreement "if applicable", and none is published (0 of 10). The API is sold publicly with no beta label (10). Total 15.
Schema & documentation Scrapling +46
Scrapling 81
Read from the server source (scrapling/core/ai/server.py) and docs/ai/mcp-server.md in the repository. Every tool takes typed Pydantic inputs, so tools/list carries JSON Schema for each (25). No llms.txt in the repository, and scrapling.readthedocs.io answers 404 for /llms.txt. The docs are Markdown in the repository, each docs page links its Markdown source, and an agent skill ships in agent-skill/ (5). Server instructions say when to use HTTP and when a browser, one-shot tools against sessions, and when to close a session, and each tool states its purpose in one or two sentences, but few say when not to use them (15). Literal enums for extraction type, HTTP method, wait states, load states and screenshot type, ranges such as limit 1 to 200 and duration_ms 100 to 5,000, and discriminated action types. Proxy and cookie fields take free dictionaries (12). The MCP guide has example prompts and setup for each client. Errors come back as MCP tool errors with the exception's message, and tests cover their wording, but no error list is documented (9). A dated changelog for every release from v0.1 (13 October 2024) to v0.5.1 (4 November 2026), and the server reports its version (15). 25 + 5 + 15 + 12 + 9 + 15 = 81.
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). llms.txt returns 404. The docs have "Copy page" buttons, and the xcrawl-skills repository has Markdown skill files for agents (5 of 10). Each API reference page states what the endpoint does, with no guidance on when not to use it (8 of 20). Parameter tables give types, required flags, defaults and enums for formats, device and wait_until. cookies and headers are free maps (11 of 15). Request and response examples on every reference page, but no error responses or codes documented outside the MCP troubleshooting table (6 of 15). Versioned /v1 paths and no changelog (5 of 15). Total 35.
Security & auth Scrapling +21
Scrapling 39
Read as local software with an optional HTTP transport. stdio needs no credential. Over HTTP the server refuses to start without a token or an explicit --no-auth, and accepts one shared bearer token with no scopes, rotated by restarting (15). Annotations let a client gate the destructive tools, and follow_redirects defaults to safe, which blocks redirects to private addresses. A direct request to localhost or a private address is not refused, and there is no read-only mode (10). Hidden elements, aria-hidden content, zero-width characters, comments and template tags are stripped by default before page text reaches the model, as documented in the MCP guide. The vendor's claim, untested by us (10). Browser sessions record network history the agent and operator can read back. No call log (4). No SECURITY.md, disclosure address or bug bounty in the repository, and GitHub's advisory page couldn't be read (0). 15 + 10 + 10 + 4 + 0 = 39.
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). The recommended hosted MCP setup puts the key in the URL path, so less 10, read the way the checklist reads a key in a query string (10 of 30). The API only reads third-party pages and has no destructive account actions, but there is no read-only or least-privilege key (5 of 20). No prompt-injection guidance in the docs or the skills (0 of 15). Each response reports credits used, and xcrawl_key_status gives the balance, with no request log found (3 of 15). No security.txt, disclosure policy or bug bounty. The ISO 27001 badge on the home page links to no certificate or security page (0 of 20). Total 18.
Agent ergonomics Scrapling +12
Scrapling 71
17 tools, and v0.5 and v0.5.1 both shortened the descriptions. No toolsets or read-only subset (15). css_selector narrows fetch output, extraction can be Markdown, HTML, text or an ARIA snapshot with search, main_content_only is on by default, and network history is paged with a cursor and a limit of 1 to 200 (18). Failures from bad input, the browser and curl come back as tool errors with the message, which the v0.5 notes say were made clearer. No error codes an agent can branch on (12). Every tool carries annotations, read-only for fetches and lists and destructive for actions, JavaScript and state files. HTTP requests retry three times by default with a one-second wait (17). Only url is required for a fetch, with schema defaults. One language, Python, plus a CLI and Docker (9). 15 + 18 + 12 + 17 + 9 = 71.
XCrawl 59
7 MCP tools per the Claude Code guide, compact by name and description, though the definitions themselves couldn't be read (22 of 25). Output formats, only_main_content, a search limit of 1 to 100, and crawl limit, depth and include or exclude regex keep responses sized (16 of 20). The SDKs raise errors with a code, status and request_id, but the docs list no error codes or recovery steps (5 of 20). Async jobs return IDs for polling and webhooks, with no idempotency keys or MCP annotations found (3 of 20). Only url or query is required, and Python and Node.js SDKs exist, but skip_tls_verification defaults to true (13 of 15). Total 59.
Score by category
| Category | Weight | Scrapling | XCrawl | Edge |
|---|---|---|---|---|
| Reliability | 16% | 65 | 15 | Scrapling +50 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 81 | 35 | Scrapling +46 |
| Agent ergonomics | 13% | 71 | 59 | Scrapling +12 |
| Security & auth | 14% | 39 | 18 | Scrapling +21 |
| Payments & pricing | 10% | 90 | 30 | Scrapling +60 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 93 | 17 | Scrapling +76 |
| Transparency & trust | 7% | 52 | 43 | Scrapling +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.5/100 | F 30.4/100 |
Facts side by side
| Fact | Scrapling | XCrawl |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Karim Shoair | XCrawl |
| Hosted endpoint | no (local only) | https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp |
| Transports | stdio, Streamable HTTP | Streamable HTTP, stdio |
| Auth | None | API key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | BSD-3-Clause | none |
| Tools exposed | 17 | 7 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| MCP registry | io.github.D4Vinci/Scrapling | not listed |
| Last release | 2026-11-04 | 2026-04-13 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | no date given |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 104k stars | none |
How the scores have moved
XCrawl
No score change since it was listed.
Verdicts
Scrapling
Scrapling's MCP server gives agents 17 typed tools with read-only and destructive hints, output trimming by CSS selector and default stripping of hidden page text. It is pre-1.0 (0.5.1, Beta), breaks interfaces between minor releases, has no security policy, and its tools tell the model to work through CAPTCHAs.
XCrawl
A scrape, search, map and crawl API with 7 MCP tools, MIT Python and Node.js SDKs and 1,000 free credits without a card. Xcrawl LLC gives no address or registration. There is no OpenAPI spec, status page, rate limit, error reference or changelog, plan prices did not render for us, and the hosted MCP key travels in the URL.
Before you call either
Scrapling
- Start with
make_requestand move tobrowser_fetch_onceonly when the page needs JavaScript or blocks plain HTTP - Pass
css_selectoron fetch tools to cut output. Snapshots need one match or no selector - Read network history with
browser_network_requestsbeforeclose_session, since closing a session drops it - Check the target site's terms and robots.txt yourself. The MCP tools don't read robots.txt, only the spiders do
- If you run the server over HTTP, set
SCRAPLING_MCP_AUTH_TOKENand keep it behind TLS. The token travels in clear over plain HTTP
XCrawl
- Use the
npx xcrawl-mcpsetup withXCRAWL_API_KEYin the environment rather than the hosted URL, which puts the key in the path - Set
skip_tls_verificationto false when the page's certificate matters, because scrape and crawl default it to true - Set
crawler.limitandmax_depthon every crawl, since the defaults are 100 pages and depth 3 - Call xcrawl_key_status before a large crawl, because the docs give no credit table to estimate the cost
- Treat scraped Markdown and JSON as untrusted page content, since the docs give no prompt-injection guidance
Questions
Which is better for AI agents, Scrapling or XCrawl?
Scrapling scores 68.5 (B) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category.
Do Scrapling and XCrawl need an API key?
Scrapling needs no key. XCrawl needs an API key.
Can an agent call Scrapling and XCrawl without installing anything?
Scrapling runs on your own machine, with no hosted endpoint listed. XCrawl has a hosted endpoint at https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp.
Are Scrapling and XCrawl open source?
Scrapling is open source (BSD-3-Clause). No open-source release is listed for XCrawl.
Other comparisons with Scrapling or XCrawl
- Bright Data vs Scrapling
- Bright Data vs XCrawl
- BrowserAct vs Scrapling
- BrowserAct vs XCrawl
- Context.dev vs Scrapling
- Context.dev vs XCrawl
- Crawl4AI vs Scrapling
- Crawl4AI vs XCrawl
- fastCRW vs Scrapling
- fastCRW vs XCrawl
- Decodo Web Data API vs Scrapling
- Decodo Web Data API vs XCrawl
- Jina Reader vs Scrapling
- Jina Reader vs XCrawl
- Microlink vs Scrapling
- Microlink vs XCrawl
- Olostep vs Scrapling
- Olostep vs XCrawl
- Outcrawl vs Scrapling
- Outcrawl vs XCrawl
- Oxylabs Web Scraper API vs Scrapling
- Oxylabs Web Scraper API vs XCrawl
- Scrape.do vs Scrapling
- Scrape.do vs XCrawl
- ScrapeGraphAI vs Scrapling
- ScrapeGraphAI vs XCrawl
- Scrapeless vs Scrapling
- Scrapeless vs XCrawl
- ScraperAPI vs Scrapling
- ScraperAPI vs XCrawl
- Scrapewise vs Scrapling
- Scrapewise vs XCrawl
- Scrapfly vs Scrapling
- Scrapfly vs XCrawl
- ScrapingAnt vs Scrapling
- ScrapingAnt vs XCrawl
- ScrapingBee vs Scrapling
- ScrapingBee vs XCrawl
- Scrapingdog vs Scrapling
- Scrapingdog vs XCrawl
- Scrapling vs Spider
- Scrapling vs WebScraping.AI
- Scrapling vs ZenRows
- Scrapling vs Zyte API
- Spider vs XCrawl
- WebScraping.AI vs XCrawl
- XCrawl vs ZenRows
- XCrawl vs Zyte API
- Firecrawl MCP vs XCrawl
- Diffbot vs Scrapling
- Diffbot vs XCrawl
- Firecrawl MCP vs Scrapling
- Nexscope vs Scrapling
- Nexscope vs XCrawl
- Qovia vs Scrapling
- Qovia vs XCrawl
- ScrapeAtlas vs Scrapling
- ScrapeAtlas vs XCrawl
- Scrapling vs SoldFetch
- SoldFetch vs XCrawl
- Apify MCP Server vs Scrapling
- Apify MCP Server vs XCrawl
- jevcrawl vs Scrapling
- jevcrawl vs XCrawl
- ScrapeOps Proxy API Aggregator vs Scrapling
- ScrapeOps Proxy API Aggregator vs XCrawl
Machine-readable
- This page as Markdown
/compare/scrapling-vs-xcrawl.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapling.json·/api/v1/tools/xcrawl.json - From a terminal
anchor compare scrapling xcrawl(the CLI) - Over MCP
compare_tools {"a": "scrapling", "b": "xcrawl"}at/mcp, no key