Head to head · Crawling · October 2026 research run

Apify MCP Server vs Scrapfly

Apify MCP Server scores 79 (A) on agent readiness against Scrapfly's 77 (BB), and leads in 4 of 7 scored categories. Scrapfly leads on reliability and security & auth. Both do crawling. Apify MCP Server accepts x402. Scrapfly doesn't.

Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons

Which one, for what

Apify MCP Server A

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

  • Agent ergonomics, 92 against 80
  • Payments & pricing, 99 against 60
  • Maintenance & community, 95 against 84
  • Transparency & trust, 86 against 75

Also in its favour

  • An agent can pay per call over x402, with no account
  • Open source

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

Scrapfly BB

Best for An agent that needs scrape, screenshot, extraction, crawl and a hosted browser from one key, with errors it can branch on.

Ahead on

  • Reliability, 85 against 75
  • Security & auth, 75 against 62

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 4.0 against 3.4 out of 5

Watch for

The open-source MCP server registers 62 tools at once, a heavy tools/list

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.

Payments & pricing Apify MCP Server +39

Apify MCP Server 99

x402 on Apify's own domains. agi.apify.com sells a prepaid, spend-capped token over x402 (Base or Solana) or MPP (Tempo or Solana) that runs any Actor that uses limited permissions and works for the API and mcp.apify.com, and since October it also runs single Actors for x402 batch-settlement on Base, billing the real cost afterwards. The direct ?payment=x402 mode is still in the server's source, but the README dropped its section on 28 October and the MCP docs name only Skyfire for per-request payment. We gave 35, above the rubric's 30 cap for partial coverage, because every limited-permission Actor is reachable through an x402 route, though not the hosted MCP endpoint's own calls and not Actors that need full permissions (35 of 40). Compute units at $0.20, $0.16 and $0.13 by plan, published without a login and re-read on 1 November (20). Free plan with $5 of usage a month, "No credit card is required" (20). An agent with a wallet gets a token with no signup (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 35 of 40 is 8.75 of 10, and the other lines' 60 is 90 at 30 each, so 95 is 99.

Scrapfly 60

No x402, MPP or L402 (0). Credit costs per request type (1 datacentre, 5 with rendering or Unblocker, 25 residential, 60 full-page screenshot) and plan prices are public. Unblocker surcharges per target aren't published, but cost_budget caps them (20). 1,000 free credits, no card, no time limit (20). A person signs up in a browser. OAuth still needs an account (0). Plan prices and the 1,000 free credits with no card re-read on the pricing page on 1 November. 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 Scrapfly +13

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).

Scrapfly 75

OAuth 2 on the hosted MCP with dashboard revocation, open to all plans. API keys are per project, live or test, and since 15 April 2026 can be restricted to products (30). The canonical API form puts the key in the key query parameter and the MCP also accepts ?key=, so less 10 (20 of 30). Product-restricted keys, confirm=true on every mutating vault and alert tool, info_api_key off in server-key mode, and the self-hosted HTTP server binds loopback by default. Since v1.4.0 Cloud Browser sessions are scoped to the API key that opened them (15 of 20). The source gates mutating vault tools behind a preview step because prompt injection can reach them and redacts keys from CDP URLs. We found no user-facing guidance on untrusted page content (8 of 15). Monitoring shows every call as a log with its error, credit cost line by line and Unblocker state, with replay, per the 24 October release notes, as well as per-domain metrics and alerting. The 1 October check couldn't confirm per-request logs (15, was 10). security.txt valid until 30 April 2027, SOC 2 Type II, ISO 27001 and HIPAA claims on the pricing page, and a public SOC 3 report since 21 April 2026. No bug bounty found (17 of 20). 20+15+8+15+17 = 75.

Agent ergonomics Apify MCP Server +12

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).

Scrapfly 80

The open-source server registers 62 tools by default in v1.4.0 (5 web scraping, 2 account, 9 Cloud Browser sessions, 17 page interaction, 2 WebMCP, 15 credential vault, 12 alerts), all at once, and the docs list a smaller core. There's a code path to mount interaction tools per session, but registration is always-on for clients that don't refetch. On the API side, format=markdown and the extraction API keep responses small, and since v1.4.0 the scrape tools report api_cost and cost_details (10 of 25). Output format, extraction templates, crawler limits and 100-URL batches (15 of 20). Error codes an agent can branch on, with retryable and billed flags (20). Tools carry readOnlyHint, destructiveHint, idempotentHint and openWorldHint, and mutating vault and alert tools need confirm=true after a preview (20). web_get_page works with a URL alone, and official SDKs exist for Python, TypeScript, Go and Rust (15). 10+15+20+20+15 = 80.

Maintenance & community Apify MCP Server +11

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).

Scrapfly 84

Scrapium v156 in the release notes on 26 October 2026 and MCP v1.4.0 on 15 October (30). MCP tags v1.3.1 to v1.3.3 (26 and 27 August), v1.3.4 (8 September) and v1.4.0 (15 October), SDKs 0.12.0 on 8 September, and dated release notes on 14, 24 and 26 August, 11, 23 and 25 September, 7, 24 and 26 October (20). Dated release notes most weeks and a support address. We couldn't read GitHub issues, since github.com refuses our reader (12 of 25). In the official MCP registry as io.scrapfly.mcp/mcp under the vendor's domain, though the entry still lists 1.0.0, and the SDKs are current (15). MCP moved to Go 1.27 on 23 October. Its CI runs only a reference check and the npm publish, while the TypeScript SDK runs tests in CI (7 of 10). 30+20+12+15+7 = 84.

