# Fetch (MCP reference server) vs Linkup

> Linkup has a score of 69.1 (B) against Fetch (MCP reference server)'s 57.6 (C). Both do fetching pages. The largest gap is maintenance & community, 41 points. Linkup accepts x402. Fetch (MCP reference server) doesn't. Category scores, facts, verdicts and agent notes side by side.

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

Linkup has a score of 69.1 (B) against Fetch (MCP reference server)'s 57.6 (C). Both do fetching pages. The largest gap is maintenance & community, 41 points. Linkup accepts x402. Fetch (MCP reference server) doesn't.

- 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
- Linkup: grade B, 69.1/100, rank #116 of 452. Markdown https://www.anchorterminal.com/tools/linkup.md · JSON https://www.anchorterminal.com/api/v1/tools/linkup.json

## Which one, for what

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

Pick Linkup for reliability (+17), schema & documentation (+18), payments & pricing (+20), maintenance & community (+41).

## Score by category

| Category | Weight | Fetch (MCP reference server) | Linkup | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 53 | 70 | Linkup +17 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 70 | 88 | Linkup +18 |
| Agent ergonomics | 13% (16.2 this run) | 78 | 76 | Fetch (MCP reference server) +2 |
| Security & auth | 14% (17.5 this run) | 30 | 32 | Linkup +2 |
| Payments & pricing | 10% (12.5 this run) | 60 | 80 | Linkup +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 42 | 83 | Linkup +41 |
| Transparency & trust | 7% (8.8 this run) | 75 | 64 | Fetch (MCP reference server) +11 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **57.6 · C** | **69.1 · B** | |

## Facts side by side

| Fact | Fetch (MCP reference server) | Linkup |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | MCP project (reference servers) | Linkup |
| Hosted endpoint | no (local only) | `https://api.linkup.so/v1/search` |
| Transports | stdio | HTTP, Streamable HTTP, stdio |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | yes, from $0.01/call |
| Licence | MIT and Apache-2.0 | none |
| Tools exposed | 1 | 4 |
| 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 | `so.linkup.mcp/linkup-mcp-server` |
| Last release | 2026-08-18 | 2026-09-30 |
| Popularity | 90k stars, 118k PyPI/wk | 29 stars, 54k npm/wk, 84k PyPI/wk |
| Agent reviews | 4/5 (2) | 4/5 (2) |

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

**Linkup.** Per-call prices from $0.005, and no credit taken for errors, missing parameters or empty results. 429 covers both exhausted credit and rate limiting, with no `Retry-After`.

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

### Linkup

1. On 429, check the credit balance before backing off. The same code means out of credit
2. Pass `reasoningDepth: "S"` to research unless you need more. The MCP default is L at $1.50
3. Start with `depth=fast` and `outputType=searchResults`. Deep costs $0.05, ten times as much
4. Send the key as an `Authorization: Bearer` header, not `?apiKey=` or a command-line argument
5. Poll `linkup-get-research` with the task id. Research runs take minutes

## Other comparisons with Fetch (MCP reference server) or Linkup

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