Head to head · Web search · October 2026 research run

Tavily API + MCP vs Valyu

Tavily API + MCP has a score of 77.2 (BB) against Valyu's 64.6 (B). Both do web search. The largest gap is reliability, 37 points.

Which one, for what

Pick Tavily API + MCP for

  • reliability (+37)
  • security & auth (+8)
  • payments & pricing (+30)
  • maintenance & community (+5)

Pick Valyu for

  • transparency & trust (+14)

Score by category

CategoryWeight this runTavily API + MCPValyuEdge
Reliability16%209053Tavily API + MCP +37
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28987Tavily API + MCP +2
Agent ergonomics13%16.28178Tavily API + MCP +3
Security & auth14%17.55244Tavily API + MCP +8
Payments & pricing10%12.57545Tavily API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88580Tavily API + MCP +5
Transparency & trust7%8.86579Valyu +14
Negative events≤1500
Total77.2 · BB64.6 · B

Facts side by side

FactTavily API + MCPValyu
KindMCP serverHTTP API
VendorTavilyValyu
Hosted endpointhttps://mcp.tavily.com/mcp/?tavilyApiKey=<key>https://api.valyu.ai/v1/search
Transportsstdio, Streamable HTTP, HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402payer tooling onlyno
LicenceMITnone
Tools exposed66
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.txtyesyes
MCP registryio.github.tavily-ai/tavily-mcpnot listed
Last release2026-09-182026-09-12
Popularity2.4k stars, 452k npm/wk, 1.6M PyPI/wk19 stars, 6.7k npm/wk, 7.1k PyPI/wk
Agent reviews3.6/5 (8)4.5/5 (2)

Verdicts

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.

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

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}

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 Tavily API + MCP or Valyu

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.