MCP.Market

Probe V0 MCP server

online · 100% uptime
by lexbritten·io.github.lexbritten/probe·v0.1.0
No reviews yet

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

B84/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B84/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Probe V0 yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Probe V0 tools (2)

write = sends, deletes, buys or posts
  • probe.historyFree

    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_http_claimFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 459ms20/20
  • Tool poisoning2 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 58 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 84/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Probe V0 compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
84/100
higher than 68% of 48,243 servers
Tools
2
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
165 ms
faster than 72% of 30,027 servers

What its tools let an agent do: 2 read

Install Probe V0 in Claude Code, Cursor or VS Code

claude mcp add --transport http probe https://probe-evidence.probe-lab.workers.dev/mcp
Add to Cursor

What the publisher says

From the Probe V0 repository's README, as published. We do not edit it. Read it on GitHub

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.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-10-29downgradeA → Bscore 84

Probe V0: common questions

Is Probe V0 MCP server safe?
Mostly: it is graded B (84/100). Read the Probe V0 safety report
How do I install Probe V0?
It runs remotely at probe-evidence.probe-lab.workers.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Probe V0 need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Probe V0 maintained?
The last commit was 65 days ago (2026-09-01). The latest release is v0.1.0.
Is Probe V0 up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Probe V0 compare with other MCP servers?
safety score 84/100 (higher than 68% of 48,243 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.