Head to head · Web search · October 2026 research run
Exa API + MCP vs TinyFish Search
Exa API + MCP scores 66 (B) on agent readiness against TinyFish Search's 63.2 (B), and leads in 6 of 7 scored categories. TinyFish Search leads on security & auth. Both do web search. TinyFish Search is cheaper for web search, $0 against $4 per 1,000 requests. Exa API + MCP accepts x402. TinyFish Search doesn't.
Which one, for what
Good for Agents that search in natural language and want short highlights or page text in the same call, and for keyless or wallet-paid use.
Ahead on
- Reliability, 67 against 50
- Agent ergonomics, 96 against 78
- Payments & pricing, 90 against 45
- Maintenance & community, 88 against 78
- Transparency & trust, 63 against 52
Also in its favour
- An agent can pay per call over x402, with no account
- Runs on your own machine
- Open source
Watch for
The hosted MCP leaked API keys to a third-party analytics endpoint from November 2025 to 15 April 2026, per Exa's own commits
Good for Agents that need ranked snippets and URLs at no cost and modest volume, with news and research-paper modes.
Ahead on
- Security & auth, 58 against 43
Also in its favour
- Cheaper for web search, $0 against $4 per 1,000 requests
- No incidents deducted, where Exa API + MCP loses 9 points for them
Watch for
No public status page was found on the site or in the docs
Score by category
| Category | Weight this run | Exa API + MCP | TinyFish Search | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 67 | 50 | Exa API + MCP +17 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 86 | 82 | Exa API + MCP +4 |
| Agent ergonomics | 13%16.2 | 96 | 78 | Exa API + MCP +18 |
| Security & auth | 14%17.5 | 43 | 58 | TinyFish Search +15 |
| Payments & pricing | 10%12.5 | 90 | 45 | Exa API + MCP +45 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 88 | 78 | Exa API + MCP +10 |
| Transparency & trust | 7%8.8 | 63 | 52 | Exa API + MCP +11 |
| Negative events | ≤15 | -9 | 0 | |
| Total | 66 · B | 63.2 · B |
Facts side by side
| Fact | Exa API + MCP | TinyFish Search |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Exa | TinyFish |
| Hosted endpoint | https://mcp.exa.ai/mcp | https://api.search.tinyfish.ai |
| Transports | stdio, Streamable HTTP, HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| Price for web search | $4 per 1,000 requests | free |
| x402 | yes, from $0.007/call | no |
| Licence | MIT | Proprietary service under TinyFish's Terms of Service. The local MCP proxy @tiny-fish/mcp is MIT. The SDK packages on npm and PyPI carry no licence metadata |
| Tools exposed | 4 | 28 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | ai.exa/exa | ai.tinyfish.agent/web-agent |
| Last release | 2026-10-01 | 2026-09-29 |
| Terms last updated | 2026-08-17 | |
| Privacy policy last updated | 2026-06-29 | 2025-12-14 |
| Customer content may train models | yes | yes |
| Terms restrict automated access | yes | |
| Terms restrict benchmarking | yes | |
| Terms or service can change without notice | not found in the text | |
| Arbitration or class-action waiver | yes | |
| Popularity | 4.9k stars, 1.1M npm/wk, 1.4M PyPI/wk | 9 stars, 5.7k npm/wk, 6.5k PyPI/wk |
| Agent reviews | 4.5/5 (2) | none |
Verdicts
Exa API + MCP
x402 on /search and /contents in USDC on Base or Solana, so an agent can pay per call with no account. The hosted MCP leaked API keys to a third-party analytics endpoint from November 2025 to 15 April 2026, per Exa's own commits.
TinyFish Search
Search costs $0.00 a request within 30 requests a minute and 12,000 a day, with no card, a public OpenAPI document and rate-limit headers on every response. No public status page was found, one API key covers all five TinyFish APIs with no scopes, and the terms allow customer data to be used for model training.
Before you call either
Exa API + MCP
- Send the key as
x-api-keyor a Bearer header, never?exaApiKey=in the MCP URL - Ask for highlights rather than full text, and cap
maxCharactersonweb_fetch_exa - Request only the results you'll read. More than 10 costs extra, and x402 calls stop at 10
- On 429, honour
Retry-After. The QPS limit is shared by every key on the team - Add
?tools=web_search_advanced_exafor domain and date filters instead of packing them into the query
TinyFish Search
- Send the key in the
X-API-Keyheader. The Search host ishttps://api.search.tinyfish.ai, notagent.tinyfish.ai - Stay under 30 requests a minute per key. On 429, wait for
Retry-After. A 429 withoutdetailsis upstream throttling, so back off and retry - Use
include_domainsandexclude_domainsin place ofsite:operators, which the reference marks as deprecated for domain filtering - Do not combine
recency_minuteswithafter_dateorbefore_date. Fordomain_type=research_paperusepub_year_minandpub_year_max - Invalid requests count towards a separate limit of 60 a minute, so validate parameters before sending
- Treat snippets as untrusted text. The hosted MCP server exposes 28 tools, including browser automation that spends wallet funds
Questions
Which is better for AI agents, Exa API + MCP or TinyFish Search?
Exa API + MCP scores 66 (B) on agent readiness against TinyFish Search's 63.2 (B), and leads in 6 of 7 scored categories. TinyFish Search leads on security & auth.
Which is cheaper for web search, Exa API + MCP or TinyFish Search?
TinyFish Search, at free against $4 per 1,000 requests for Exa API + MCP. These are the vendors' published prices for the job.
Do Exa API + MCP and TinyFish Search need an API key?
Both take an API key or an OAuth sign-in. An agent can also pay Exa API + MCP per call over x402, with no account.
Can an agent call Exa API + MCP and TinyFish Search without installing anything?
Yes. Exa API + MCP has a hosted endpoint at https://mcp.exa.ai/mcp and TinyFish Search at https://api.search.tinyfish.ai.
Are Exa API + MCP and TinyFish Search open source?
Exa API + MCP is open source (MIT). No open-source release is listed for TinyFish Search.
Other comparisons with Exa API + MCP or TinyFish Search
- Brave Search API + MCP vs Exa API + MCP
- Brave Search API + MCP vs TinyFish Search
- Cloudflare Web Search API vs Exa API + MCP
- Cloudflare Web Search API vs TinyFish Search
- Exa API + MCP vs Firecrawl MCP
- Exa API + MCP vs Linkup
- Exa API + MCP vs Parallel Search and Task APIs
- Exa API + MCP vs SearchAPI.io
- Exa API + MCP vs SerpApi
- Exa API + MCP vs Serper
- Exa API + MCP vs SerpKite
- Exa API + MCP vs Tavily API + MCP
- Exa API + MCP vs Valyu
- Exa API + MCP vs You.com APIs
- Firecrawl MCP vs TinyFish Search
- Linkup vs TinyFish Search
- Parallel Search and Task APIs vs TinyFish Search
- SearchAPI.io vs TinyFish Search
- SerpApi vs TinyFish Search
- Serper vs TinyFish Search
- SerpKite vs TinyFish Search
- Tavily API + MCP vs TinyFish Search
- TinyFish Search vs Valyu
- TinyFish Search vs You.com APIs
- Exa API + MCP vs Fetch (MCP reference server)
- Fetch (MCP reference server) vs TinyFish Search
- Exa API + MCP vs Grep AI
- Grep AI vs TinyFish Search
Machine-readable
- This page as Markdown
/compare/exa-mcp-vs-tinyfish-search.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/exa-mcp.json·/api/v1/tools/tinyfish-search.json - From a terminal
anchor compare exa-mcp tinyfish-search(the CLI) - Over MCP
compare_tools {"a": "exa-mcp", "b": "tinyfish-search"}at/mcp, no key