ScrapeOps Proxy API Aggregator vs ScraperAPI

ScrapeOps Proxy API Aggregator 61

Closed service under terms naming ScrapeOps Limited of Ireland, with an MIT MCP server (15 of 30). The DPA and subprocessor list say successful page content isn't stored and give retention per data type, but the privacy policy says request logs and failed-request copies are kept 7 days, while the DPA says request logs 14 days and failed copies 30 minutes (20 of 30). No deprecation policy. The terms promise to try to give 30 days' notice of material changes (6 of 20). Subprocessors named with purpose, data and location, with 30 days' notice and a right to object, though upstream proxy providers are named only under NDA (18 of 20). 15 + 20 + 6 + 18 = 59.

ScraperAPI 54

Closed service. The MCP server and skills are MIT. Terms of Use exist at /terms/, but robots.txt disallows that path, so we could not confirm what they say (10 of 30). The privacy policy says activity logs are deleted after 7 days and account data within 60 days of a request, async results are kept up to 72 hours and DataPipeline results 30 days. The policy is undated, names Saas.group Inc. while a November 2025 release note says the service operates as ScraperAPI LLC, and no DPA was found (14 of 30). The terms and billing change was announced with effective dates of 4 November 2025 and 5 January 2026. No standing deprecation policy (8 of 20). No sub-processor list or hosting location found, only a general statement on transfers outside the EEA (3 of 20). 10 + 14 + 8 + 3 = 35.

ScrapeOps Proxy API Aggregator 37

Graded on the hosted lines. No status page was found on scrapeops.io or in the docs, and status.scrapeops.io did not answer (0). No readable incident history (5). Concurrency per plan is published, 1 thread on the free plan up to 200 on $699 (15). 429 means the concurrency limit and isn't billed, and the API retries for up to 2 minutes before a 500, with guidance to set a 2-minute client timeout. No Retry-After or backoff guidance (7 of 15). No SLA; the terms disclaim availability (0). Generally available since July 2022 (10). 0 + 5 + 15 + 7 + 0 + 10 = 37.

ScraperAPI 42

No status page is linked from the home, pricing, support or docs pages we read on 9 October or 4 November (0). No readable incident history (5). Concurrency limits are published per plan, 5 threads on Free, 20 on Hobby, 50, 100, 200, 300 and 500 above it, and the local MCP server limits itself to 10 calls in 60 seconds (15). 429 is documented as a concurrency rejection with no charge, the API retries a target for up to 70 seconds before returning 500, failed requests aren't charged, and the docs tell clients to retry failed requests. That is safe-retry guidance with no idempotency keys on the async job writes and no Retry-After header (12 of 15). The pricing page lists a 99.9% uptime guarantee on every plan, but no SLA document or credit terms were found and the Terms of Use are closed to us (0 of 10). The API, async service and crawler are generally available (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.

ScrapeOps Proxy API Aggregator 79

Three MCP tools (25). Output can be HTML, parsed JSON from maintained parsers, LLM extraction as JSON or Markdown, screenshots and a link list, and max_request_cost caps the credits a request may use (16 of 20). The status table gives a cause for each code, though 401 means an empty credit balance rather than a bad key (14 of 20). Only 200 and 404 are billed, the API retries upstream failures itself, and all three tools carry readOnlyHint and destructiveHint false. No idempotency key (16 of 20). Only the key and url are required. Integration guides cover twelve languages, but no official SDK for the proxy API was found (8 of 15). 25 + 16 + 14 + 16 + 8 = 79.

ScraperAPI 74

28 MCP tools with no toolsets or dynamic loading (15 of 25). output_format returns Markdown or text, autoparse returns JSON on supported domains, structured endpoints page their results, and max_cost, crawl_budget and max_depth cap a job (15 of 20). Errors are HTTP status codes with plain-text messages. No machine-readable error codes (13 of 20). All 28 MCP tools carry readOnlyHint, destructiveHint, idempotentHint and openWorldHint, failed requests are not charged, and async jobs return a status URL to poll (16 of 20). Only api_key and url are required, rendering is off by default, and SDKs are documented for Python, Node.js, PHP, Ruby and Java (15). 15 + 15 + 13 + 16 + 15 = 74.

ScrapeOps Proxy API Aggregator 46

Read for a closed service. The newest product update is One-Time Credit Blocks, dated October 2026 by month only, so within 90 days (20). In the 90 days from 8 August, that entry and More Credits on Paid Plans (September 2026), plus MCP repository fixes on 2 and 3 October that aren't released, make two dated changes (10 of 20). Public changelog by product and support by email. GitHub issues weren't read (8 of 25). The MCP server's server.json names io.github.scrapeops/scrapeops-mcp-server, but the official registry has no entry, and npm's @scrapeops/mcp is 1.0.1 of 1 January 2026 while the repository says 1.1.0 (5 of 15). The MCP repository has tests but no CI workflow (3 of 10). 20 + 10 + 8 + 5 + 3 = 46.

ScraperAPI 41

The newest dated entry is the October 2026 release note on automatic Akamai unblocking, dated by month only. Counted from its month, October lies 4 to 34 days back, so it is inside 90 days but not shown within 30, as crustdata's October entries. The skills plugin's 1.1.0 of 7 August is an untagged version bump, and the MCP server's v1.1.1 is from 17 July 2026 (20). Since 6 August only the October note and the 7 August plugin bump are dated, fewer than three (0 of 20). The npm and PyPI pages of the SDKs and CLI couldn't be read on 4 November. Monthly release notes and support through the dashboard and email. We did not read the repository's issues (8 of 15). SDKs are documented for five languages, but we could not check their release dates, and the Node.js SDK repository's last commit is from 12 January 2024 (8 of 15). The MCP repository has unit tests and a lock file but no public CI workflow (5 of 10). 20 + 0 + 8 + 8 + 5 = 41.