NestDaddy

Web Search API Eval

io.github.psinglap/websearch-api-eval · v1.1.0

Web search API benchmark for AI agents: You.com, Tavily, Exa, Parallel. Results and charts.

Connect Remote server

Terminal
claude mcp add --transport http websearch-api-eval https://websearch-api-eval.psberkeleymba.workers.dev/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "websearch-api-eval": {
      "url": "https://websearch-api-eval.psberkeleymba.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "websearch-api-eval": {
      "type": "http",
      "url": "https://websearch-api-eval.psberkeleymba.workers.dev/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://websearch-api-eval.psberkeleymba.workers.dev/mcp

Tools 11 found in our last check

  • get_overall_results

    Headline findings and the overall scorecard across all 30 queries (90 calls per API): accuracy, fully correct, precision@5, freshness, empty responses, failed calls, latency p50/p95, cost per correct answer. Also the per-use-case summary, which API fits which agent, and develope…

  • get_scorecard

    Full metric scorecard for one use case (gtm, insurance, finance) or 'overall'. Metrics: search-only latency p50/p95 (server and client), calls under 1 s, accuracy, freshness (% in window, newest relevant result age), content in one call, tokens, search cost.

  • compare_providers

    Compare two or more of You.com, Tavily, Exa and Parallel side by side, overall or within one use case, optionally filtered to metrics whose name contains a keyword (e.g. 'latency', 'accuracy', 'fresh', 'cost', 'empty').

  • recommend_provider

    Which web search API fits an agent, based on this benchmark: live voice/chat turns, deep research, semantic or long-tail queries, docs lookups, or a specific use case (GTM, insurance, finance). Returns the guidance with the supporting numbers.

  • list_questions

    The 30 benchmark questions (G1-G10 GTM, I1-I10 insurance, F1-F10 finance): ID, what the agent is asked, the search call and freshness.

  • get_question

    One benchmark question by ID (e.g. G3, I4, F5): the task, search call, parameters, answer key with sources, and what each API returned with its accuracy score (0-2, mean of 3 runs).

  • get_charts

    The published graphs: overall scorecard, key metrics and per-query grids for GTM, insurance and finance, and developer activation. Without chart_id, lists them with titles and image links; with chart_id, also returns the image.

  • get_methodology

    How the benchmark was run and graded: query design, identical request parameters, 3 runs per query, latency timing, SimpleQA and FreshQA grading, the 10 metrics and the standards they follow, and limits.

  • how_to_run_locally

    How to rerun this benchmark on your own machine with your own API keys, including on your own queries. Nothing runs on this server.

  • search

    Search the Web Search API Eval benchmark (results, questions, methodology, charts, how to run). Returns matching document IDs, titles and URLs.

  • fetch

    Full text of one benchmark document by its ID (for example question-F5, scorecard-finance, overall, methodology).

Details

Endpointhttps://websearch-api-eval.psberkeleymba.workers.dev/mcp (Streamable HTTP)
Package[email protected] (NPM, stdio)
First published27 Oct 2026
Last updated27 Oct 2026
Registry nameio.github.psinglap/websearch-api-eval

More search and web servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.