MCP server for advanced web search using Tavily
Nothing to run from here
Web Search API Eval is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
trust score
12
tools declared
local
or remote
—
downloads a day
What it does
Web search API benchmark for AI agents: You.com, Tavily, Exa, Parallel. Results and charts.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user web-search-api-eval-mcp '--' npx -y websearch-api-eval-mcp
# 2 — ask your agent for something these tools do
# get_overall_results, get_scorecard, compare_providers and 9 more
Web Search API Eval costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PSAll 1 server
psinglap1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user web-search-api-eval-mcp '--' npx -y websearch-api-eval-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://websearch-api-eval.psberkeleymba.workers.dev/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http web-search-api-eval-mcp https://websearch-api-eval.psberkeleymba.workers.dev/mcpFree on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take YDC_API_KEY (Optional. You.com API key, used only by run_live_search), TAVILY_API_KEY (Optional. Tavily API key, used only by run_live_search), EXA_API_KEY (Optional. Exa API key, used only by run_live_search), PARALLEL_API_KEY (Optional. Parallel API key, used only by run_live_search) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Headline findings and the overall scorecard across all 30 queries (90 calls per API): accuracy, fully correct, precision@5,
No parameter schema on file.
Full metric scorecard for one use case (gtm, insurance, finance) or 'overall'. Metrics: search-only latency p50/p95 (server and client),
| Parameter | Type | Required | Notes |
|---|---|---|---|
| use_case | string | yes | overall, gtm, insurance or finance |
Compare two or more of You.com, Tavily, Exa and Parallel side by side, overall or within one use case, optionally filtered to metrics
| Parameter | Type | Required | Notes |
|---|---|---|---|
| providers | array | yes | Two or more of: You.com, Tavily, Exa, Parallel |
| use_case | string | no | overall, gtm, insurance or finance |
| metric_filter | string | no | Optional keyword to keep only matching metrics |
Which web search API fits an agent, based on this benchmark: live voice/chat turns, deep research, semantic or long-tail queries,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_need | string | no | What the agent does, e.g. 'voice agent answering in under a second' or 'finance research' |
The 30 benchmark questions (G1-G10 GTM, I1-I10 insurance, F1-F10 finance): ID, what the agent is asked, the search call and freshness.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| use_case | string | no | all, gtm, insurance or finance |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Question ID, e.g. G3, I4 or F5 |
The published graphs: overall scorecard, key metrics and per-query grids for GTM, insurance and finance, and developer activation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chart_id | string | no | e.g. overall_scorecard, finance_key_metrics, gtm_query_grid, time_steps_activation |
| use_case | string | no | Filter the list |
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.
No parameter schema on file.
How to rerun this benchmark on your own machine with your own API keys, including on your own queries. Nothing runs on this server.
No parameter schema on file.
Search the Web Search API Eval benchmark (results, questions, methodology, charts, how to run). Returns matching document IDs, titles and URLs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What to look for |
Full text of one benchmark document by its ID (for example question-F5, scorecard-finance, overall, methodology).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Document ID from search |
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Web Search API Eval or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 96 / 100
Release 1.1.0 · scanned 28 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings1 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest3eda8b7ec60f954a907ea589de70e46ff706bb7d6b56d73540cef30cf544f138
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (12 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_overall_results | no tags | |
| get_scorecard | no tags | |
| compare_providers | no tags | |
| recommend_provider | untrusted-input | untrusted-input: keyword "web_search" |
| list_questions | no tags | |
| get_question | no tags | |
| get_charts | no tags | |
| get_methodology | no tags | |
| how_to_run_locally | no tags | |
| search | untrusted-input | untrusted-input: keyword "web_search" |
| fetch | untrusted-input | untrusted-input: keyword "fetch" |
| run_live_search | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest3eda8b7ec60f954a
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.1.0. Pin a release below and the command asks for exactly that one.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Web Search API Eval can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.