# Probe V0 [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/lexbritten/probe-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/probe-v0

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

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "probe-v0": {
    "command": "npx",
    "args": ["-y","probe-v0"]
  }
}
```

## Documentation & README

# Probe (experimental V0)

Probe lets AI agents empirically verify current claims about public HTTPS endpoints by making a bounded direct observation. This differs from web search or documentation, which report what sources say, and from model inference, which is not a live observation.

Probe persists timestamped, freshness-aware evidence so a sufficiently recent matching observation can be reused and historical observations can be compared.

V0 is intentionally narrow: public HTTPS hostname URLs on port 443; GET or HEAD; HTTP status, exact header, exact JSON Pointer value, or literal body-substring assertions. Public V0 requires `freshness_seconds` exactly `300`.

Redirect following is opt-in with `follow_redirects=true`, limited to three 301/302/303/307/308 hops. Every destination must satisfy the same HTTPS, hostname, port, credential, query, fragment, and private/local safety restrictions. With the default `false`, Probe observes only the first response. Probe must not be used when the user's actual claim requires fetching an unsupported destination.

Probe does not provide a complete DNS-rebinding guarantee, uptime guarantee, SLA, authentication feature, or pricing commitment. It is experimental V0.