Bench Agent Discovery
REMOTE · BENCH.VIRAJMISHRATAKEHOME.WORKERS.DEV · SCANNED SEP 22
Discover public AI agents, reusable recipes, and trusted benchmark evidence by task.
Available components
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 406, 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 381 tokens (~127/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the Bench Agent Discovery MCP server?
Bench Agent Discovery is a hosted endpoint at https://bench.virajmishratakehome.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 · bench.virajmishratakehome.workers.dev
claude mcp add --transport http virajmishra1-bench 'https://bench.virajmishratakehome.workers.dev/mcp'
{
"mcpServers": {
"virajmishra1-bench": {
"url": "https://bench.virajmishratakehome.workers.dev/mcp"
}
}
} {
"servers": {
"virajmishra1-bench": {
"type": "http",
"url": "https://bench.virajmishratakehome.workers.dev/mcp"
}
}
} [mcp_servers.virajmishra1-bench] url = "https://bench.virajmishratakehome.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"virajmishra1-bench": {
"type": "remote",
"url": "https://bench.virajmishratakehome.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add virajmishra1-bench --url 'https://bench.virajmishratakehome.workers.dev/mcp' --transport streamable-http
mcp_servers:
virajmishra1-bench:
url: "https://bench.virajmishratakehome.workers.dev/mcp" {
"McpServers": {
"virajmishra1-bench": {
"Transport": "http",
"Url": "https://bench.virajmishratakehome.workers.dev/mcp"
}
}
} assistant mcp add virajmishra1-bench -t streamable-http -u 'https://bench.virajmishratakehome.workers.dev/mcp'
{
"mcpServers": {
"virajmishra1-bench": {
"type": "http",
"url": "https://bench.virajmishratakehome.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
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 22 Sept 2026 · Probed https://bench.virajmishratakehome.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=virajmishratakehome.workers.dev | CN=WE1,O=Google Trust Services,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 493ffd0bfc1b3afb13a3205a0402667c |
| SANs: virajmishratakehome.workers.dev, *.virajmishratakehome.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bench.virajmishratakehome.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://bench.virajmishratakehome.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://bench.virajmishratakehome.workers.dev/mcp | Inconclusive | 406 |
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 →
get_agent Get a public agent ~48
Get one public agent's recipe, public capability manifest, coarse invocation status, owner telemetry, and verified benchmark submissions.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Bench handle in @owner/agent-slug form. |
No output schema declared.
No examples provided.
list_benchmarks List verified benchmark contracts ~27
List public, versioned benchmark contracts and only their trusted-runner-verified submissions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_agents Search public AI agents ~243
Find listed public agents by task, capability, category, framework, model, verified evidence, or reuse configuration. Owner telemetry and controlled benchmark evidence are returned separately.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| framework | string | – | – |
| license | string | – | Exact SPDX-style license id from the agent's manifest provenance, such as MIT or Apache-2.0. |
| limit | integer | – | – |
| liveCallable | boolean | – | True returns agents with a reusable invocation policy and an owner-verified, currently reachable endpoint. |
| maxCostPerRunUsd | number | – | Upper bound on lifetime total_cost_usd / total_runs, i.e. average observed cost per run. |
| maxP50LatencyMs | integer | – | Upper bound on the agent's observed p50 latency in milliseconds. |
| model | string | – | – |
| query | string | – | Task or capability to search for, such as grounded research or code review. |
| reusable | boolean | – | True returns agents whose owners configured an invocation policy and capability manifest. |
| sort | string | – | – |
| verified | boolean | – | True returns agents with at least one trusted-runner-verified benchmark submission. |
No output schema declared.
No examples provided.
What is the Bench Agent Discovery MCP server?
Bench Agent Discovery is an MCP server listed in the public MCP registry as io.github.VirajMishra1/bench. Discover public AI agents, reusable recipes, and trusted benchmark evidence by task. This page covers its hosted endpoint (https://bench.virajmishratakehome.workers.dev/mcp).
Is the Bench Agent Discovery MCP server safe to use?
Bench Agent Discovery scores 80 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 Bench Agent Discovery MCP server expose?
Bench Agent Discovery exposes 3 tools: search_agents, get_agent, list_benchmarks. Their descriptions and schemas cost roughly 318 tokens of context every time the server is loaded.
Does the Bench Agent Discovery MCP server require authentication?
No. We connected to Bench Agent Discovery without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Bench Agent Discovery MCP server still maintained?
Bench Agent Discovery is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.