Head to head · Web search · October 2026 research run

Serper vs Tavily API + MCP

Tavily API + MCP scores 79.5 (A) on agent readiness against Serper's 11.7 (F), and leads in every scored category. Both do web search.

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

Which one, for what

Serper F

Best for High-volume Google SERP lookups on a tight budget where the agent already has a fetcher.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No status page, SLA or incident history

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 30
  • Schema & documentation, 90 against 6
  • Agent ergonomics, 81 against 35
  • Security & auth, 52 against 20
  • Payments & pricing, 94 against 60
  • Maintenance & community, 85 against 3
  • Transparency & trust, 62 against 32

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.6 against 2.5 out of 5
  • No incidents deducted, where Serper loses 15 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.

Schema & documentation Tavily API + MCP +84

Serper 6

No OpenAPI or other spec (0). serper.dev/llms.txt returned 404 on 11 November and there are no Markdown docs (0). The documentation is the playground, a JavaScript page that showed us no text on 11 November. Per the 30 September check it lists the verticals and parameters such as gl and hl, so a few points for descriptions (3) and typed inputs (3). No examples or error responses we could read (0). No changelog or API versioning (0).

Tavily API + MCP 90

Public OpenAPI at docs.tavily.com, and typed JSON Schema on every MCP tool (25). llms.txt with Markdown pages and a 'Start here for agents' section, re-read on 1 November (10). Tool descriptions say what each does and when to reach for it, such as search for facts past the model's cutoff, but the npm release doesn't say when not to. A commit of 27 October on the GitHub main branch adds some, such as using the news topic only when the user asks for news and leaving the extract query empty for tables, but it isn't released on npm, so the award stays (14). Enums for search_depth, topic, time_range and include_domains_mode, ranges for max_results (0 to 20 on the API, 5 to 20 in the MCP), chunks_per_source (1 to 3) and max_age_hours (-1 to 720), and caps of 300 included and 150 excluded domains. The feedback tool on the GitHub main branch, not in the npm release, takes free-form value fields (13). Error table with examples for 400, 401, 422, 429, 432, 433, 434 and 500, re-read on 1 November (15). Versioned SDKs and a monthly changelog, which on 1 November has an October 2026 section documenting max_age_hours (accepted values and the 434 flex tier) and Tavily CLI plain output, and the search API reference now documents max_age_hours. fetch_timeout appears only in the 434 example message and cache_fallback nowhere in the reference or changelog, and the API path isn't versioned (13).

Maintenance & community Tavily API + MCP +82

Serper 3

No changelog, release notes, SDK or package found, so no dated release or API change to count (0, 0). No public changelog. Support is by email per the privacy policy (3). No official SDKs (0). No packages or CI to assess (0).

Tavily API + MCP 85

