Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
lexbritten/probe-mcp
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4.4/5.0

Scored across 2 tools

Disambiguation5/5

verify_http_claim performs live current verification while probe.history retrieves persisted past observations. The descriptions explicitly separate the two use cases, so an agent should not confuse them.

Naming Consistency3/5

verify_http_claim follows a verb_object pattern, while probe.history uses a namespace.noun pattern. Both names are readable and lowercase, but the two naming styles are mixed rather than following one predictable convention.

Tool Count3/5

With only two tools the surface feels thin, but the narrow purpose of live HTTP verification plus historical evidence lookup is served without unnecessary additions. The minimal count is appropriate but borderline on the calibration scale.

Completeness4/5

The core workflow is covered: verify a claim with current evidence and later inspect the persisted history. Minor gaps such as listing or clearing experiments are absent but not required for the stated verification loop.

Available Tools

2 tools
probe.historyInspect Historical HTTP EvidenceA
Read-onlyIdempotent
Inspect

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.

Inputs: probe_id (required), limit. Returns: summary, probe_id, protocol, observations

verify_http_claimVerify Live HTTP ClaimA
Read-onlyIdempotent
Inspect

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.

Inputs: url (required), assertions (required), method, follow_redirects, +1 more. Returns: result, summary, protocol, evidence_source, +1 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.