Probe V0
Experimental MCP server for current empirical verification of explicit public HTTPS endpoint claims.
Open source Repository Open in the app JSON README (API)
About
Experimental MCP server for current empirical verification of explicit public HTTPS endpoint claims.
Details
- Kind
- MCP servers
- Topic
- No topic detected
- Publisher
- lexbritten
- Origin
- official
- Category
- ferramentas
- Transport
- http
- Version
- 0.1.0
- Last push
- 2026-09-01T10:08:21Z
- Repository state
- ativo
- License
- MIT
- Added
- 2026-09-01 11:00:06
- Updated
- 2026-09-01 11:00:06
- Origin id
io.github.lexbritten/probe
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.