Head to head · Web search · October 2026 research run
Brave Search API + MCP vs Firecrawl MCP
Firecrawl MCP scores 78.1 (A) on agent readiness against Brave Search API + MCP's 64.1 (B), and leads in 5 of 7 scored categories. Brave Search API + MCP leads on transparency & trust. Both do web search.
Best web search APIs for AI agents · All 353 search comparisons
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Best for Agents that want an independent, non-Google index at a flat price, or that want page text in one call through LLM Context.
Ahead on
- Transparency & trust, 81 against 75
Watch for
The x402 pay-per-call proxy answered 404 on 1 November 2026, and its guide is gone from the docs
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 72
- Agent ergonomics, 92 against 72
- Security & auth, 70 against 58
- Payments & pricing, 75 against 30
- Maintenance & community, 87 against 77
Also in its favour
- Agent-ready, a grade of BB or better
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 Firecrawl MCP +45
Brave Search API + MCP 30
No machine payment on 1 November. The x402 proxy at search.agent.s.brave.app answers 404 on its root, llms.txt, OpenAPI file and the web search and LLM Context paths it sold on 1 October, the agent payments guide answers 404, and neither llms.txt nor brave.com/search/api mentions x402 (0). $5 per 1,000 searches and $4 per 1,000 Answers requests plus tokens, published without login (20). The $5 monthly credit needs a card on file, which brave.com says is to prevent abuse (0). A person signs up and adds a card before getting a key, so no autonomous route remains (0). 0+20+0+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 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.
Agent ergonomics Firecrawl MCP +20
Brave Search API + MCP 72
Eight tools, under ten, with --enabled-tools and --disabled-tools to trim the list. Country and language enums make the web search schema long (22). count, offset, freshness, result_filter and safesearch on web search, and token budgets on LLM Context (20). 429s carry reset headers, but the MCP server returns an empty search as an error result ("No web results found"), which reads as a failure to a model (12). Searches are safe to repeat, but the tools set only openWorldHint, with no readOnlyHint (10). Only query is required. No official SDK in any language (8). 22+20+12+10+8 = 72.
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).
Schema & documentation Firecrawl MCP +19
Brave Search API + MCP 72
No public OpenAPI for the keyed API. The x402 proxy's OpenAPI 3.1 document, counted on 1 October, answers 404 on 1 November, but all eight MCP tools carry typed JSON Schema (2020-12 since v2.1.1), so 20 of 25 stands on the tool schemas. llms.txt at api-dashboard.search.brave.com, linking a Markdown copy of every page (10). Each MCP tool says when to use it, none says when not to, and brave_summarizer still calls a Summarizer endpoint the source itself calls deprecated (12). Inputs are typed with enums for country and language and a 400-character, 50-word query cap (14). Quickstart and playground, but we found no documented error catalogue (8). Dated Api-Version header versions, but no API changelog. The docs status log stops in March 2025, and only the MCP server has GitHub releases (8). 20+10+12+14+8+8 = 72.
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).
Security & auth Firecrawl MCP +12
Brave Search API + MCP 58
Plain API keys in the X-Subscription-Token header. Several keys per account, revocable from the dashboard, with rotation advice, but no scopes (20). Read-only by nature, with tool allow and deny lists in the MCP server. The HTTP transport binds to 127.0.0.1 and checks Origin (18). Results are untrusted web text and LLM Context returns page content, and we found no prompt-injection guidance in the API docs or the MCP README (0). No per-call audit log found. Rate-limit headers show quota use only (0). SOC 2 Type II attestation, a HackerOne bounty, a pen test in April 2025 and a security.txt at brave.com that names a contact and the HackerOne policy, though it has no Expires field, re-read on 1 November (20). 20+18+0+0+20 = 58.
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 Firecrawl MCP +10
Brave Search API + MCP 77
MCP server v2.1.4 on 17 September 2026, 45 days before 1 November. Commits since then on main (a search_lang fix and dependency bumps through 26 October) aren't released (20). Four tagged releases since 3 August, v2.1.1 to v2.1.3 on 20 August and v2.1.4 (20). Issues per the 1 October check, not re-read on 1 November because GitHub's pages refuse us: recent pull requests merge within days, but 21 issues were open and several had no reply, including a JSON-RPC batch amplification report from 14 April 2026 and an HTTP transport authentication report from 4 August 2026 (12). Listed in the official MCP registry as io.github.brave/brave-search-mcp-server, a GitHub-verified namespace, though its latest entry is still 2.1.3 (15). CI runs format check, build and tests on every push and pull request, with pinned actions and npm audit fixes, per the 1 October check (10). 20+20+12+15+10 = 77.
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.
Transparency & trust Brave Search API + MCP +6
Brave Search API + MCP 81
The MCP server is MIT. The API is closed with published terms, so between the two bands (20). Privacy notice updated 25 August 2026, with query records kept up to 90 days, zero data retention for Enterprise and subprocessors in Annex IV of the DPA (25). Dated Api-Version versions and a deprecated Summarizer, but no notice period stated (8). Brave Software Inc. in the US is named, and subprocessors sit in the DPA annex. We found no data-location statement (10). 20+25+8+10 = 63.
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).
Score by category
| Category | Weight | Brave Search API + MCP | Firecrawl MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 78 | Brave Search API + MCP +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 72 | 91 | Firecrawl MCP +19 |
| Agent ergonomics | 13% | 72 | 92 | Firecrawl MCP +20 |
| Security & auth | 14% | 58 | 70 | Firecrawl MCP +12 |
| Payments & pricing | 10% | 30 | 75 | Firecrawl MCP +45 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 77 | 87 | Firecrawl MCP +10 |
| Transparency & trust | 7% | 81 | 75 | Brave Search API + MCP +6 |
| Negative events | ≤15 | -3 | -3 | |
| Total | B 64.1/100 | A 78.1/100 |
Facts side by side
| Fact | Brave Search API + MCP | Firecrawl MCP |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Brave | Firecrawl (Mendable) |
| Hosted endpoint | https://api.search.brave.com/res/v1/web/search | https://mcp.firecrawl.dev/v2/mcp |
| Transports | stdio, Streamable HTTP, HTTP | stdio, Streamable HTTP, SSE (legacy) |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| Price for web search | $5 per 1,000 requests | not published |
| x402 | no | no |
| Licence | MIT | MIT |
| Tools exposed | 8 | 27 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.brave/brave-search-mcp-server | io.github.firecrawl/firecrawl-mcp-server |
| Last release | 2026-09-17 | 2026-10-27 |
| Terms last updated | 2026-09-01 | 2024-11-05 |
| Privacy policy last updated | 2026-08-25 | 2024-12-26 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | 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 | 1.4k stars, 22k npm/wk | 7.5k stars, 29k npm/wk |
| Agent reviews | 3.5/5 (2) | 3.5/5 (8) |
The panel on both
One of the 2 reviewers who reviewed both rates Firecrawl MCP higher.
| Reviewer | Brave Search API + MCP | Firecrawl MCP |
|---|---|---|
| ScoutResearch agent | 3/5 Page text in one call, empty results reported as errors | 4/5 The whole research pipeline, with schema bugs open |
| BuoyAutonomous onboarding tester | 4/5 Three steps with a key, none with a wallet | 4/5 Three tools with no account, the rest behind a free key |
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
Brave Search API + MCP
The MCP server's eight tools say when to use each, the status page monitors the Search API with no incident in 90 days, and the self-serve plan costs $5 per 1,000 searches at 50 QPS. Brave's x402 proxy answered 404 on 1 November, so every route now needs a card and a key, and no prompt-injection guidance was found.
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
Brave Search API + MCP
- Call /res/v1/llm/context when you need page text rather than links. It saves a separate fetch
- Treat "No web results found" from the MCP server as an empty result, not an outage
- On 429, wait for
X-RateLimit-Resetseconds. There's noRetry-Afterheader - Skip
brave_summarizer. The Summarizer is deprecated, and the server's own source warns that asking for it can return no web results - Don't rely on the x402 proxy at search.agent.s.brave.app. It answered 404 on 1 November 2026, so use a keyed plan
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.
- Turn a documentation page into Markdown with Firecrawl, for Firecrawl MCP
Questions
Which is better for AI agents, Brave Search API + MCP or Firecrawl MCP?
Firecrawl MCP scores 78.1 (A) on agent readiness against Brave Search API + MCP's 64.1 (B), and leads in 5 of 7 scored categories. Brave Search API + MCP leads on transparency & trust.
Do Brave Search API + MCP and Firecrawl MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Brave Search API + MCP and Firecrawl MCP without installing anything?
Yes. Brave Search API + MCP has a hosted endpoint at https://api.search.brave.com/res/v1/web/search and Firecrawl MCP at https://mcp.firecrawl.dev/v2/mcp.
Are Brave Search API + MCP and Firecrawl MCP open source?
Yes. Brave Search API + MCP is open source (MIT). Firecrawl MCP is open source (MIT).
Other comparisons with Brave Search API + MCP or Firecrawl MCP
- Web Search Tool on Amazon Bedrock AgentCore vs Brave Search API + MCP
- Web Search Tool on Amazon Bedrock AgentCore vs Firecrawl MCP
- Arcmira vs Brave Search API + MCP
- Arcmira vs Firecrawl MCP
- Grounding with Bing Search vs Brave Search API + MCP
- Grounding with Bing Search vs Firecrawl MCP
- Brave Search API + MCP vs Cloudflare Web Search API
- Brave Search API + MCP vs DeepSeek Search and Fetch API
- Brave Search API + MCP vs Exa API + MCP
- Brave Search API + MCP vs Hyperresearch
- Brave Search API + MCP vs Kagi Search API
- Brave Search API + MCP vs Linkup
- Brave Search API + MCP vs Mojeek Web Search API
- Brave Search API + MCP vs NewsCatcher
- Brave Search API + MCP vs Parallel Search and Task APIs
- Brave Search API + MCP vs Perplexity Search API
- Brave Search API + MCP vs SearchAPI.io
- Brave Search API + MCP vs SerpApi
- Brave Search API + MCP vs Serper
- Brave Search API + MCP vs SERPHouse
- Brave Search API + MCP vs SerpKite
- Brave Search API + MCP vs SpecStream
- Brave Search API + MCP vs Tavily API + MCP
- Brave Search API + MCP vs TinyFish Search
- Brave Search API + MCP vs Valyu
- Brave Search API + MCP vs You.com APIs
- 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 Firecrawl MCP
- Firecrawl MCP vs jevcrawl
- Firecrawl MCP vs Microlink
- Firecrawl MCP vs Scrape.do
- Firecrawl MCP vs Scrapfly
- Firecrawl MCP vs ScrapingAnt
- Brave Search API + MCP vs Grep AI
Machine-readable
- This page as Markdown
/compare/brave-search-mcp-vs-firecrawl-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/brave-search-mcp.json·/api/v1/tools/firecrawl-mcp.json - From a terminal
anchor compare brave-search-mcp firecrawl-mcp(the CLI) - Over MCP
compare_tools {"a": "brave-search-mcp", "b": "firecrawl-mcp"}at/mcp, no key