Head to head · Web search · October 2026 research run

Firecrawl MCP vs Tavily API + MCP

Tavily API + MCP scores 79.5 (A) on agent readiness against Firecrawl MCP's 78.1 (A), and leads in 2 of 7 scored categories. Firecrawl MCP leads on agent ergonomics, security & auth and transparency & trust. 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

  • Agent ergonomics, 92 against 81
  • Security & auth, 70 against 52
  • Transparency & trust, 75 against 62

Watch for

No x402 or other machine payment

Tavily API + MCP A

Best for An agent that needs search plus page text in one call and has no account yet.

Ahead on

  • Reliability, 90 against 78
  • Payments & pricing, 94 against 75

Also in its favour

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

Watch for

x402 covers advanced search only, not extract, map, crawl or research

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 Tavily API + MCP +19

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.

Tavily API + MCP 94

Official x402 at x402.tavily.com sells advanced search only, $0.01 in USDC on Base. An unpaid POST to /search returned 402 on 1 November with an x402 version 2 envelope offering the exact scheme on eip155:8453 for 10000 units (0.01 USDC), and a second agent-pay option on aws:base for 0.016, described as advanced mode. Extract, map, crawl and research aren't sold over x402 (15). Credit costs per endpoint and $0.008 a credit pay as you go, published without a login and unchanged on 1 November (20). 1,000 free credits a month, no card, re-read on 1 November (20). Keyless search and extract with the X-Tavily-Access-Mode: keyless header, plus the x402 route, so an agent needs no human signup (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 15 of 40 is 3.75 of 10, and the other lines' 60 is 90 at 30 each, so 75 is 94.

Security & auth Firecrawl MCP +18

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

Tavily API + MCP 52

Revocable keys, separate development and production keys, and the Logs API filters by key, so several keys per account work. The hosted MCP adds OAuth but maps it to one dashboard key with no scopes (22). The MCP README and docs still lead with ?tavilyApiKey= in the URL on 1 November (minus 10). The five tools in the npm release all read. The GitHub main branch adds tavily_feedback, which posts scores to Tavily, the hosted server's tool list is unknown, and there's no read-only toolset (10). The home page says requests pass through 'security, privacy, and content validation layers that block PII leakage, prompt injection, and malicious sources'. That's a claim with no technical detail in the docs, plus a safe_search flag for adult content, per the 1 October check (7). The Logs API (filter by key and endpoint since August 2026) and include_usage give per-call visibility (13). SOC 2 and ISO 27001 named on the privacy page, per the 4 October check, and the MCP repo patches vulnerable dependencies about monthly (seven updates on 26 October). The trust centre is JavaScript-only for us (per the 1 October check, not re-read on 1 November), www.tavily.com/.well-known/security.txt returned 404 on 1 November, and no bug bounty found (10).

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

Tavily API + MCP 62

MCP server MIT and SDKs open, API closed under platform terms (18). The privacy policy (last updated 24 November 2025, re-read on 1 November) keeps data for the life of the account with no fixed periods, says query data may be used to improve future responses unless a contract says otherwise, and describes no zero-retention option. No DPA on the privacy page, and the trust centre didn't render for us (per the 1 October check, not re-read on 1 November) (15). No deprecation policy or dated deprecation notices found, and none in the changelog on 1 November (0). Names Stripe, Google Analytics, Google Tag Manager, PostHog and third-party search index providers such as Google, with US processing under Standard Contractual Clauses (14).

Reliability Tavily API + MCP +12

Firecrawl MCP 78

Better Stack status page at status.firecrawl.dev with history (20). Four incidents in the 90 days to 1 November 2026, all partial degradations of api.firecrawl.dev, the longest 56 minutes on the /interact prompt field on 27 August (06:00 to 06:56 UTC in the feed) and the others 7, 16 and 46 minutes, with none after 15 September. The 20 July /interact incident has left the window (20). Rate limits published per plan and endpoint, from 10 scrapes a minute on Free to 10,000 on Scale, plus concurrent browsers and a per-IP daily cap for keyless use, re-read on 1 November (15). The Errors reference, linked from the rate-limit page, says 429s carry Retry-After when available, marks every error retryable or not, and gives backoff advice per code. No idempotency keys for calls that start crawl, agent or monitor jobs (13 of 15). SLA on Enterprise only, per the pricing page, with no terms published (0). GA (10). 20 + 20 + 15 + 13 + 0 + 10 = 78.

Tavily API + MCP 90

incident.io status page at status.tavily.com with separate API, MCP and website components (20). One incident in the 90 days from 3 August, website degraded performance on 17 September 2026, and none since per the status feed re-read on 1 November. The API and MCP showed 100% per the 1 October check (30). Published limits, re-read on 1 November, 100 requests a minute on development keys and 1,000 on production, crawl 100 and research 20 task creations on both (15). 429 carries Retry-After and the docs say to use that value and the status code rather than parse the message. Since October a 434 tells non-paying plans that live fetching with max_age_hours is refused under load, with the advice to retry or omit it (15). The pricing page lists 'Enterprise-grade support and SLAs' for the custom Enterprise plan but publishes no SLA terms, per the 17 October check, and none were found in the docs index or terms (0). GA (10).

