Web Search API Eval
REMOTE · WEBSEARCH-API-EVAL.PSBERKELEYMBA.WORKERS.DEV · 2 COMPONENTS
Web search API benchmark for AI agents: You.com, Tavily, Exa, Parallel. Results and charts.
Available components
Last scanned (1 day ago)
Scores higher than 55% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 924 tokens (~84/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://websearch-api-eval.psberkeleymba.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=psberkeleymba.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 511af518fc7457005ecf4a47cb2301cde9f |
| SANs: *.psberkeleymba.workers.dev, psberkeleymba.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of websearch-api-eval.psberkeleymba.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://websearch-api-eval.psberkeleymba.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://websearch-api-eval.psberkeleymba.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_providers Compare providers ~117
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').
| Name | Type | Req | Description |
|---|---|---|---|
| metric_filter | string | – | Optional keyword to keep only matching metrics |
| providers | array | yes | Two or more of: You.com, Tavily, Exa, Parallel |
| use_case | string | – | overall, gtm, insurance or finance |
No output schema declared.
No examples provided.
fetch Fetch a benchmark document ~43
Full text of one benchmark document by its ID (for example question-F5, scorecard-finance, overall, methodology).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Document ID from search |
No output schema declared.
No examples provided.
get_charts Charts ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chart_id | string | – | e.g. overall_scorecard, finance_key_metrics, gtm_query_grid, time_steps_activation |
| use_case | string | – | Filter the list |
No output schema declared.
No examples provided.
get_methodology Methodology ~53
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_overall_results Overall results ~75
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 developer activation time.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_question Get a question ~80
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).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Question ID, e.g. G3, I4 or F5 |
No output schema declared.
No examples provided.
get_scorecard Scorecard ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| use_case | string | yes | overall, gtm, insurance or finance |
No output schema declared.
No examples provided.
how_to_run_locally Run it yourself ~39
How to rerun this benchmark on your own machine with your own API keys, including on your own queries. Nothing runs on this server.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_questions List questions ~63
The 30 benchmark questions (G1-G10 GTM, I1-I10 insurance, F1-F10 finance): ID, what the agent is asked, the search call and freshness.
| Name | Type | Req | Description |
|---|---|---|---|
| use_case | string | – | all, gtm, insurance or finance |
No output schema declared.
No examples provided.
recommend_provider Recommend a provider ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_need | string | – | What the agent does, e.g. 'voice agent answering in under a second' or 'finance research' |
No output schema declared.
No examples provided.
search Search the benchmark ~47
Search the Web Search API Eval benchmark (results, questions, methodology, charts, how to run). Returns matching document IDs, titles and URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What to look for |
No output schema declared.
No examples provided.
How do I install the Web Search API Eval MCP server?
Web Search API Eval is a hosted endpoint at https://websearch-api-eval.psberkeleymba.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · websearch-api-eval.psberkeleymba.workers.dev
claude mcp add --transport http psinglap-websearch-api-eval 'https://websearch-api-eval.psberkeleymba.workers.dev/mcp'
What is the Web Search API Eval MCP server?
Web Search API Eval is an MCP server listed in the public MCP registry as io.github.psinglap/websearch-api-eval. Web search API benchmark for AI agents: You.com, Tavily, Exa, Parallel. Results and charts. This page covers its hosted endpoint (https://websearch-api-eval.psberkeleymba.workers.dev/mcp).
Is the Web Search API Eval MCP server safe to use?
Web Search API Eval scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Web Search API Eval MCP server expose?
Web Search API Eval exposes 11 tools: get_overall_results, get_scorecard, compare_providers, recommend_provider, list_questions, and 6 more. Their descriptions and schemas cost roughly 787 tokens of context every time the server is loaded.
Does the Web Search API Eval MCP server require authentication?
No. We connected to Web Search API Eval without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Web Search API Eval MCP server still maintained?
Web Search API Eval is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.