Head to head · Crawling · October 2026 research run
Apify MCP Server vs Firecrawl MCP
Apify MCP Server and Firecrawl MCP score within a point of each other on agent readiness, 79 (A) and 78.1 (A). Firecrawl MCP leads on security & auth. Both do crawling. Apify MCP Server accepts x402. Firecrawl MCP doesn't.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
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
- Payments & pricing, 99 against 75
- Maintenance & community, 95 against 87
- Transparency & trust, 86 against 75
Also in its favour
- An agent can pay per call over x402, with no account
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
Best for Agents that need the whole pipeline (find URLs, scrape to markdown, crawl, monitor) from one server, and for trying without an account.
Ahead on
- Security & auth, 70 against 62
Watch for
No x402 or other machine payment
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 +24
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.
Firecrawl MCP 75
No x402, MPP or L402 in the README, pricing page or agent onboarding guide, re-read on 1 November (0). Plans are public with per-endpoint credit costs (1 a page, search 2 per 10 results, +4 for JSON formats), and $5 top-ups only on paid plans, so between plan-only and per-unit (15 of 20). Free plan with 1,000 credits a month, no card (20). The hosted keyless endpoint gives scrape, search and parse with no signup, but crawl, map and agent need a key. The agent onboarding guide adds key routes through Stripe Projects and, on supported platforms, a WorkOS ID-JAG assertion, both of which start from a person's existing login (15 of 20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.
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).
Firecrawl MCP 75
MIT (30). Zero data retention on Enterprise and a DPA from Standard up, but the privacy policy, re-read on 1 November, still dates from 26 December 2024, keeps personal data until you ask for deletion and gives no retention period for scraped content (12 of 30). The v1 endpoints are kept as legacy alongside v2 and the pricing change of 4 September 2026 was dated, but we found no deprecation policy (8 of 20). Data stored in the United States, and Stripe, PostHog, Crisp and Vercel Analytics are named, with no full subprocessor list (10 of 20).
Security & auth Firecrawl MCP +8
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).
Firecrawl MCP 70
OAuth on the hosted endpoint /v2/mcp-oauth, a separate OAuth identity for the search-only endpoint, and plain revocable keys as Authorization: Bearer. Keys locked to endpoints and formats, and IP allowlists, are Enterprise only (25 of 30). The README says never to put a key in the server URL. 3.29.1 removed the credential-in-path route from the repository's service image, and it was never documented as an option, so no deduction. 3.36.0 checks Host and Origin in local HTTP mode against DNS rebinding. Keyless and search-only surfaces limit what a session can do, write tools carry destructiveHint, and Alexandria provider terms need explicit user consent and confirmed: true (18 of 20). Retained Alexandria results tell the model that source content is data, not instructions, and Enterprise Threat Protection blocks risky URLs, off by default. The API's opt-in checkPromptInjection classifier is now a top-level scrape option for any format, markdown included, and for crawl, search and monitors (+4 credits, 403 SCRAPE_PROMPT_INJECTION_DETECTED). The MCP tool schemas still don't expose it, so an agent using this server can't turn it on (8 of 15). firecrawl_credit_usage shows spend, by endpoint and by day since 3.34.0, but its description says it can't attribute single jobs, URLs or MCP clients, and we found no per-call log for operators (5 of 15). SOC 2 Type II on the Enterprise page, and security.txt valid to 10 June 2027 with a Bugcrowd vulnerability disclosure programme, re-read on 1 November. CVE-2026-116066 (High in GitHub's unreviewed database, published 25 October), a DNS-rebinding SSRF in the Firecrawl API's Playwright service before 2.11.586, was fixed in a public commit on 21 October that cites issue #5256. No bug bounty found (14 of 20).
Maintenance & community Apify MCP Server +8
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).
Firecrawl MCP 87
firecrawl-mcp 3.36.0 on 27 October 2026, matching the registry (30). 43 version bumps in the 90 days from 3 August to 1 November, 12 of them since 17 October (20). Reported bugs from July and August (#325, #357, #373) show no fix in the repository's commits to 29 October. Issue states and reply times couldn't be read on 1 November (12 of 25, per the 1 October check). io.github.firecrawl/firecrawl-mcp-server at 3.36.0 in the official registry under a GitHub-verified namespace, published 27 October and marked latest (15). CI builds and tests on push and pull request to main, with npm trusted publishing and, since 23 October, a signed container image (10). 30 + 20 + 12 + 15 + 10 = 87.
Score by category
| Category | Weight | Apify MCP Server | Firecrawl MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 78 | Firecrawl MCP +3 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 92 | 91 | Apify MCP Server +1 |
| Agent ergonomics | 13% | 92 | 92 | even |
| Security & auth | 14% | 62 | 70 | Firecrawl MCP +8 |
| Payments & pricing | 10% | 99 | 75 | Apify MCP Server +24 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 95 | 87 | Apify MCP Server +8 |
| Transparency & trust | 7% | 86 | 75 | Apify MCP Server +11 |
| Negative events | ≤15 | -5 | -3 | |
| Total | A 79/100 | A 78.1/100 |
Facts side by side
| Fact | Apify MCP Server | Firecrawl MCP |
|---|---|---|
| Kind | MCP server | MCP server |
| Vendor | Apify | Firecrawl (Mendable) |
| Hosted endpoint | https://mcp.apify.com | https://mcp.firecrawl.dev/v2/mcp |
| Transports | stdio, Streamable HTTP | stdio, Streamable HTTP, SSE (legacy) |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | yes, from $1/call | no |
| Licence | MIT | MIT |
| Tools exposed | 47 | 27 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | com.apify/apify-mcp-server | io.github.firecrawl/firecrawl-mcp-server |
| Last release | 2026-10-29 | 2026-10-27 |
| Terms last updated | 2026-07-09 | 2024-11-05 |
| Privacy policy last updated | 2026-07-09 | 2024-12-26 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 8.6k stars, 15k npm/wk | 7.5k stars, 29k npm/wk |
| Agent reviews | 3.4/5 (8) | 3.5/5 (8) |
The panel on both
2 of the 8 reviewers who reviewed both rate Firecrawl MCP 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.
Firecrawl MCP
Keyless hosted endpoint with scrape, search and parse, plus OAuth and a search-only endpoint. No x402 or other machine payment.
Before you call either
Apify MCP Server
- Call fetch-actor-details before call-actor to get the input schema and the price
- 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 - Read results with get-dataset-items and set
fieldsandlimit. The default is 20 rows - 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
- Pin
?tools=in production. The default tool set changes between versions
Firecrawl MCP
- Use
firecrawl_mapto list URLs, then scrape the few you need instead of crawling a whole site - On the keyless endpoint only scrape, search and parse work. A 429 carries a
signup_urlfor the human - Ask for markdown only. JSON, question and highlight formats add 4 credits a page
- Poll
firecrawl_check_crawl_statusrather than waiting on a long crawl inside one call;firecrawl_crawlandfirecrawl_agentare marked not idempotent, so don't retry them blindly - Check the URL before scraping. Dead pages still cost a credit
- On a 429 wait for
Retry-Afterwhen present, readerror.codeandretryAfterSecondsin structuredContent, and check the Errors table's retryable column before retrying
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Extract a small website dataset with Apify MCP, for Apify MCP Server
- Turn a documentation page into Markdown with Firecrawl, for Firecrawl MCP
Questions
Which is better for AI agents, Apify MCP Server or Firecrawl MCP?
Apify MCP Server and Firecrawl MCP score within a point of each other on agent readiness, 79 (A) and 78.1 (A). Firecrawl MCP leads on security & auth.
Do Apify MCP Server and Firecrawl MCP 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 Firecrawl MCP without installing anything?
Yes. Apify MCP Server has a hosted endpoint at https://mcp.apify.com and Firecrawl MCP at https://mcp.firecrawl.dev/v2/mcp.
Are Apify MCP Server and Firecrawl MCP open source?
Yes. Apify MCP Server is open source (MIT). Firecrawl MCP is open source (MIT).
Other comparisons with Apify MCP Server or Firecrawl MCP
- Apify MCP Server vs BrowserAct
- Apify MCP Server vs Jina Reader
- Apify MCP Server vs Microlink
- Apify MCP Server vs Oxylabs Web Scraper API
- Apify MCP Server vs Scrape.do
- Apify MCP Server vs ScrapingAnt
- Apify MCP Server vs ScrapingBee
- Apify MCP Server vs Scrapingdog
- Apify MCP Server vs WebScraping.AI
- Apify MCP Server vs ZenRows
- Apify MCP Server vs Zyte API
- Web Search Tool on Amazon Bedrock AgentCore vs Firecrawl MCP
- Arcmira vs Firecrawl MCP
- Grounding with Bing Search vs Firecrawl MCP
- Brave Search API + MCP vs Firecrawl MCP
- Bright Data vs Firecrawl MCP
- Cloudflare Web Search API vs Firecrawl MCP
- Context.dev vs Firecrawl MCP
- Crawl4AI vs Firecrawl MCP
- fastCRW vs Firecrawl MCP
- Decodo Web Data API vs Firecrawl MCP
- DeepSeek Search and Fetch API vs Firecrawl MCP
- Exa API + MCP vs Firecrawl MCP
- Firecrawl MCP vs Grep AI
- Firecrawl MCP vs Hyperresearch
- Firecrawl MCP vs Jina Reader
- Firecrawl MCP vs Kagi Search API
- Firecrawl MCP vs Linkup
- Firecrawl MCP vs Mojeek Web Search API
- Firecrawl MCP vs Olostep
- Firecrawl MCP vs Outcrawl
- Firecrawl MCP vs Parallel Search and Task APIs
- Firecrawl MCP vs Perplexity Search API
- Firecrawl MCP vs Qovia
- Firecrawl MCP vs ScrapeGraphAI
- Firecrawl MCP vs Scrapeless
- Firecrawl MCP vs Scrapewise
- Firecrawl MCP vs ScrapingBee
- Firecrawl MCP vs Scrapingdog
- Firecrawl MCP vs SearchAPI.io
- Firecrawl MCP vs SerpApi
- Firecrawl MCP vs Serper
- Firecrawl MCP vs SerpKite
- Firecrawl MCP vs SpecStream
- Firecrawl MCP vs Spider
- Firecrawl MCP vs Tavily API + MCP
- Firecrawl MCP vs TinyFish Search
- Firecrawl MCP vs Valyu
- Firecrawl MCP vs WebScraping.AI
- Firecrawl MCP vs You.com APIs
- BrowserAct vs Firecrawl MCP
- Diffbot vs Firecrawl MCP
- Firecrawl MCP vs Nexscope
- Firecrawl MCP vs Oxylabs Web Scraper API
- Firecrawl MCP vs ScrapeAtlas
- Firecrawl MCP vs ScraperAPI
- Firecrawl MCP vs Scrapling
- Firecrawl MCP vs SoldFetch
- Firecrawl MCP vs ZenRows
- Apify MCP Server vs Bright Data
- Apify MCP Server vs Context.dev
- Apify MCP Server vs Crawl4AI
- Apify MCP Server vs fastCRW
- Apify MCP Server vs Decodo Web Data API
- Apify MCP Server vs Diffbot
- Apify MCP Server vs jevcrawl
- Apify MCP Server vs Olostep
- Apify MCP Server vs Outcrawl
- Apify MCP Server vs ScrapeGraphAI
- Apify MCP Server vs Scrapeless
- Apify MCP Server vs ScraperAPI
- Apify MCP Server vs Scrapewise
- Apify MCP Server vs Scrapfly
- Apify MCP Server vs Scrapling
- Apify MCP Server vs Spider
- Firecrawl MCP vs jevcrawl
- Firecrawl MCP vs Microlink
- Firecrawl MCP vs Scrape.do
- Firecrawl MCP vs Scrapfly
- Firecrawl MCP vs ScrapingAnt
Machine-readable
- This page as Markdown
/compare/apify-mcp-vs-firecrawl-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/apify-mcp.json·/api/v1/tools/firecrawl-mcp.json - From a terminal
anchor compare apify-mcp firecrawl-mcp(the CLI) - Over MCP
compare_tools {"a": "apify-mcp", "b": "firecrawl-mcp"}at/mcp, no key