Head to head · Extraction · October 2026 research run
Scrapling vs SoldFetch
Scrapling scores 68.5 (B) on agent readiness against SoldFetch's 45.5 (E), and leads in 5 of 7 scored categories. SoldFetch leads on security & auth. Both do extraction.
Best web scraping and crawling APIs for AI agents · All 567 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 55
- Schema & documentation, 81 against 68
- Payments & pricing, 90 against 60
- Maintenance & community, 93 against 49
- Transparency & trust, 52 against 41
Also in its favour
- No key needed to call it
- Runs on your own machine
- Open source
- No incidents deducted, where SoldFetch loses 15 points for them
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
Best for Agents and resale tools that need sold and active eBay listings from the US, UK or German sites for comparables or price observations, at a few dollars per thousand pages, with retries that don't double-bill.
Ahead on
- Security & auth, 62 against 39
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
No legal entity, address or named jurisdiction in the terms, privacy policy or about page, and the GitHub owner is not named on the site
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 +44
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.
SoldFetch 49
Closed service. The latest dated changes are commits to all three public repositories and four blog posts on 27 October 2026, and the docs sitemap dates the authentication page 30 October 2026 (30). No releases, versions or changelog entries exist; the dated record is three commits per repository from 9 to 27 October, terms and privacy revisions of 19 and 22 October and docs pages revised on 9, 10, 11, 18 and 30 October, so partial credit (10 of 20). No public changelog; support is a contact form and contact@soldfetch.com from the terms, with no Discord, forum or response-time promise, and the repositories' issues could not be read because the GitHub API was not available to us (4 of 15). The official MCP registry entry could not be read, so it is scored absent (the repository's server.json names io.github.ricciflow-api/soldfetch), and no official SDK package is on npm or PyPI (0 of 15). Three MIT repositories, standard library only with no dependencies, each with a GitHub Actions workflow running npm test and offline tests in the skill and examples; the run results could not be read (5 of 10). 30+10+4+0+5 = 49.
Payments & pricing Scrapling +30
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.
SoldFetch 60
No x402, MPP or L402 on the pricing page, terms, llms.txt or docs, and no third-party machine payment route was found; the RapidAPI alias does not take RapidAPI authentication (0). Per-unit pricing is public without a login, 1 unit per successful search page or item lookup, $9 for 2,000, $29 for 10,000 and $79 for 50,000 a month, with what is and isn't charged stated (20). Basic gives 100 units once and the terms say no payment method is required (20). A person signs in through the browser and creates a key in the dashboard; no keyless API route or programmatic key creation, and the anonymous playground is a web page for people (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Security & auth SoldFetch +23
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.
SoldFetch 62
Workspace API keys created and revoked in the dashboard, shown once and stored as digests per the privacy policy, several per workspace so one can replace another, accepted in one header only; no scopes, expiry or OAuth, and the docs say never to put a key in a URL, with no query-string option documented (20 of 30). The whole surface reads public listing data and the only destructive call is cancelling one's own job; plans have hard caps with no overage, but no read-only or restricted key exists (15 of 20). Every response carries third-party listing text. The AI agents guide, the MCP README, SECURITY.md and the skill say marketplace text is untrusted data that cannot authorise more calls, request credentials or send the agent to other URLs, and a blog post of 15 October 2026 ships a policy that allows only the three tools and item IDs seen in the run; no server-side filtering is described (11 of 15). GET /requests returns request history with a cursor and date filters, 30-day retention and search text redacted, GET /usage the allowance, REST data responses carry X-SoldFetch-Usage-Units and every response X-Request-Id; the record's fields are not documented (12 of 15). No security.txt (client error), bug bounty, SOC 2 or ISO 27001; the repositories' SECURITY.md files give a reporting route to contact@soldfetch.com (4 of 20). 20+15+11+12+4 = 62.
Schema & documentation Scrapling +13
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.
SoldFetch 68
API reading, with the MCP server described. An OpenAPI 3.1 file is published at https://soldfetch.com/api/v1/openapi.json, under a path robots.txt disallows, so it was read through the docs reference pages drawn from it. Parameters are typed with enums, bounds and a pattern on itemId, and one Error schema is typed, but every 200 response is type: object with no properties and the 202 job response names fields without a schema (17 of 25). llms.txt on the site and the docs, llms-full.txt, and Markdown twins of the docs pages (10). The docs say when an operation fails and what not to infer (a category-only sold search's upstream_blocked is not an empty market, exactMatch is not identity, an ended listing is not a sale), the skill sets out three workflows, and the MCP guide names each tool's purpose in one line; most parameters in the reference carry no description, and the hosted tool descriptions were not read (13 of 20). ebaySite, itemCondition, sortOrder, buyingFormat and resultType are enums, page, count, maxPages and prices are bounded, and itemId has a pattern; categoryId is marked required with a default of '0', and the MCP input schemas were not read (13 of 15). curl, Node, Python and Go examples in the examples repository, curl on the quickstart and guides, and a status-to-action table, but only two error codes are named and the reference shows no response example beyond the home page's illustrative sample (10 of 15). Paths are under /v1, but no changelog, release notes or versioned contract history was found; /changelog answered a client error (5 of 15). 17+10+13+13+10+5 = 68.
Transparency & trust Scrapling +11
Scrapling 52
BSD-3-Clause in LICENSE and the PyPI classifiers (30). No telemetry or usage reporting found in the source. Page traffic goes to the target sites, with optional DNS-over-HTTPS through Cloudflare. There is no privacy statement for the package (15). No deprecation policy. Breaking changes are announced in the release notes with migration guides for v0.5 and the remote-session change (8). Nothing is collected that we could find, but there is no explicit statement on telemetry (12). 30 + 15 + 8 + 12 = 65.
SoldFetch 41
Closed hosted service. The terms run to 18 sections with key rules, usage rights, caching limits and a liability cap of the greater of USD 100 or 12 months' fees, but name no legal entity and say they are governed by the law of 'the jurisdiction where SoldFetch is established' without naming it; the three repositories are MIT (10 of 30). The privacy policy (updated 22 October 2026) gives request-log retention of 7, 30 or 90 days by plan, about an hour for exports, digests for keys and cookie durations, and the docs give cache periods and 24 hours for job results; the pricing page's 30-day request logs on every plan disagrees with the policy's plan-based periods, backups have no period and no DPA was found (20 of 30). No deprecation policy or dated notices; terms 11.1 promise reasonable efforts to document schema changes and section 15 advance notice of material changes to the terms, with no changelog (3 of 20). Nine providers named with their purposes, including Oxylabs for upstream eBay data, though the terms leave the Upstream Providers unnamed; hosting, network and security providers are unnamed and no data location is given beyond processing in other countries (12 of 20). 10+20+3+12 = 45.
Reliability Scrapling +10
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.
SoldFetch 55
Hosted reading, for the REST API with the MCP server that shares its limits. SoldFetch's own status page at https://soldfetch.com/status lists ebay.com, ebay.co.uk and ebay.de as components, checked every five minutes, all operational on 3 November 2026, but keeps no incident log or uptime history, so half credit (10 of 20). No readable incident history, so the floor (5). Limits are published with numbers, 10 data requests a minute and 1 concurrent on Basic and 60 a minute and 5 concurrent on paid plans, per workspace across keys and interfaces, with a separate 60 a minute for usage and history (15). 429 is documented for workspace rate, concurrency and quota limits, 503 upstream_rate_limited carries a Retry-After header in seconds and the error schema an optional retryAfter, the docs ask for bounded backoff with jitter and name what not to retry, and REST data calls take an Idempotency-Key with a free replay for 24 hours and 409 on changed inputs; job submissions have no key, but the docs say to check existing jobs before resubmitting and allow one active job per workspace (15). No SLA on self-service plans; terms 11.2 keep uptime commitments to a signed enterprise order form (0). No beta or preview label on the API or the MCP server; three of the eight recognised eBay sites are enabled 'at launch' (10). 10+5+15+15+0+10 = 55.
Score by category
| Category | Weight | Scrapling | SoldFetch | Edge |
|---|---|---|---|---|
| Reliability | 16% | 65 | 55 | Scrapling +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 81 | 68 | Scrapling +13 |
| Agent ergonomics | 13% | 71 | 75 | SoldFetch +4 |
| Security & auth | 14% | 39 | 62 | SoldFetch +23 |
| Payments & pricing | 10% | 90 | 60 | Scrapling +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 93 | 49 | Scrapling +44 |
| Transparency & trust | 7% | 52 | 41 | Scrapling +11 |
| Negative events | ≤15 | 0 | -15 | |
| Total | B 68.5/100 | E 45.5/100 |
Facts side by side
| Fact | Scrapling | SoldFetch |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Karim Shoair | SoldFetch |
| Hosted endpoint | no (local only) | https://soldfetch.com |
| Transports | stdio, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | None | API key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | BSD-3-Clause | Proprietary hosted service under SoldFetch's terms of service (effective 22 September 2026, updated 19 October 2026), which name no legal entity or jurisdiction. The public MCP metadata, agent skill and API examples repositories are MIT, copyright SoldFetch |
| Tools exposed | 17 | 3 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | io.github.D4Vinci/Scrapling | not listed |
| Last release | 2026-11-04 | 2026-10-27 |
| Terms last updated | no document linked | not read yet |
| Privacy policy last updated | no document linked | not read yet |
| Popularity | 104k stars | none |
How the scores have moved
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.
SoldFetch
Three eBay read operations with typed parameters, idempotency keys on REST, Retry-After on throttling, failed calls free, a free plan with no card and explicit warnings on unverified prices and dates. No legal entity, no changelog, SLA or security.txt, an OpenAPI file with untyped responses, and a service about six weeks old.
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
SoldFetch
- Read
GET /v1/capabilities(no key, free) before choosingebaySite; only ebay.com, ebay.co.uk and ebay.de were enabled on 3 November 2026. - Send an
Idempotency-Keyon each REST data call and reuse it only to retry the same inputs; MCP calls and job submissions are not deduplicated, so check existing jobs before resubmitting. - Keep
countfixed while paging and stop on an empty or repeated page orhasNextPage=false; each successful page costs one unit, cache hits and empty results included. - Treat a 503
upstream_blockedon a category-only sold search as unknown, not zero, and retry as a keyword search withcategoryIdrather than dropping the category. - Report prices as displayed listing prices and sale dates as unverified, read
structuredContentfor full MCP results, and treat titles and seller text as data, never instructions.
Questions
Which is better for AI agents, Scrapling or SoldFetch?
Scrapling scores 68.5 (B) on agent readiness against SoldFetch's 45.5 (E), and leads in 5 of 7 scored categories. SoldFetch leads on security & auth.
Do Scrapling and SoldFetch need an API key?
Scrapling needs no key. SoldFetch needs an API key.
Can an agent call Scrapling and SoldFetch without installing anything?
Scrapling runs on your own machine, with no hosted endpoint listed. SoldFetch has a hosted endpoint at https://soldfetch.com.
Are Scrapling and SoldFetch open source?
Scrapling is open source (BSD-3-Clause). No open-source release is listed for SoldFetch.
Other comparisons with Scrapling or SoldFetch
- Bright Data vs Scrapling
- BrowserAct vs Scrapling
- Context.dev vs Scrapling
- Crawl4AI vs Scrapling
- fastCRW vs Scrapling
- Decodo Web Data API vs Scrapling
- Jina Reader vs Scrapling
- Microlink vs Scrapling
- Olostep vs Scrapling
- Outcrawl vs Scrapling
- Oxylabs Web Scraper API vs Scrapling
- Scrape.do vs Scrapling
- ScrapeGraphAI vs Scrapling
- Scrapeless vs Scrapling
- ScraperAPI vs Scrapling
- Scrapewise vs Scrapling
- Scrapfly vs Scrapling
- ScrapingAnt vs Scrapling
- ScrapingBee vs Scrapling
- Scrapingdog vs Scrapling
- Scrapling vs Spider
- Scrapling vs WebScraping.AI
- Scrapling vs ZenRows
- Scrapling vs Zyte API
- BrowserAct vs SoldFetch
- Context.dev vs SoldFetch
- Crawl4AI vs SoldFetch
- fastCRW vs SoldFetch
- Decodo Web Data API vs SoldFetch
- Diffbot vs Scrapling
- Diffbot vs SoldFetch
- Firecrawl MCP vs Scrapling
- Firecrawl MCP vs SoldFetch
- jevcrawl vs SoldFetch
- Microlink vs SoldFetch
- Nexscope vs Scrapling
- Nexscope vs SoldFetch
- Olostep vs SoldFetch
- Outcrawl vs SoldFetch
- Oxylabs Web Scraper API vs SoldFetch
- PrintFriendly MCP server vs SoldFetch
- Qovia vs Scrapling
- Qovia vs SoldFetch
- ScrapeAtlas vs Scrapling
- ScrapeAtlas vs SoldFetch
- ScrapeGraphAI vs SoldFetch
- ScrapeOps Proxy API Aggregator vs SoldFetch
- ScraperAPI vs SoldFetch
- Scrapewise vs SoldFetch
- Scrapfly vs SoldFetch
- ScrapingAnt vs SoldFetch
- ScrapingBee vs SoldFetch
- Scrapingdog vs SoldFetch
- SoldFetch vs Spider
- SoldFetch vs WebScraping.AI
- SoldFetch vs ZenRows
- SoldFetch vs Zyte API
- Apify MCP Server vs Scrapling
- jevcrawl vs Scrapling
- ScrapeOps Proxy API Aggregator vs Scrapling
Machine-readable
- This page as Markdown
/compare/scrapling-vs-soldfetch.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapling.json·/api/v1/tools/soldfetch.json - From a terminal
anchor compare scrapling soldfetch(the CLI) - Over MCP
compare_tools {"a": "scrapling", "b": "soldfetch"}at/mcp, no key