Probe V0
REMOTE · PROBE-EVIDENCE.PROBE-LAB.WORKERS.DEV · SCANNED SEP 20
Experimental MCP server for current empirical verification of explicit public HTTPS endpoint claims.
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 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 Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 529 tokens (~264/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Probe V0 MCP server?
Probe V0 is a hosted endpoint at https://probe-evidence.probe-lab.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 · probe-evidence.probe-lab.workers.dev
claude mcp add --transport http lexbritten-probe 'https://probe-evidence.probe-lab.workers.dev/mcp'
{
"mcpServers": {
"lexbritten-probe": {
"url": "https://probe-evidence.probe-lab.workers.dev/mcp"
}
}
} {
"servers": {
"lexbritten-probe": {
"type": "http",
"url": "https://probe-evidence.probe-lab.workers.dev/mcp"
}
}
} [mcp_servers.lexbritten-probe] url = "https://probe-evidence.probe-lab.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lexbritten-probe": {
"type": "remote",
"url": "https://probe-evidence.probe-lab.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add lexbritten-probe --url 'https://probe-evidence.probe-lab.workers.dev/mcp' --transport streamable-http
mcp_servers:
lexbritten-probe:
url: "https://probe-evidence.probe-lab.workers.dev/mcp" {
"McpServers": {
"lexbritten-probe": {
"Transport": "http",
"Url": "https://probe-evidence.probe-lab.workers.dev/mcp"
}
}
} assistant mcp add lexbritten-probe -t streamable-http -u 'https://probe-evidence.probe-lab.workers.dev/mcp'
{
"mcpServers": {
"lexbritten-probe": {
"type": "http",
"url": "https://probe-evidence.probe-lab.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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://probe-evidence.probe-lab.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=probe-lab.workers.dev | CN=WE1,O=Google Trust Services,C=US | 31 Aug 2026 | 29 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 9d59722454037318136d328cbf99ee5f |
| SANs: probe-lab.workers.dev, *.probe-lab.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 probe-evidence.probe-lab.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://probe-evidence.probe-lab.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://probe-evidence.probe-lab.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 →
probe.history Inspect Historical HTTP Evidence ~128
Retrieve up to 20 persisted observations for an existing Probe experiment ID without making a new HTTP request. Use after verify_http_claim to inspect repeated results, PASS/FAIL/ERROR counts, agreement, or whether the observed verdict changed between the two latest decisive observations. This is historical evidence lookup, not a current live verification; use verify_http_claim when freshness or present endpoint behavior matters.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of newest stored observations to return, from 1 through 20. |
| probe_id | string | yes | The 64-character lowercase hexadecimal Probe experiment ID returned by verify_http_claim. |
| Name | Type | Req | Description |
|---|---|---|---|
| observations | array | yes | – |
| probe_id | string | yes | – |
| protocol | string | yes | – |
| summary | object | yes | – |
No examples provided.
verify_http_claim Verify Live HTTP Claim ~289
Use this to verify a current public HTTPS claim by direct observation rather than web search, documentation, browser inference, or shell/curl. Use for explicit assertions that a GET/HEAD currently returns an expected HTTP status, exact header value, JSON value at a JSON Pointer, or body substring. It evaluates assertions, persists bounded evidence, reuses sufficiently fresh matching evidence, and summarizes recent observations. follow_redirects defaults to false; when true, Probe manually follows at most 3 validated HTTPS redirects. Every fetch uses redirect: manual. V0 supports only public HTTPS URLs without credentials, query strings, fragments, IP literals, or non-443 ports. Redirect validation is hostname/policy based; the Worker cannot guarantee protection against DNS rebinding between validation and platform DNS resolution.
| Name | Type | Req | Description |
|---|---|---|---|
| assertions | array | yes | One to eight explicit assertions evaluated against the same HTTP response. |
| follow_redirects | boolean | – | Whether to follow up to three validated HTTPS redirects. Defaults to false. |
| freshness_seconds | integer | – | Maximum acceptable age of reusable matching evidence, in seconds. Public Probe V0 requires exactly 300. |
| method | string | – | HTTP method to observe. Use HEAD only when response headers and status are sufficient. |
| url | string | yes | Public HTTPS URL to observe. V0 forbids credentials, query strings, fragments, IP literals, private or local destinations, and non-443 ports. |
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_age_seconds | number | yes | – |
| evidence_source | string | yes | – |
| protocol | string | yes | – |
| result | object | yes | – |
| summary | object | yes | – |
No examples provided.
What is the Probe V0 MCP server?
Probe V0 is an MCP server listed in the public MCP registry as io.github.lexbritten/probe. Experimental MCP server for current empirical verification of explicit public HTTPS endpoint claims. This page covers its hosted endpoint (https://probe-evidence.probe-lab.workers.dev/mcp).
Is the Probe V0 MCP server safe to use?
Probe V0 scores 75 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 Probe V0 MCP server expose?
Probe V0 exposes 2 tools: verify_http_claim, probe.history. Their descriptions and schemas cost roughly 417 tokens of context every time the server is loaded.
Does the Probe V0 MCP server require authentication?
No. We connected to Probe V0 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Probe V0 MCP server still maintained?
Probe V0 is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.