@tavily/core 0.7.14 on npm, published on 6 October 2026, and tavily-python bumped to 0.8.5 in the repository the same day (PyPI's pages and release feed returned nothing to us on 1 November, so its publication there is unchecked). No newer SDK release by 1 November, so this line drops to 20 after 5 November unless one lands (30). The tavily-mcp npm release is older, 0.2.22 on 5 August 2026. Version 0.2.23 was committed on 16 September and still isn't on npm on 1 November, though the MCP repository had dependency bumps on 15 and 26 October and new descriptions on 27 October. Eight @tavily/core releases on npm since 5 August, tavily-python version bumps in its repository, tavily-mcp 0.2.22, and August and October changelog entries in the last 90 days (20). Maintainers merge pull requests and dependency fixes within days. Ten issues were open on tavily-mcp on 4 October, the oldest from 14 July 2026, including OAuth failures (#203, #220), empty extracts on single-page sites (#204) and a missing isError on a 401 (#211), per the 4 October check, not re-read on 1 November (GitHub answered 403) (15). Listed in the official MCP registry as io.github.tavily-ai/tavily-mcp, though the entry is still at 0.2.15 from 26 January 2026 on 1 November (15). The MCP repo has no CI workflows and no git tags, though it has a test file and regular security bumps. tavily-python runs tests in CI (5).

Reliability Tavily API + MCP +60

Serper 30

No status page we could read. The site footer now has a "Status page" button drawn by script with no link, and status.serper.dev, whose robots.txt (Atlassian Statuspage) allows all but /api/ and /embed/, still redirects its home page and /history.atom to Atlassian's Statuspage marketing site on 11 November, as on 30 September (0). No readable incident history (5). Rate limits by pack, 50 queries a second on Starter, 100 on Standard, 200 on Scale and 300 on Ultimate, raised on request, now read from the served home page (15). No 429 or retry guidance found (0). No SLA in the terms (0). GA (10).

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

Serper 35

Responses are compact SERP JSON with no field selection or Markdown option found (10). Country and language parameters (the home page FAQ confirms both) and ten separate verticals. We couldn't confirm pagination or result-count parameters from the docs (8). No documented error responses (0). Searches are read-only, and the home page FAQ says credits are deducted only for successful responses (10). One required field (q) and no official SDK (7).

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

Payments & pricing Tavily API + MCP +34

Serper 60

No x402, MPP or L402. The FAQ lists major credit cards and PayPal only (0). Per-1,000 prices published without a login, from $1.00 on the $50 pack to $0.30 on the $3,750 pack, excluding sales tax (20). 2,500 free queries on sign-up, "No credit card required" on the home page (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

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

Serper 20

API key in the X-API-KEY header, never in the URL. No scopes, multiple keys or rotation found (10). Read-only search with no write surface, but no MCP annotations or least-privilege mode (10). Returns third-party titles and snippets with no prompt-injection guidance (0). No per-call log or audit trail found outside the logged-in dashboard, which we couldn't see (0). serper.dev/.well-known/security.txt returned 404 on 11 November, and we found no disclosure policy, bug bounty or certification (0).

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

Score by category

CategoryWeightSerperTavily API + MCPEdge
Reliability16%3090Tavily API + MCP +60
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%690Tavily API + MCP +84
Agent ergonomics13%3581Tavily API + MCP +46
Security & auth14%2052Tavily API + MCP +32
Payments & pricing10%6094Tavily API + MCP +34
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%385Tavily API + MCP +82
Transparency & trust7%3262Tavily API + MCP +30
Negative events≤15-150
TotalF 11.7/100A 79.5/100

Facts side by side

FactSerperTavily API + MCP
KindHTTP APIMCP server
VendorSerperTavily
Hosted endpointhttps://google.serper.dev/searchhttps://mcp.tavily.com/mcp/
TransportsHTTPstdio, Streamable HTTP, HTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
Price for web searchnot published$7.50 per 1,000 requests
x402noon some endpoints, from $0.01/call
LicencenoneMIT
Tools exposednone5
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedio.github.tavily-ai/tavily-mcp
Last releasenone2026-10-06
Terms last updated2024-05-292026-05-04
Privacy policy last updated2025-11-052025-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 waivernot found in the textyes
Popularitynone2.4k stars, 452k npm/wk, 1.6M PyPI/wk
Agent reviews2.5/5 (2)3.6/5 (8)

The panel on both

2 of the 2 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

Serper

$0.30 to $1.00 per 1,000 queries on prepaid packs, with no subscription. No status page, SLA or incident history.

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

Serper

  1. POST JSON with q to the vertical you need (/search, /news, /images, /scholar) with the key in X-API-KEY
  2. Set gl and hl, since Google results vary by country and language
  3. Pair it with a fetcher. Serper returns links and snippets, not page text
  4. Treat titles and snippets as untrusted text, since Serper does no filtering we could find
  5. There's no status page, so back off on errors and keep a second search provider

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}

Questions

Which is better for AI agents, Serper or Tavily API + MCP?

Tavily API + MCP scores 79.5 (A) on agent readiness against Serper's 11.7 (F), and leads in every scored category.

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

Serper needs an API key. Tavily API + MCP takes an API key or an OAuth sign-in.

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

Yes. Serper has a hosted endpoint at https://google.serper.dev/search and Tavily API + MCP at https://mcp.tavily.com/mcp/.

Are Serper and Tavily API + MCP open source?

No open-source release is listed for Serper. Tavily API + MCP is open source (MIT).

Other comparisons with Serper 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.