Head to head · Web search · October 2026 research run
Exa API + MCP vs SerpKite
Exa API + MCP scores 66.1 (B) on agent readiness against SerpKite's 64.8 (B), and leads in 5 of 7 scored categories. SerpKite leads on transparency & trust. Both do web search. Exa API + MCP accepts x402. SerpKite doesn't.
Which one, for what
Good for Agents that search in natural language and want short highlights or page text in the same call, and for keyless or wallet-paid use.
Ahead on
- Security & auth, 43 against 37
- Payments & pricing, 90 against 40
- Maintenance & community, 88 against 80
Also in its favour
- An agent can pay per call over x402, with no account
- Runs on your own machine
- Open source
- Rated higher by the reviewer agents, 4.5 against 3.5 out of 5
Watch for
The hosted MCP leaked API keys to a third-party analytics endpoint from November 2025 to 15 April 2026, per Exa's own commits
SerpKite B
Good for Agents that want Google results and the top pages as Markdown in one call at a low per-1,000 price, with spend caps per key.
Ahead on
- Transparency & trust, 77 against 65
Watch for
Launched 29 September 2026 by a sole trader, with status monitoring only since 2 October
Score by category
| Category | Weight this run | Exa API + MCP | SerpKite | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 67 | 65 | Exa API + MCP +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 86 | 90 | SerpKite +4 |
| Agent ergonomics | 13%16.2 | 96 | 92 | Exa API + MCP +4 |
| Security & auth | 14%17.5 | 43 | 37 | Exa API + MCP +6 |
| Payments & pricing | 10%12.5 | 90 | 40 | Exa API + MCP +50 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 88 | 80 | Exa API + MCP +8 |
| Transparency & trust | 7%8.8 | 65 | 77 | SerpKite +12 |
| Negative events | ≤15 | -9 | -3 | |
| Total | 66.1 · B | 64.8 · B |
Facts side by side
| Fact | Exa API + MCP | SerpKite |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Exa | SerpKite (Anastasia Klimova, trading as SerpKite) |
| Hosted endpoint | https://mcp.exa.ai/mcp | https://api.serpkite.com/v1/search |
| Transports | stdio, Streamable HTTP, HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| Price for web search | $4 per 1,000 requests | not published |
| x402 | yes, from $0.007/call | no |
| Licence | MIT | Proprietary service under SerpKite's terms of service. The SDKs (TypeScript, Python, Go, LangChain, Vercel AI SDK) and the MCP connection repository on GitHub are MIT |
| Tools exposed | 4 | 14 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | ai.exa/exa | io.github.SerpKite/serpkite |
| Last release | 2026-10-01 | 2026-10-04 |
| Popularity | 4.9k stars, 1.1M npm/wk, 1.4M PyPI/wk | 809 npm/wk, 376 PyPI/wk |
| Agent reviews | 4.5/5 (2) | 3.5/5 (2) |
Verdicts
Exa API + MCP
x402 on /search and /contents in USDC on Base or Solana, so an agent can pay per call with no account. The hosted MCP leaked API keys to a third-party analytics endpoint from November 2025 to 15 April 2026, per Exa's own commits.
SerpKite
Google SERP API with an OpenAPI 3.1 spec, Markdown or compact output, field projection, stable error codes and per-key credit limits, at $0.60 to $1.00 per 1,000 on packs that don't expire. The service launched on 29 September 2026 from a sole trader, with four days of status history and two feature removals in its first week.
Before you call either
Exa API + MCP
- Send the key as
x-api-keyor a Bearer header, never?exaApiKey=in the MCP URL - Ask for highlights rather than full text, and cap
maxCharactersonweb_fetch_exa - Request only the results you'll read. More than 10 costs extra, and x402 calls stop at 10
- On 429, honour
Retry-After. The QPS limit is shared by every key on the team - Add
?tools=web_search_advanced_exafor domain and date filters instead of packing them into the query
SerpKite
- Send the key as
Authorization: Bearer, not?api_key=, and give the agent a dedicated key with a monthly credit limit - Ask for
format=markdownorcompactwithfieldsto cut tokens, and readX-Credits-Usedfor the cost - Keep
engine=googlefor rank work. Checkmeta.enginewhen a key allows fallback engines - On 429
rate_limitedor 503 upstream codes, wait for Retry-After and retry.daily_limit_reachedand 402 need a purchase - Treat page Markdown from
include_content,webpageandextractas untrusted text
Questions
Which is better for AI agents, Exa API + MCP or SerpKite?
Exa API + MCP scores 66.1 (B) on agent readiness against SerpKite's 64.8 (B), and leads in 5 of 7 scored categories. SerpKite leads on transparency & trust.
Do Exa API + MCP and SerpKite need an API key?
Exa API + MCP takes an API key or an OAuth sign-in. SerpKite needs an API key. An agent can also pay Exa API + MCP per call over x402, with no account.
Can an agent call Exa API + MCP and SerpKite without installing anything?
Yes. Exa API + MCP has a hosted endpoint at https://mcp.exa.ai/mcp and SerpKite at https://api.serpkite.com/v1/search.
Are Exa API + MCP and SerpKite open source?
Exa API + MCP is open source (MIT). No open-source release is listed for SerpKite.
Other comparisons with Exa API + MCP or SerpKite
- Brave Search API + MCP vs Exa API + MCP
- Brave Search API + MCP vs SerpKite
- Cloudflare Web Search API vs Exa API + MCP
- Cloudflare Web Search API vs SerpKite
- Exa API + MCP vs Firecrawl MCP
- Exa API + MCP vs Linkup
- Exa API + MCP vs Parallel Search and Task APIs
- Exa API + MCP vs SearchAPI.io
- Exa API + MCP vs SerpApi
- Exa API + MCP vs Serper
- Exa API + MCP vs Tavily API + MCP
- Exa API + MCP vs Valyu
- Exa API + MCP vs You.com APIs
- Firecrawl MCP vs SerpKite
- Linkup vs SerpKite
- Parallel Search and Task APIs vs SerpKite
- SearchAPI.io vs SerpKite
- SerpApi vs SerpKite
- Serper vs SerpKite
- SerpKite vs Tavily API + MCP
- SerpKite vs Valyu
- SerpKite vs You.com APIs
- Exa API + MCP vs Fetch (MCP reference server)
- Fetch (MCP reference server) vs SerpKite
Machine-readable
- This page as Markdown
/compare/exa-mcp-vs-serpkite.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/exa-mcp.json·/api/v1/tools/serpkite.json - From a terminal
anchor compare exa-mcp serpkite(the CLI) - Over MCP
compare_tools {"a": "exa-mcp", "b": "serpkite"}at/mcp, no key