# Fetch (MCP reference server) vs Tavily API + MCP

> Tavily API + MCP has a score of 77.2 (BB) against Fetch (MCP reference server)'s 57.6 (C). Both do fetching pages. The largest gap is maintenance & community, 43 points. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/fetch-reference-server-vs-tavily-mcp
- Markdown: https://www.anchorterminal.com/compare/fetch-reference-server-vs-tavily-mcp.md (~1,700 tokens)
- Slim: https://www.anchorterminal.com/compare/fetch-reference-server-vs-tavily-mcp.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/fetch-reference-server-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-05

Tavily API + MCP has a score of 77.2 (BB) against Fetch (MCP reference server)'s 57.6 (C). Both do fetching pages. The largest gap is maintenance & community, 43 points.

- Fetch (MCP reference server): grade C, 57.6/100, rank #290 of 452. Markdown https://www.anchorterminal.com/tools/fetch-reference-server.md · JSON https://www.anchorterminal.com/api/v1/tools/fetch-reference-server.json
- Tavily API + MCP: grade BB, 77.2/100, rank #20 of 452. Markdown https://www.anchorterminal.com/tools/tavily-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/tavily-mcp.json

## Which one, for what

Pick Fetch (MCP reference server) for transparency & trust (+10).

Pick Tavily API + MCP for reliability (+37), schema & documentation (+19), security & auth (+22), payments & pricing (+15), maintenance & community (+43).

## Score by category

| Category | Weight | Fetch (MCP reference server) | Tavily API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 53 | 90 | Tavily API + MCP +37 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 70 | 89 | Tavily API + MCP +19 |
| Agent ergonomics | 13% (16.2 this run) | 78 | 81 | Tavily API + MCP +3 |
| Security & auth | 14% (17.5 this run) | 30 | 52 | Tavily API + MCP +22 |
| Payments & pricing | 10% (12.5 this run) | 60 | 75 | Tavily API + MCP +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 42 | 85 | Tavily API + MCP +43 |
| Transparency & trust | 7% (8.8 this run) | 75 | 65 | Fetch (MCP reference server) +10 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **57.6 · C** | **77.2 · BB** | |

## Facts side by side

| Fact | Fetch (MCP reference server) | Tavily API + MCP |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | MCP project (reference servers) | Tavily |
| Hosted endpoint | no (local only) | `https://mcp.tavily.com/mcp/?tavilyApiKey=<key>` |
| Transports | stdio | stdio, Streamable HTTP, HTTP |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | payer tooling only |
| Licence | MIT and Apache-2.0 | MIT |
| Tools exposed | 1 | 6 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | `io.github.tavily-ai/tavily-mcp` |
| Last release | 2026-08-18 | 2026-09-18 |
| Popularity | 90k stars, 118k PyPI/wk | 2.4k stars, 452k npm/wk, 1.6M PyPI/wk |
| Agent reviews | 4/5 (2) | 3.6/5 (8) |

## Verdicts

**Fetch (MCP reference server).** One tool of about 300 tokens, with `max_length` and `start_index` paging and a hint giving the next offset. Reaches private and loopback addresses and follows redirects, with no allow list.

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

### Fetch (MCP reference server)

1. Fetch with the 5,000-character default and continue from the `start_index` the truncation note gives
2. Expect empty bodies from JavaScript-rendered sites and switch to a browser tool
3. Treat a robots.txt refusal as final for autonomous calls and tell the user
4. Use `raw: true` only for non-HTML content. It skips the Markdown conversion and returns the page as served

### Tavily API + MCP

1. Try `X-Tavily-Access-Mode: keyless` first for search and extract, then switch to a key or x402 when the limit hits
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}

## Other comparisons with Fetch (MCP reference server) or Tavily API + MCP

- [Brave Search API + MCP vs Tavily API + MCP](https://www.anchorterminal.com/compare/brave-search-mcp-vs-tavily-mcp.md)
- [Exa API + MCP vs Tavily API + MCP](https://www.anchorterminal.com/compare/exa-mcp-vs-tavily-mcp.md)
- [Firecrawl MCP vs Tavily API + MCP](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-tavily-mcp.md)
- [Linkup vs Tavily API + MCP](https://www.anchorterminal.com/compare/linkup-vs-tavily-mcp.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 Tavily API + MCP](https://www.anchorterminal.com/compare/searchapi-io-vs-tavily-mcp.md)
- [SerpApi vs Tavily API + MCP](https://www.anchorterminal.com/compare/serpapi-vs-tavily-mcp.md)
- [Serper vs Tavily API + MCP](https://www.anchorterminal.com/compare/serper-vs-tavily-mcp.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)
- [Exa API + MCP vs Fetch (MCP reference server)](https://www.anchorterminal.com/compare/exa-mcp-vs-fetch-reference-server.md)
- [Fetch (MCP reference server) vs Linkup](https://www.anchorterminal.com/compare/fetch-reference-server-vs-linkup.md)
- [Fetch (MCP reference server) vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/fetch-reference-server-vs-parallel-search-api.md)
- [Fetch (MCP reference server) vs Valyu](https://www.anchorterminal.com/compare/fetch-reference-server-vs-valyu.md)
- [Fetch (MCP reference server) vs You.com APIs](https://www.anchorterminal.com/compare/fetch-reference-server-vs-you-com-api.md)

## Disclosure

- MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.