MCP server: One MCP server.

Probe V0

@lexbrittenMCP server · External

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

Fact-checkingv0.1.0MIT
Freeno charge per call

One address for any MCP client. No sign-in needed on this server.

What it does

1 read1 other

Grouped by tool name. At most: only reads or looks up information.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Tools

2 · grouped by tool name · checked 7 Oct 2026

Read · 1Look things up

  • verify_http_claim

Other · 1Neither hinted nor named

  • probe.history
Try it in the Inspector
README1 min read

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.

Similar modules

Browse Fact-checking