# Web Search API Eval (remote · websearch-api-eval.psberkeleymba.workers.dev)

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

- Trust score: 71/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `websearch-api-eval.psberkeleymba.workers.dev`: 71/100 (this document), [markdown](https://verifymcp.io/servers/psinglap-websearch-api-eval/websearch-api-eval.md), [page](https://verifymcp.io/servers/psinglap-websearch-api-eval/websearch-api-eval)
- npm · `websearch-api-eval-mcp`: 63/100, [markdown](https://verifymcp.io/servers/psinglap-websearch-api-eval/websearch-api-eval-mcp.md), [page](https://verifymcp.io/servers/psinglap-websearch-api-eval/websearch-api-eval-mcp)

## Channel facts

- Endpoint: `https://websearch-api-eval.psberkeleymba.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 924 tokens (~84/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http psinglap-websearch-api-eval 'https://websearch-api-eval.psberkeleymba.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "psinglap-websearch-api-eval": {
      "url": "https://websearch-api-eval.psberkeleymba.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "psinglap-websearch-api-eval": {
      "type": "http",
      "url": "https://websearch-api-eval.psberkeleymba.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.psinglap-websearch-api-eval]
url = "https://websearch-api-eval.psberkeleymba.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "psinglap-websearch-api-eval": {
      "type": "remote",
      "url": "https://websearch-api-eval.psberkeleymba.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add psinglap-websearch-api-eval --url 'https://websearch-api-eval.psberkeleymba.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  psinglap-websearch-api-eval:
    url: "https://websearch-api-eval.psberkeleymba.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "psinglap-websearch-api-eval": {
      "Transport": "http",
      "Url": "https://websearch-api-eval.psberkeleymba.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add psinglap-websearch-api-eval -t streamable-http -u 'https://websearch-api-eval.psberkeleymba.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "psinglap-websearch-api-eval": {
      "type": "http",
      "url": "https://websearch-api-eval.psberkeleymba.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 70, +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.

### 2026-11-01 (score 69, +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.

### 2026-10-30 (score 68, +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.

### 2026-10-28 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 66)

First indexed and scored.

## MCP tools (11)

### `get_overall_results` (~75 tokens)

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 developer activation time.

### `get_scorecard` (~87 tokens)

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.

Input parameters:

- `use_case` (string, required): overall, gtm, insurance or finance

### `compare_providers` (~117 tokens)

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').

Input parameters:

- `metric_filter` (string): Optional keyword to keep only matching metrics
- `providers` (array, required): Two or more of: You.com, Tavily, Exa, Parallel
- `use_case` (string): overall, gtm, insurance or finance

### `recommend_provider` (~89 tokens)

Recommend a 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.

Input parameters:

- `agent_need` (string): What the agent does, e.g. 'voice agent answering in under a second' or 'finance research'

### `list_questions` (~63 tokens)

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.

Input parameters:

- `use_case` (string): all, gtm, insurance or finance

### `get_question` (~80 tokens)

Get a 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).

Input parameters:

- `id` (string, required): Question ID, e.g. G3, I4 or F5

### `get_charts` (~94 tokens)

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.

Input parameters:

- `chart_id` (string): e.g. overall_scorecard, finance_key_metrics, gtm_query_grid, time_steps_activation
- `use_case` (string): Filter the list

### `get_methodology` (~53 tokens)

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` (~39 tokens)

Run it yourself

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` (~47 tokens)

Search the benchmark

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

Input parameters:

- `query` (string, required): What to look for

### `fetch` (~43 tokens)

Fetch a benchmark document

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

Input parameters:

- `id` (string, required): Document ID from search

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/psinglap-websearch-api-eval/websearch-api-eval#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 69
- 2026-11-01: 69
- 2026-10-31: 68
- 2026-10-30: 68
- 2026-10-29: 67
- 2026-10-28: 67
- 2026-10-27: 66

## Common questions

### 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 71 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://websearch-api-eval.psberkeleymba.workers.dev/mcp
- Repository: https://github.com/psinglap/websearch-api-eval
- Website: https://psinglap.github.io/websearch-api-eval/
- Changelog RSS feed: https://verifymcp.io/servers/psinglap-websearch-api-eval/websearch-api-eval.xml
- Changelog JSON feed: https://verifymcp.io/servers/psinglap-websearch-api-eval/websearch-api-eval.json
- HTML version of this page: https://verifymcp.io/servers/psinglap-websearch-api-eval/websearch-api-eval