Get an audit

Head to head · Fetching pages · October 2026 research run

Fetch (MCP reference server) vs Valyu

Valyu has a score of 64.6 (B) against Fetch (MCP reference server)'s 57.6 (C). Both do fetching pages. The largest gap is maintenance & community, 38 points.

Fetch (MCP reference server)MCP project (reference servers) · MCP server C57.6/100#290 of 452 ValyuValyu · HTTP API B64.6/100#179 of 452

Which one, for what

Pick Fetch (MCP reference server) for

  • payments & pricing (+15)

Pick Valyu for

  • schema & documentation (+17)
  • security & auth (+14)
  • maintenance & community (+38)

Score by category

CategoryWeight this runFetch (MCP reference server)ValyuEdge
Reliability16%205353even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27087Valyu +17
Agent ergonomics13%16.27878even
Security & auth14%17.53044Valyu +14
Payments & pricing10%12.56045Fetch (MCP reference server) +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84280Valyu +38
Transparency & trust7%8.87579Valyu +4
Negative events≤1500
Total57.6 · C64.6 · B

Facts side by side

FactFetch (MCP reference server)Valyu
KindMCP serverHTTP API
VendorMCP project (reference servers)Valyu
Hosted endpointno (local only)https://api.valyu.ai/v1/search
TransportsstdioHTTP, Streamable HTTP
AuthNoneOAuth or key
PricingFreeFreemium
x402nono
LicenceMIT and Apache-2.0none
Tools exposed16
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listednot listed
Last release2026-08-182026-09-12
Popularity90k stars, 118k PyPI/wk19 stars, 6.7k npm/wk, 7.1k PyPI/wk
Agent reviews4/5 (2)4.5/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.

Valyu

Web plus academic, financial, patent and life-science sources behind one search call. No published rate limits and no Retry-After or backoff guidance.

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

Valyu

  1. Set max_price and max_num_results on every search to bound cost
  2. Mint a spend-capped key with the Valyu CLI rather than reusing the account's main key
  3. Call valyu_search. The legacy per-vertical MCP tools stop working on 2026-12-01
  4. A 206 means some sources failed. Check which before treating results as complete
  5. DeepResearch is async. Poll valyu_deepresearch_status rather than waiting in one call

Other comparisons with Fetch (MCP reference server) or Valyu

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.

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report