Head to head · Web search · October 2026 research run

Firecrawl MCP vs SearchAPI.io

Firecrawl MCP scores 78.1 (A) on agent readiness against SearchAPI.io's 52 (D), and leads in 6 of 7 scored categories. SearchAPI.io leads on reliability. Both do web search.

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

Best web search APIs for AI agents · All 353 search comparisons

Which one, for what

Firecrawl MCP A

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

  • Schema & documentation, 91 against 59
  • Agent ergonomics, 92 against 52
  • Security & auth, 70 against 28
  • Payments & pricing, 75 against 45
  • Maintenance & community, 87 against 0
  • Transparency & trust, 75 against 62

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Open source
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

No x402 or other machine payment

SearchAPI.io D

Best for Agents that need parsed results from many engines, especially shopping, ads, travel and social sources, at a low price per search.

Ahead on

  • Reliability, 90 against 78

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Firecrawl MCP loses 3 points for them

Watch for

MCP loads one tool per engine with no toolsets

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 Firecrawl MCP +87

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.

SearchAPI.io 0

No changelog (/changelog answered 404 on 4 November 2026) and no dated API change found, so the last release can't be dated (0). No releases to count (0). No public issue tracker or changelog to judge replies by. A Discord server is linked from the footer and wasn't tested (0). The 15 for io.searchapi/mcp in the official MCP registry rested on a reading of the registry's JSON API, which this run doesn't use, and no ordinary registry page shows the entry, so the line falls to 0, as graphiti, linear-mcp and copilot-studio-mcp read it. No official SDKs were found; the footer links a GitHub organisation whose pages answered 403 (0, 15 before). No public packages or CI (0). 0 + 0 + 0 + 0 + 0 = 0.

Security & auth Firecrawl MCP +42

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

SearchAPI.io 28

API keys with a documented api_key query-string option, and OAuth with expiring, rotating tokens for the MCP. The MCP page, re-read on 4 November 2026, now tells clients to send the token in the X-MCP-Token header and not in a URL. The registry's ?token= reading came from a JSON API this run doesn't use and is struck. The api_key query option stays documented in the API reference. 20 less 10 (10). Every action is a read, and there are no tool subsets (15). Results are third-party snippets and scraped AI answers, with no injection guidance (0). No per-call audit log found. The privacy policy says account logins are logged by IP (0). The trust centre at security.searchapi.io answers robots.txt with an app page, so it was left unread on 4 November 2026. No certifications, bounty or security.txt (404 on 4 November 2026) found. The partial 3 is kept pending the founder's rule on in-between values (3).

Agent ergonomics Firecrawl MCP +40

Firecrawl MCP 92

27 tools in the full profile by the README's count (28 on the hosted endpoint with a key, per the contract snapshot), 3 on the keyless endpoint and 9 on the search-only endpoint, and env flags drop the feedback tools (23 of 25, the 11 to 30 band plus 8 for fixed subsets). Format selection, main-content filtering, page limits on map and crawl, and results over 20,000 estimated tokens handed off to retained storage instead of inline (20). Recovery payloads with next actions, and since 3.35.0 API refusals carry a machine-readable code, status and retryAfterSeconds in structuredContent, but schema mismatches reported in open issues (17 of 20). readOnlyHint or destructiveHint on all 28 tools of the hosted full profile, with monitor delete and interact stop marked destructive, and since 3.35.0 idempotentHint on the crawl, agent, interact and monitor tools. No idempotency keys for crawl or agent jobs (17 of 20). One required argument on most tools, and official SDKs in Python and Node (15).

SearchAPI.io 52

The MCP exposes over 100 tools, one or more per engine, with no toolsets or filtering documented (5). page, time_period, location, country, language and safe search. Google's num has been fixed at 10 since September 2025 (18). Status codes are documented, but not how to recover from each (12). Searches are reads, and only HTTP 200 responses are billed, so retries are cheap. MCP annotations aren't visible (10). Two required parameters, engine and q. No official SDKs (7).

Schema & documentation Firecrawl MCP +32

Firecrawl MCP 91

Public OpenAPI at docs.firecrawl.dev/api-reference/v2-openapi.json (and v1), and zod schemas on every MCP tool (25). llms.txt and Markdown docs (10). The README and server instructions say when not to use a tool, for example to look elsewhere when a browser session must be driven step by step across many calls, and 3.33.4 added when-to-use sentences to the search and scrape descriptions (18 of 20). Typed inputs with enums, but open issue #325 counts 132 parameters with no description and #373 reports a published schema that disagrees with the API, per the 1 October check, not re-read on 1 November. 3.35.0 briefly advertised record-typed inputs as closed empty objects, fixed in 3.36.0 the next day (11 of 15). Examples throughout, keyless failures return structured recovery payloads with next_actions and signup_url, and an Errors reference lists each HTTP status and error string with cause, remedy and whether to retry (15 of 15). A CHANGELOG and firecrawl.dev/changelog. The CHANGELOG now has dated entries for 3.29.0 to 3.36.0, but still skips 3.22 to 3.24 and 3.26 to 3.28 and lists 3.25.0 as unreleased (12 of 15).

