Probe V0

io.github.lexbritten由 GitHub 账号 lexbritten 发布v0.1.0更新于 Oct 27, 2026

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

已验证Streamable HTTP可网页运行开发者工具安全与监控

概览

AI 生成的概览

实验性远程 MCP 服务器,让助手直接观测公开 HTTPS 端点,以核实关于状态码、响应头、JSON 值或响应正文的断言。

可以做什么
  • 对公开 HTTPS 网址发起一次受限的 GET 或 HEAD 请求,核实预期的状态码、精确响应头值、JSON Pointer 值或正文子串
  • 仅在显式开启时跟随最多三次重定向,默认只观测第一个响应
  • 按已有实验 ID 取回最多 20 条已保存的观测记录,且不发起新请求
  • 比较重复结果、PASS/FAIL/ERROR 计数、一致性,以及最近两次决定性观测之间结论是否改变
适用场景
适合需要确认关于公开 HTTPS 端点的当前明确断言,而不依赖网页搜索、文档或模型推断的场景;也适合需要重复观测或历史对比同一检查的情况。
运行要求
远程 streamable HTTP 端点;未声明任何软件包、账号、API 密钥或请求头。目标须为 443 端口的公开 HTTPS 主机名,公开 V0 要求 freshness_seconds 恰为 300。
安装前请注意
它会代你向公开网址发起外部请求,并保存带时间戳的观测记录,之后可按实验 ID 取回。重定向跟随需显式开启且受限,但服务器声明不提供完整的 DNS 重绑定防护、可用性或 SLA 承诺、身份验证功能与定价承诺,且为实验性 V0。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Probe V0,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.lexbritten%2Fprobe/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "probe-v0": {
      "type": "http",
      "url": "https://probe-evidence.probe-lab.workers.dev/mcp"
    }
  }
}

README

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.

来源:README.md,提交 4958606

工具

2

verify_http_claim

Verify Live 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.

输入参数url必填methodassertions必填follow_redirectsfreshness_seconds

probe.history

Inspect Historical HTTP Evidence

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.

输入参数limitprobe_id必填

版本历史

1
  1. v0.1.0最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分