Agent ergonomics Firecrawl MCP +11

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

Tavily API + MCP 81

Five tools in the published tavily-mcp 0.2.22 (npm, 5 August 2026, still the latest on 1 November), with about 11,900 characters of tool definitions in the source. The unreleased 0.2.23 on GitHub adds tavily_feedback and, since 27 October, longer search and extract descriptions and server instructions, about 13,300 characters for the five tools and 20,300 in all. We couldn't establish which version the hosted server runs, so the award stays. No tool filter found. Raw content, images and answers are opt-in, which keeps API responses small (18). max_results, domain include and exclude lists, time_range, start and end dates, country, and crawl depth, breadth and limit (20). 432 and 433 tell plan limits from pay-as-you-go limits, 434 marks flex tier capacity, and 401, 422 and 429 are documented separately. Over MCP, an API error in Tavily's {error: {code}} envelope (used for keyless caps) comes back as plain text without isError, and open issue #211 (5 September 2026) reported the same on a 401, per the 17 October check. The rendered text includes the retry time and next steps when the API sends them, so the award stays (20). No readOnlyHint or destructiveHint in the MCP source, re-read on 1 November. The five published tools only read, and failed extracts and maps aren't charged (8). Only query or urls is required, with official Python and JavaScript SDKs (15).

Score by category

CategoryWeightFirecrawl MCPTavily API + MCPEdge
Reliability16%7890Tavily API + MCP +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9190Firecrawl MCP +1
Agent ergonomics13%9281Firecrawl MCP +11
Security & auth14%7052Firecrawl MCP +18
Payments & pricing10%7594Tavily API + MCP +19
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8785Firecrawl MCP +2
Transparency & trust7%7562Firecrawl MCP +13
Negative events≤15-30
TotalA 78.1/100A 79.5/100

Facts side by side

FactFirecrawl MCPTavily API + MCP
KindMCP serverMCP server
VendorFirecrawl (Mendable)Tavily
Hosted endpointhttps://mcp.firecrawl.dev/v2/mcphttps://mcp.tavily.com/mcp/
Transportsstdio, Streamable HTTP, SSE (legacy)stdio, Streamable HTTP, HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
Price for web searchnot published$7.50 per 1,000 requests
x402noon some endpoints, from $0.01/call
LicenceMITMIT
Tools exposed275
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.firecrawl/firecrawl-mcp-serverio.github.tavily-ai/tavily-mcp
Last release2026-10-272026-10-06
Terms last updated2024-11-052026-05-04
Privacy policy last updated2024-12-262025-11-24
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularity7.5k stars, 29k npm/wk2.4k stars, 452k npm/wk, 1.6M PyPI/wk
Agent reviews3.5/5 (8)3.6/5 (8)

The panel on both

4 of the 8 reviewers who reviewed both rate Tavily API + 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.

Tavily API + MCP

Keyless search and extract, plus a free 1,000 credits a month with no card. x402 covers advanced search only, not extract, map, crawl or research, and the npm MCP release has trailed the GitHub source since August.

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

Tavily API + MCP

  1. Try X-Tavily-Access-Mode: keyless first for search and extract. Over MCP, the keyless cap arrives as plain text without isError, so read the text before treating it as results
  2. Send the key in Authorization: Bearer, not ?tavilyApiKey= in the MCP URL
  3. On 429, wait for Retry-After. A 432 or 433 means a spend limit, and retrying won't help. A 434 on a free plan means retry shortly or drop max_age_hours
  4. Run /map before /crawl to bound the crawl, since crawl is billed as map plus extract
  5. Research is async and runs 4 to 250 credits. Create the task, then poll /research/{request_id}

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 Tavily API + MCP?

Tavily API + MCP scores 79.5 (A) on agent readiness against Firecrawl MCP's 78.1 (A), and leads in 2 of 7 scored categories. Firecrawl MCP leads on agent ergonomics, security & auth and transparency & trust.

Do Firecrawl MCP and Tavily API + MCP need an API key?

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

Can an agent call Firecrawl MCP and Tavily API + MCP without installing anything?

Yes. Firecrawl MCP has a hosted endpoint at https://mcp.firecrawl.dev/v2/mcp and Tavily API + MCP at https://mcp.tavily.com/mcp/.

Are Firecrawl MCP and Tavily API + MCP open source?

Yes. Firecrawl MCP is open source (MIT). Tavily API + MCP is open source (MIT).

Other comparisons with Firecrawl MCP or Tavily API + MCP

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.