mcpbeat Sign in

Probe V0 MCP Server

by lexbritten Your server? Claim it
answering

Probe V0 is answering right now. Last checked 9 min ago. It exposes 2 tools. Last commit 1 Sep 2026.

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

Uptime history 70 days of history · worst day 91%
70 days agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
189 ms
Response time
average over 24h
0
Stars
last commit 1 Sep 2026

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 3 September 2026. No other catalogue keeps this.

3 Sep 2 tools changed the parameters they ask for probe.history, verify_http_claim

Nothing serious here today

Today is the operative word: we check Probe V0 every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add probe --transport http https://probe-evidence.probe-lab.workers.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://probe-evidence.probe-lab.workers.dev/mcp
~/.codex/config.toml
[mcp_servers.probe]
url = "https://probe-evidence.probe-lab.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "probe": {
      "url": "https://probe-evidence.probe-lab.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "probe": {
      "type": "http",
      "url": "https://probe-evidence.probe-lab.workers.dev/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

probe
probe.history
Retrieve up to 20 persisted observations for an existing Probe experiment ID without making a new HTTP request. Use after verify_http_claim to inspect repeated results, PASS/FAIL/ERROR counts, agreement, or whether the observed verdict changed between the two latest decisive observations. This is historical evidence lookup, not a current live verification; use verify_http_claim when freshness or present endpoint behavior matters.
verify
verify_http_claim
Use this to verify a current public HTTPS claim by direct observation rather than web search, documentation, browser inference, or shell/curl. Use for explicit assertions that a GET/HEAD currently returns an expected HTTP status, exact header value, JSON value at a JSON Pointer, or body substring. It evaluates assertions, persists bounded evidence, reuses sufficiently fresh matching evidence, and summarizes recent observations. follow_redirects defaults to false; when true, Probe manually follows at most 3 validated HTTPS redirects. Every fetch uses redirect: manual. V0 supports only public HTTPS URLs without credentials, query strings, fragments, IP literals, or non-443 ports. Redirect validation is hostname/policy based; the Worker cannot guarantee protection against DNS rebinding between validation and platform DNS resolution.

Endpoints

URLTransportStateLatencyChecked
https://probe-evidence.probe-lab.workers.dev/mcp streamable-http answering 193 ms 9 min ago

Alternatives to Probe V0

same job, measured the same way
Tomba MCP Server
by tomba-io

MCP server for Tomba email finder, verification, and contact enrichment API

55 installs/wk 38 tools answering
HODLXXI Read-Only
by hodlxxi

Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.

26 tools answering
Verify API
by drain54

AI claim verification MCP endpoint with x402 payments and stealth web fetch

1 tools answering
Execute bid-clarification-q-and-a-mcp
by evozim

Premium agentic endpoint for bid-clarification-q-and-a-mcp.

1 tools answering
Svix MCP
by mrfentmen

MCP server for Svix: applications, endpoints, MCP: real tools for real work.

93 installs/wk local only
X402 Scan MCP
by forgemeshlabs

x402 Endpoint Scanner — a free local health probe for x402 paid endpoints as an MCP server.

339 installs/wk local only
I
Italian Company Verification – Official Sources
by alexanderdandrea-art

Verify Italian companies for KYB, supplier onboarding and procurement using official/public sources.

1 tools answering
Simap MCP
by digilac

MCP server for simap.ch - Swiss public procurement platform

605 installs/wk local only

Probe V0 — questions

Answers built from our own checks of this server.

What can Probe V0 do?
It exposes 2 tools, read directly from the server on our last check. Among them: probe.history, verify_http_claim. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Probe V0 working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 189 ms. The bar chart above shows every period we have measured.
How do I connect Probe V0?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Probe V0 need an API key?
No. Probe V0 completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Probe V0?
It answers our handshake in 189 ms on average, which is faster than 70% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Probe V0 open source?
The code is open source: it is published under the MIT licence and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at probe-evidence.probe-lab.workers.dev, which runs on its operator's own terms.