# Probe V0 (remote · probe-evidence.probe-lab.workers.dev)

Experimental MCP server for current empirical verification of explicit public HTTPS endpoint claims.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `probe-evidence.probe-lab.workers.dev`: 75/100 (this document), [markdown](https://verifymcp.io/servers/lexbritten-probe/probe-evidence.md), [page](https://verifymcp.io/servers/lexbritten-probe/probe-evidence)

## Channel facts

- Endpoint: `https://probe-evidence.probe-lab.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.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-09-20.

- **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**: 71/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

### Claude

```bash
claude mcp add --transport http lexbritten-probe 'https://probe-evidence.probe-lab.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "lexbritten-probe": {
      "url": "https://probe-evidence.probe-lab.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lexbritten-probe": {
      "type": "http",
      "url": "https://probe-evidence.probe-lab.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.lexbritten-probe]
url = "https://probe-evidence.probe-lab.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lexbritten-probe": {
      "type": "remote",
      "url": "https://probe-evidence.probe-lab.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lexbritten-probe --url 'https://probe-evidence.probe-lab.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lexbritten-probe:
    url: "https://probe-evidence.probe-lab.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "lexbritten-probe": {
      "Transport": "http",
      "Url": "https://probe-evidence.probe-lab.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add lexbritten-probe -t streamable-http -u 'https://probe-evidence.probe-lab.workers.dev/mcp'
```

### Other

```json
{
  "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.

## 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-09-20 (score 75, +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.

### 2026-09-18 (score 74, +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.

### 2026-09-15 (score 73, +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.

### 2026-09-13 (score 72, +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.

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

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

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

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

## MCP tools (2)

### `verify_http_claim` (~289 tokens)

Verify Live HTTP Claim

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.

Input parameters:

- `assertions` (array, required): 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, required): Public HTTPS URL to observe. V0 forbids credentials, query strings, fragments, IP literals, private or local destinations, and non-443 ports.

Output parameters:

- `evidence_age_seconds` (number)
- `evidence_source` (string)
- `protocol` (string)
- `result` (object)
- `summary` (object)

### `probe.history` (~128 tokens)

Inspect Historical HTTP Evidence

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.

Input parameters:

- `limit` (integer): Maximum number of newest stored observations to return, from 1 through 20.
- `probe_id` (string, required): The 64-character lowercase hexadecimal Probe experiment ID returned by verify_http_claim.

Output parameters:

- `observations` (array)
- `probe_id` (string)
- `protocol` (string)
- `summary` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lexbritten-probe/probe-evidence#diagnostics

## Score history

- 2026-09-20: 75
- 2026-09-19: 74
- 2026-09-18: 74
- 2026-09-17: 73
- 2026-09-16: 73
- 2026-09-15: 73
- 2026-09-14: 72
- 2026-09-13: 72
- 2026-09-12: 71
- 2026-09-11: 71
- 2026-09-10: 70
- 2026-09-09: 70
- 2026-09-08: 69
- 2026-09-07: 69
- 2026-09-06: 68
- 2026-09-05: 68
- 2026-09-04: 67
- 2026-09-03: 64
- 2026-09-02: 63
- 2026-09-01: 63

## Common questions

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

## Links

- Remote endpoint: https://probe-evidence.probe-lab.workers.dev/mcp
- Repository: https://github.com/lexbritten/probe-mcp
- Changelog RSS feed: https://verifymcp.io/servers/lexbritten-probe/probe-evidence.xml
- Changelog JSON feed: https://verifymcp.io/servers/lexbritten-probe/probe-evidence.json
- HTML version of this page: https://verifymcp.io/servers/lexbritten-probe/probe-evidence