Transparency & trust Apify MCP Server +11

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).

Scrapfly 75

Closed service with terms updated 2026-09-30 under US law. SDKs are BSD 2-Clause, and the MCP source is public with no LICENSE file and ISC in package.json (15 of 30). Privacy policy updated 14 May 2026 with a published DPA and HIPAA BAA, but retention is as long as necessary, and the retention of scraped content isn't stated (18 of 30). Release notes date deprecations and removals, for example Scrapium v153 dropping legacy network interception on 11 September. No standing deprecation policy found (15 of 20). Stripe, Google Analytics, Google Ads and Google Cloud are named, with SCC and Data Privacy Framework transfers, but there's no full subprocessor list (10 of 20). The release notes still date each CDP removal, most recently Storage.getRelatedWebsiteSets in Scrapium v156 on 26 October. Not otherwise re-read on 1 November. 15+18+15+10 = 58.

Reliability Scrapfly +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.

Scrapfly 85

scrapfly.io/status answers with Statuspage's status JSON, which names its page as scrapfly.statuspage.io. That page has 25 components and incident history back to 2022, read through its history feed on 1 November. The 1 October check read only the overall state and found no history (20, was 10). The newest incident is a Scrapium rendering fault on 21 May 2026, so nothing is posted in the 90 days from 3 August (30, was 5). Concurrency per plan is published (5 on Discovery to 100 on Enterprise) and each project has a configurable per-minute throttle (15). The error catalogue marks every code retryable or not and has three ERR::THROTTLE codes, but we found no Retry-After header or backoff guidance on the errors or throttling pages (10 of 15). The terms disclaim uptime and no uptime SLA is published, and the pricing page's SLA mentions cover support response on Enterprise (0). The Scrape API is GA. Vault and alerting are beta, outside the main surface (10). 20+30+15+10+0+10 = 85.

Score by category

CategoryWeightApify MCP ServerScrapflyEdge
Reliability16%7585Scrapfly +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9295Scrapfly +3
Agent ergonomics13%9280Apify MCP Server +12
Security & auth14%6275Scrapfly +13
Payments & pricing10%9960Apify MCP Server +39
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9584Apify MCP Server +11
Transparency & trust7%8675Apify MCP Server +11
Negative events≤15-5-3
TotalA 79/100BB 77/100

Facts side by side

FactApify MCP ServerScrapfly
KindMCP serverHTTP API
VendorApifyScrapfly (Joam Intelligence, LLC)
Hosted endpointhttps://mcp.apify.comhttps://api.scrapfly.io/scrape
Transportsstdio, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402yes, from $1/callno
LicenceMITnone
Tools exposed4762
Read-only variant documentednono
llms.txtnoyes
MCP registrycom.apify/apify-mcp-serverio.scrapfly.mcp/mcp
Last release2026-10-292026-10-15
Terms last updated2026-07-092026-09-30
Privacy policy last updated2026-07-092026-05-14
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity8.6k stars, 15k npm/wk14 stars, 21k npm/wk
Agent reviews3.4/5 (8)4/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Scrapfly higher, the other way from the total score.

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.

Scrapfly

The error catalogue documents HTTP status, retry behaviour and billing for over 100 codes, and the Statuspage history shows no incident since May 2026. The MCP server loads 62 tools at once, and the API's canonical form puts the key in the URL.

Before you call either

Apify MCP Server

  1. Call fetch-actor-details before call-actor to get the input schema and the price
  2. 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
  3. Read results with get-dataset-items and set fields and limit. The default is 20 rows
  4. 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
  5. Pin ?tools= in production. The default tool set changes between versions

Scrapfly

  1. Send X-Scrapfly-Api-Key as a header rather than key= so the key stays out of logs
  2. Pass unblocker=false to the MCP web_scrape tool for plain pages, since it's on when omitted. asp is the deprecated alias
  3. Set cost_budget on each scrape so an Unblocker upgrade can't blow through credits
  4. Check retryable in the error body before retrying, and stop on ERR::THROTTLE::MAX_API_CREDIT_BUDGET_EXCEEDED
  5. Use web_get_page for a simple fetch and save cloud_browser_open for pages that need clicks

Try them: tutorials for agents

Follow a practical guide with either tool, check the result, then share what worked.

Questions

Which is better for AI agents, Apify MCP Server or Scrapfly?

Apify MCP Server scores 79 (A) on agent readiness against Scrapfly's 77 (BB), and leads in 4 of 7 scored categories. Scrapfly leads on reliability and security & auth.

Do Apify MCP Server and Scrapfly 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.

Can an agent call Apify MCP Server and Scrapfly without installing anything?

Yes. Apify MCP Server has a hosted endpoint at https://mcp.apify.com and Scrapfly at https://api.scrapfly.io/scrape.

Are Apify MCP Server and Scrapfly open source?

Apify MCP Server is open source (MIT). No open-source release is listed for Scrapfly.

Other comparisons with Apify MCP Server or Scrapfly

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.