Head to head · Web search · October 2026 research run

Brave Search API + MCP vs Serper

Brave Search API + MCP scores 64.1 (B) on agent readiness against Serper's 11.7 (F), and leads in 6 of 7 scored categories. Serper leads on payments & pricing. Both do web search.

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

Which one, for what

Brave Search API + MCP B

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

  • Reliability, 80 against 30
  • Schema & documentation, 72 against 6
  • Agent ergonomics, 72 against 35
  • Security & auth, 58 against 20
  • Maintenance & community, 77 against 3
  • Transparency & trust, 81 against 32

Also in its favour

  • Runs on your own machine
  • Open source
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

Watch for

The x402 pay-per-call proxy answered 404 on 1 November 2026, and its guide is gone from the docs

Serper F

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

Ahead on

  • Payments & pricing, 60 against 30

Also in its favour

  • Free to start without a card

Watch for

No status page, SLA or incident history

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 Brave Search API + MCP +74

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.

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

Schema & documentation Brave Search API + MCP +66

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.

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

Reliability Brave Search API + MCP +50

Brave Search API + MCP 80

status.brave.app (Better Stack) lists a Brave Search API component monitoring api.search.brave.com, showing 100% uptime with every two-day mark from 6 May to 1 November 2026 operational, and a Search API Dashboard monitor at 99.996%. The 1 October note read the page as unmonitored, but its marks go back to May (20). No incident in the 90 days from 3 August on the page or its feed, and the docs' own status log still ends on 27 March 2025, so a clean record on a readable page (20). Rate limits published per plan, 50 QPS Search, 2 QPS Answers, 100 QPS Spellcheck and Autosuggest, in a 1-second sliding window, per the 1 October check (15). 429 on overrun, X-RateLimit-Reset in seconds and exponential backoff guidance. Searches are reads, so no idempotency keys are needed (15). No SLA on any self-serve plan (0). GA (10). 20+20+15+15+0+10 = 80.

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

Transparency & trust Brave Search API + MCP +49

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.

Serper 32

Closed service. The terms exist (updated 29 May 2024, UK law) but name no legal entity, only 'Serper' (8). The privacy policy (last reviewed 5 November 2025) says the service 'should normally not lead to the processing of personal data' and keeps most personal data for the life of the account, but states no retention period for queries or results (10). No deprecation policy or dated notices (0). Data processors are described by category without names, with transfers outside the EEA under an adequacy decision or standard contractual clauses (5).

Security & auth Brave Search API + MCP +38

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.

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

Agent ergonomics Brave Search API + MCP +37

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.

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

Score by category

CategoryWeightBrave Search API + MCPSerperEdge
Reliability16%8030Brave Search API + MCP +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%726Brave Search API + MCP +66
Agent ergonomics13%7235Brave Search API + MCP +37
Security & auth14%5820Brave Search API + MCP +38
Payments & pricing10%3060Serper +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%773Brave Search API + MCP +74
Transparency & trust7%8132Brave Search API + MCP +49
Negative events≤15-3-15
TotalB 64.1/100F 11.7/100

Facts side by side

FactBrave Search API + MCPSerper
KindHTTP APIHTTP API
VendorBraveSerper
Hosted endpointhttps://api.search.brave.com/res/v1/web/searchhttps://google.serper.dev/search
Transportsstdio, Streamable HTTP, HTTPHTTP
AuthOAuth or keyAPI key
PricingPay per useFreemium
Price for web search$5 per 1,000 requestsnot published
x402nono
LicenceMITnone
Tools exposed8none
Read-only variant documentednono
llms.txtyesno
MCP registryio.github.brave/brave-search-mcp-servernot listed
Last release2026-09-17none
Terms last updated2026-09-012024-05-29
Privacy policy last updated2026-08-252025-11-05
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity1.4k stars, 22k npm/wknone
Agent reviews3.5/5 (2)2.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Brave Search 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

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.

Serper

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

Before you call either

Brave Search API + MCP

  1. Call /res/v1/llm/context when you need page text rather than links. It saves a separate fetch
  2. Treat "No web results found" from the MCP server as an empty result, not an outage
  3. On 429, wait for X-RateLimit-Reset seconds. There's no Retry-After header
  4. Skip brave_summarizer. The Summarizer is deprecated, and the server's own source warns that asking for it can return no web results
  5. 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

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

Questions

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

Brave Search API + MCP scores 64.1 (B) on agent readiness against Serper's 11.7 (F), and leads in 6 of 7 scored categories. Serper leads on payments & pricing.

Do Brave Search API + MCP and Serper need an API key?

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

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

Yes. Brave Search API + MCP has a hosted endpoint at https://api.search.brave.com/res/v1/web/search and Serper at https://google.serper.dev/search.

Are Brave Search API + MCP and Serper open source?

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

Other comparisons with Brave Search API + MCP or Serper

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.