Skip to content

Probe V0

by lexbritten · remote · no sign-in to list tools · v0.1.0 · published by GitHub user lexbritten

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

Changes · 1
CompareRegistry entry

2 tools: 1 change things and 1 only read.

Scanned Oct 21, 2026

2 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Findings

Matches of fixed checks, with the text they matched.

2 info
  • Infoverify_http_claim

    The description mentions "credentials".

    Matched text

    description: "...supports only public HTTPS URLs without credentials, query strings, fragments, IP literals,..."

    What this check looks for
  • Infoverify_http_claim

    The input schema at properties.url.description mentions "credentials".

    Matched text

    inputSchema.properties.url.description: "Public HTTPS URL to observe. V0 forbids credentials, query strings, fragments, IP literals,..."

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

2 tools

Changes things 1Claude Code: ask
  • verify_http_claimUse this to verify a current public HTTPS claim by direct observation rather than web search, documentation, browser inference, or shell/curl.2 findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...supports only public HTTPS URLs without credentials, query strings, fragments, IP literals,..."

      What this check looks for
    • Info

      The input schema at properties.url.description mentions "credentials".

      Matched text

      inputSchema.properties.url.description: "Public HTTPS URL to observe. V0 forbids credentials, query strings, fragments, IP literals,..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 1Claude Code: allow
  • probe.historyRetrieve up to 20 persisted observations for an existing Probe experiment ID without making a new HTTP request.No findings

    Why it is in this group

    • The description's first verb is "retrieve": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__probe__probe_history"
    ],
    "ask": [
      "mcp__probe__verify_http_claim"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as probe. Review it before you use it.