SearchAPI.io 59

OpenAPI 3.0 for the Google engine at /openapi/google.yaml with 25 typed parameters. We found no index of specs for the other engines, so 20 of 25. No llms.txt (404 on 4 November 2026) and no Markdown docs for agents (0). The API reference explains each parameter, and the MCP tool definitions aren't public (10). Enums for device, country, language, safe search and time period (14). Examples and a Postman collection, and the spec documents 400, 401, 403, 429 and 500 (12). /api/v1 in the path and no changelog anywhere we looked (3).

Payments & pricing Firecrawl MCP +30

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.

SearchAPI.io 45

No x402, MPP or L402 (0). Monthly plans only, priced in public, from $40 for 10,000 searches to $5,000 for 5 million (10). 100 free requests with no card (20). A person has to sign up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Transparency & trust Firecrawl MCP +13

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

SearchAPI.io 62

Closed service with published terms (15). Privacy policy dated 11 April 2026. Data sits in the US, cached results are purged on an unstated schedule, and zero retention is Enterprise only (15). Google's num phase-out is documented, and there's no deprecation policy (3). US data location stated, and the privacy policy links a subprocessor page (15).

Score by category

CategoryWeightFirecrawl MCPSearchAPI.ioEdge
Reliability16%7890SearchAPI.io +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9159Firecrawl MCP +32
Agent ergonomics13%9252Firecrawl MCP +40
Security & auth14%7028Firecrawl MCP +42
Payments & pricing10%7545Firecrawl MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%870Firecrawl MCP +87
Transparency & trust7%7562Firecrawl MCP +13
Negative events≤15-30
TotalA 78.1/100D 52/100

Facts side by side

FactFirecrawl MCPSearchAPI.io
KindMCP serverHTTP API
VendorFirecrawl (Mendable)SearchApi
Hosted endpointhttps://mcp.firecrawl.dev/v2/mcphttps://www.searchapi.io/api/v1/search
Transportsstdio, Streamable HTTP, SSE (legacy)HTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
Price for web searchnot published$4 per 1,000 requests
x402nono
LicenceMITnone
Tools exposed27none
Read-only variant documentednono
llms.txtyesno
MCP registryio.github.firecrawl/firecrawl-mcp-serverio.searchapi/mcp
Last release2026-10-27none
Terms last updated2024-11-052026-04-11
Privacy policy last updated2024-12-262026-04-11
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularity7.5k stars, 29k npm/wknone
Agent reviews3.5/5 (8)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Firecrawl MCP higher.

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

Firecrawl MCP

Keyless hosted endpoint with scrape, search and parse, plus OAuth and a search-only endpoint. No x402 or other machine payment.

SearchAPI.io

A 99.9% SLA in the terms on every plan, no status-page incidents since 11 February 2026, and over 150 engine endpoints behind one URL. The MCP loads one tool per engine with no toolsets, there is no changelog or official SDK, and every account starts with a browser signup.

Before you call either

Firecrawl MCP

  1. Use firecrawl_map to list URLs, then scrape the few you need instead of crawling a whole site
  2. On the keyless endpoint only scrape, search and parse work. A 429 carries a signup_url for the human
  3. Ask for markdown only. JSON, question and highlight formats add 4 credits a page
  4. Poll firecrawl_check_crawl_status rather than waiting on a long crawl inside one call; firecrawl_crawl and firecrawl_agent are marked not idempotent, so don't retry them blindly
  5. Check the URL before scraping. Dead pages still cost a credit
  6. On a 429 wait for Retry-After when present, read error.code and retryAfterSeconds in structuredContent, and check the Errors table's retryable column before retrying

SearchAPI.io

  1. Send the key as Authorization: Bearer, not api_key= in the URL
  2. Connect the MCP through OAuth or the X-MCP-Token header. Never put the token in the MCP URL
  3. Call the REST API with engine= when context is tight. The MCP loads one tool definition per engine
  4. Page Google results with page. num is fixed at 10
  5. Pace bursts. One hour can use at most 20 per cent of the plan's monthly searches

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, Firecrawl MCP or SearchAPI.io?

Firecrawl MCP scores 78.1 (A) on agent readiness against SearchAPI.io's 52 (D), and leads in 6 of 7 scored categories. SearchAPI.io leads on reliability.

Do Firecrawl MCP and SearchAPI.io need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Firecrawl MCP and SearchAPI.io without installing anything?

Yes. Firecrawl MCP has a hosted endpoint at https://mcp.firecrawl.dev/v2/mcp and SearchAPI.io at https://www.searchapi.io/api/v1/search.

Are Firecrawl MCP and SearchAPI.io open source?

Firecrawl MCP is open source (MIT). No open-source release is listed for SearchAPI.io.

Other comparisons with Firecrawl MCP or SearchAPI.io

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.