# Fetch (MCP reference server) vs Linkup (slim)

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

- Full: https://www.anchorterminal.com/compare/fetch-reference-server-vs-linkup.md (~1,650 tokens) · this version ~380 tokens · JSON https://www.anchorterminal.com/compare/fetch-reference-server-vs-linkup.json · canonical https://www.anchorterminal.com/compare/fetch-reference-server-vs-linkup
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-04

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): C 57.6, rank #290 of 452 · https://www.anchorterminal.com/tools/fetch-reference-server.min.md
- Linkup: B 69.1, rank #116 of 452 · https://www.anchorterminal.com/tools/linkup.min.md
- Pick Fetch (MCP reference server) for transparency & trust (+11). Pick Linkup for reliability (+17), schema & documentation (+18), payments & pricing (+20), maintenance & community (+41).

| Category | Fetch (MCP reference server) | Linkup |
| --- | --- | --- |
| Reliability (16%) | 53 | 70 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 70 | 88 |
| Agent ergonomics (13%) | 78 | 76 |
| Security & auth (14%) | 30 | 32 |
| Payments & pricing (10%) | 60 | 80 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 42 | 83 |
| Transparency & trust (7%) | 75 | 64 |