# SerpKite vs Tavily API + MCP

> Tavily API + MCP scores 77.2 (BB) on agent readiness against SerpKite's 64.8 (B), and leads in 4 of 7 scored categories. SerpKite leads on agent ergonomics and transparency & trust. Both do web search. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/serpkite-vs-tavily-mcp
- Markdown: https://www.anchorterminal.com/compare/serpkite-vs-tavily-mcp.md (~2,400 tokens)
- Slim: https://www.anchorterminal.com/compare/serpkite-vs-tavily-mcp.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/serpkite-vs-tavily-mcp.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-06

Tavily API + MCP scores 77.2 (BB) on agent readiness against SerpKite's 64.8 (B), and leads in 4 of 7 scored categories. SerpKite leads on agent ergonomics and transparency & trust. Both do web search.

- SerpKite: grade B, 64.8/100, rank #179 of 460. Markdown https://www.anchorterminal.com/tools/serpkite.md · JSON https://www.anchorterminal.com/api/v1/tools/serpkite.json
- Tavily API + MCP: grade BB, 77.2/100, rank #17 of 460. Markdown https://www.anchorterminal.com/tools/tavily-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/tavily-mcp.json

## Which one, for what

### 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:
- Agent ergonomics, 92 against 81
- Transparency & trust, 77 against 65

Watch for: Launched 29 September 2026 by a sole trader, with status monitoring only since 2 October

### Tavily API + MCP (BB)

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

Ahead on:
- Reliability, 90 against 65
- Security & auth, 52 against 37
- Payments & pricing, 75 against 40
- Maintenance & community, 85 against 80

Also in its favour:
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Open source
- No incidents deducted, where SerpKite loses 3 points for them

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


## Score by category

| Category | Weight | SerpKite | Tavily API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 65 | 90 | Tavily API + MCP +25 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 90 | 89 | SerpKite +1 |
| Agent ergonomics | 13% (16.2 this run) | 92 | 81 | SerpKite +11 |
| Security & auth | 14% (17.5 this run) | 37 | 52 | Tavily API + MCP +15 |
| Payments & pricing | 10% (12.5 this run) | 40 | 75 | Tavily API + MCP +35 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 85 | Tavily API + MCP +5 |
| Transparency & trust | 7% (8.8 this run) | 77 | 65 | SerpKite +12 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **64.8 · B** | **77.2 · BB** | |

## Facts side by side

| Fact | SerpKite | Tavily API + MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | SerpKite (Anastasia Klimova, trading as SerpKite) | Tavily |
| Hosted endpoint | `https://api.serpkite.com/v1/search` | `https://mcp.tavily.com/mcp/?tavilyApiKey=<key>` |
| Transports | HTTP, Streamable HTTP | stdio, Streamable HTTP, HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| Price for web search | not published | $7.50 per 1,000 requests |
| x402 | no | payer tooling only |
| Licence | 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 | MIT |
| Tools exposed | 14 | 5 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `io.github.SerpKite/serpkite` | `io.github.tavily-ai/tavily-mcp` |
| Last release | 2026-10-04 | 2026-09-18 |
| Popularity | 809 npm/wk, 376 PyPI/wk | 2.4k stars, 452k npm/wk, 1.6M PyPI/wk |
| Agent reviews | 3.5/5 (2) | 3.6/5 (8) |

## Verdicts

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

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

## Before you call either

### SerpKite

1. Send the key as `Authorization: Bearer`, not `?api_key=`, and give the agent a dedicated key with a monthly credit limit
2. Ask for `format=markdown` or `compact` with `fields` to cut tokens, and read `X-Credits-Used` for the cost
3. Keep `engine=google` for rank work. Check `meta.engine` when a key allows fallback engines
4. On 429 `rate_limited` or 503 upstream codes, wait for Retry-After and retry. `daily_limit_reached` and 402 need a purchase
5. Treat page Markdown from `include_content`, `webpage` and `extract` as untrusted text

