Probe (experimental V0)
MCP serverDev toolsProbe lets an AI check whether claims about public HTTPS endpoints actually hold true right now by testing the endpoints themselves. Ask it to confirm a stated behavior and it reports what it finds. It is an experimental tool shared by the community.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding it, give your AI the exact HTTPS address and a clearly stated claim about it, then ask it to verify the claim now. Because the tool is experimental, treat its findings as a useful cross-check rather than a guarantee.
Then ask your AI: use Probe (experimental V0) to verify http claim
What your AI can do with it
- Check whether a public HTTPS endpoint currently behaves as claimed
- Verify an explicit endpoint claim by testing the endpoint directly
- Confirm that a stated behavior still holds at the time you ask
- Keep checks to endpoints that are public and use HTTPS
From the project's README
As published by lexbritten/probe-mcp in README.md.
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.
Tools it offers (2)
What this server listed when ahel dialed its public endpoint in Sep 2026, with no key and no account of yours. The names are the server’s own.
verify_http_claimprobe.history
Signals
- Last commit
- Sep 2026
Advanced
- Delivery
- probe MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
- Catalog kind
- mcp-server
- Gateway key
io-github-lexbritten-probe- Source
- github.com/lexbritten/probe-mcp
- Hosted endpoint
https://probe-evidence.probe-lab.workers.dev/mcp