Odel
Probe V0

Probe V0

@lexbrittenMITUpdated 6 days ago

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

View on GitHubSign in to connect
Server endpointStreamable HTTPNo authProbed
https://probe-evidence.probe-lab.workers.dev/mcp

This is the third-party server itself — Odel doesn't run it. Hitting this URL directly talks straight to the upstream server with no auth or proxying. Connect through Odel to front it with managed auth.

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.