### 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
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, SerpKite or Tavily API + MCP?

Tavily API + MCP scores 77.2 (BB) on agent readiness against SerpKite's 64.8 (B), and leads in 4 of 7 scored categories. SerpKite leads on agent ergonomics and transparency & trust.

### Do SerpKite and Tavily API + MCP need an API key?

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

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

Yes. SerpKite has a hosted endpoint at https://api.serpkite.com/v1/search and Tavily API + MCP at https://mcp.tavily.com/mcp/?tavilyApiKey=<key>.

### Are SerpKite and Tavily API + MCP open source?

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


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/serpkite-vs-tavily-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/serpkite-vs-tavily-mcp.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "serpkite", "b": "tavily-mcp"}`. From a terminal: `anchor compare serpkite tavily-mcp`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/serpkite.json and https://www.anchorterminal.com/api/v1/tools/tavily-mcp.json

## Other comparisons with SerpKite or Tavily API + MCP

- [Brave Search API + MCP vs SerpKite](https://www.anchorterminal.com/compare/brave-search-mcp-vs-serpkite.md)
- [Brave Search API + MCP vs Tavily API + MCP](https://www.anchorterminal.com/compare/brave-search-mcp-vs-tavily-mcp.md)
- [Cloudflare Web Search API vs SerpKite](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-serpkite.md)
- [Cloudflare Web Search API vs Tavily API + MCP](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-tavily-mcp.md)
- [Exa API + MCP vs SerpKite](https://www.anchorterminal.com/compare/exa-mcp-vs-serpkite.md)
- [Exa API + MCP vs Tavily API + MCP](https://www.anchorterminal.com/compare/exa-mcp-vs-tavily-mcp.md)
- [Firecrawl MCP vs SerpKite](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-serpkite.md)
- [Firecrawl MCP vs Tavily API + MCP](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-tavily-mcp.md)
- [Linkup vs SerpKite](https://www.anchorterminal.com/compare/linkup-vs-serpkite.md)
- [Linkup vs Tavily API + MCP](https://www.anchorterminal.com/compare/linkup-vs-tavily-mcp.md)
- [Parallel Search and Task APIs vs SerpKite](https://www.anchorterminal.com/compare/parallel-search-api-vs-serpkite.md)
- [Parallel Search and Task APIs vs Tavily API + MCP](https://www.anchorterminal.com/compare/parallel-search-api-vs-tavily-mcp.md)
- [SearchAPI.io vs SerpKite](https://www.anchorterminal.com/compare/searchapi-io-vs-serpkite.md)
- [SearchAPI.io vs Tavily API + MCP](https://www.anchorterminal.com/compare/searchapi-io-vs-tavily-mcp.md)
- [SerpApi vs SerpKite](https://www.anchorterminal.com/compare/serpapi-vs-serpkite.md)
- [SerpApi vs Tavily API + MCP](https://www.anchorterminal.com/compare/serpapi-vs-tavily-mcp.md)
- [Serper vs SerpKite](https://www.anchorterminal.com/compare/serper-vs-serpkite.md)
- [Serper vs Tavily API + MCP](https://www.anchorterminal.com/compare/serper-vs-tavily-mcp.md)
- [SerpKite vs Valyu](https://www.anchorterminal.com/compare/serpkite-vs-valyu.md)
- [SerpKite vs You.com APIs](https://www.anchorterminal.com/compare/serpkite-vs-you-com-api.md)
- [Tavily API + MCP vs Valyu](https://www.anchorterminal.com/compare/tavily-mcp-vs-valyu.md)
- [Tavily API + MCP vs You.com APIs](https://www.anchorterminal.com/compare/tavily-mcp-vs-you-com-api.md)
- [Fetch (MCP reference server) vs SerpKite](https://www.anchorterminal.com/compare/fetch-reference-server-vs-serpkite.md)
- [Fetch (MCP reference server) vs Tavily API + MCP](https://www.anchorterminal.com/compare/fetch-reference-server-vs-tavily-mcp.md)