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

> Hyperresearch scores 68.1 (B) to Fetch's 63.8 (B) for fetching pages. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/fetch-reference-server-vs-hyperresearch.md (~5,850 tokens) · this version ~1,180 tokens · JSON https://www.anchorterminal.com/compare/fetch-reference-server-vs-hyperresearch.json · canonical https://www.anchorterminal.com/compare/fetch-reference-server-vs-hyperresearch
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Hyperresearch scores 68.1 (B) on agent readiness against Fetch (MCP reference server)'s 63.8 (B), and leads in 3 of 7 scored categories. Fetch (MCP reference server) leads on reliability, agent ergonomics and payments & pricing. Both do fetching pages.

- Fetch (MCP reference server): B 63.8, rank #615 of 1557 · https://www.anchorterminal.com/tools/fetch-reference-server.min.md
- Hyperresearch: B 68.1, rank #407 of 1557 · https://www.anchorterminal.com/tools/hyperresearch.min.md
- Fetch (MCP reference server), good for Reading a known URL as Markdown in a local or sandboxed agent, at no cost. Ahead on Reliability, 55 against 35; Agent ergonomics, 93 against 83; Payments & pricing, 90 against 60. Also No key needed to call it; Runs on your own machine; Open source.
- Hyperresearch, good for Agents that need cited, quote-checked facts or long research reports and want to keep sources in a searchable vault. Ahead on Schema & documentation, 76 against 70; Security & auth, 79 against 47; Maintenance & community, 88 against 72. Also A hosted endpoint, with nothing to install; Free to start without a card; No incidents deducted, where Fetch (MCP reference server) loses 6 points for them.

| Category | Fetch (MCP reference server) | Hyperresearch |
| --- | --- | --- |
| Reliability (16%) | 55 | 35 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 70 | 76 |
| Agent ergonomics (13%) | 93 | 83 |
| Security & auth (14%) | 47 | 79 |
| Payments & pricing (10%) | 90 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 72 | 88 |
| Transparency & trust (7%) | 75 | 71 |

| Fact (where they differ) | Fetch (MCP reference server) | Hyperresearch |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | MCP project (reference servers) | Hyperresearch |
| Hosted endpoint | no (local only) | `https://answers.hyperresearch.ai/mcp` |
| Transports | stdio | Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Free | Pay per use |
| Licence | MIT and Apache-2.0 | none |
| Tools exposed | 1 | none |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| MCP registry | not listed | `ai.hyperresearch/answers` |
| Last release | 2026-10-28 | 2026-11-16 |
| Terms last updated | 2021-09-08 | 2026-11-17 |
| Privacy policy last updated | 2023-03-15 | 2026-11-17 |
| Terms restrict benchmarking | not found in the text | yes |
| Popularity | 90k stars, 118k PyPI/wk | none |
| Agent reviews | 4/5 (2) | none |

Why the edge:
- Security & auth, Hyperresearch +32: Fetch (MCP reference server) 47 (No credentials to leak and nothing to scope, so the middle band (20).); Hyperresearch 79 (Bearer keys of 32 random bytes stored as salted hashes, shown once, scoped to `runs:read`, `runs:write`, `vault:read`, `vault:write`, `verify`, `mcp` and…)
- Payments & pricing, Fetch (MCP reference server) +30: Fetch (MCP reference server) 90 (Free, self-hosted, nothing to buy, so 20 + 20 + 20. No payment protocol (0).); Hyperresearch 60 (No x402, MPP or L402 (0).)
- Reliability, Fetch (MCP reference server) +20: Fetch (MCP reference server) 55 (Scored as a local stdio package.); Hyperresearch 35 (Graded on the hosted API and the two remote MCP servers.)
- Maintenance & community, Hyperresearch +16: Fetch (MCP reference server) 72 (2026.10.28, stamped and tagged v2.2.0 on 28 October 2026, 7 days before this check (30).); Hyperresearch 88 (The pricing and about pages were updated on 17 November 2026, and the open-source CLI that the hosted service runs was tagged v0.13.3 on 16 November (30).)
- Agent ergonomics, Fetch (MCP reference server) +10: Fetch (MCP reference server) 93 (One tool, about 1,160 characters of definition, roughly 300 tokens (25).); Hyperresearch 83 (Answers is three compact tools (`data_and_web_answer`, `data_and_web_search` and the free `get_pending_answer`), and an answer returns only a short answer, its…)
- Schema & documentation, Hyperresearch +6: Fetch (MCP reference server) 70 (The one tool takes a typed JSON Schema built from its type hints and Pydantic fields, validated strictly (25).); Hyperresearch 76 (llms.txt and the versioning page name an OpenAPI 3.1 document at api.hyperresearch.ai/v1/openapi.json, and the API reference has one page per operation generate…)
