verifyfirst

io.github.simulacra由 GitHub 账号 simulacra 发布v1.8.0更新于 Oct 24, 2026

Look up what your verification method cannot see: 48 failures that report success.

已验证STDIO仅桌面知识与记忆开发者工具

概览

AI 生成的概览

让助手查询验证盲区，以及那些报告成功却实际失败的案例，并按漏掉它们的验证手段归类。

可以做什么
提供一个包含 48 个“看似成功”的失败案例的注册表，按漏掉它们的验证手段分组。工具包括：from_symptom 根据观察到的症状查找对应失败；blind_spots 列出某个验证手段看不到的内容；list_instruments 与 get_instrument 查看手段详情；search 与 get_entry 检索注册表；get_protocol 给出在声称工作完成前的五步检查清单。
适用场景
当出现问题但原因不明时，或在任务进行中需要判断某种验证方式（如截图、退出码、HTTP 状态码）能否真正发现你关心的失败时，适合使用。
运行要求
以 Python 包（verifyfirst-mcp）形式通过 stdio 在本地运行，通常用 uvx 或 pip 安装。未声明需要账号、API 密钥或环境变量。可离线使用内置注册表；--remote 选项会读取在线注册表，失败时回退到内置副本。
安装前请注意
属于只读查询：返回参考资料，不会修改你的项目。启用 --remote 时会从 verifyfirst.dev 获取数据，查询内容会离开本机。注册表条目被描述为“已观察”或“有据可查”，并非假设案例。

安装

在 SourceWeft 中

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

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

verifyfirst-mcp

An MCP server for what your verification method cannot see.

A failure that crashes is cheap. A failure that reports success is expensive: the screenshot looks fine, the command exits zero, the endpoint returns 200, and the bug ships.

This server exposes verifyfirst.dev — a registry of 48 such failures, organised by the instrument that missed them rather than by the technology involved, because the instrument is what you know before you know the bug.

Install

bash
uvx verifyfirst-mcp          # run it directlypip install verifyfirst-mcp  # or install it

Register with Claude Code:

bash
claude mcp add verifyfirst -- uvx verifyfirst-mcp

Or any MCP client:

json
{  "mcpServers": {    "verifyfirst": { "command": "uvx", "args": ["verifyfirst-mcp"] }  }}

Tools

ToolWhat it does
from_symptom(description)Start here when something is wrong but you do not know why. Describe what you see — "deploy ran but nothing changed", "200 but the data is wrong" — and get the failures that produce that appearance, each with its check.
blind_spots(instrument)The one to reach for mid-task. What an instrument cannot see, terse. Takes loose names — curl, 200, pgrep, systemctl, stdout, playwright all resolve.
list_instruments()All six instruments.
get_instrument(id)Full detail plus every recorded failure it missed, each with its check.
search(query)Substring search across the registry.
get_entry(id)One entry, e.g. NS-001.
get_protocol()A five-step checklist for claiming work is done.

Example

> blind_spots("screenshot")
screenshot (A rendered image) is blind to:  - Time. A still frame cannot distinguish 'renders one frame then stops'    from 'renders one frame correctly'.  - Whether scripts ran at all, as opposed to running and producing this.  ...

Notes

Zero dependencies — Python standard library only. Works offline from a bundled copy of the registry; pass --remote to read the live one, which falls back to the bundle on any failure.

Every entry in the registry is a failure that genuinely occurs, marked observed (diagnosed first-hand) or documented (primary source cited and the check reproduced). None are hypothetical.

CC0-1.0 — public domain. Maintained by Zion Labs.

来源：pypi/README.md，提交 93dd19c

工具

0
SourceWeft 尚未在沙箱中启动过该软件包，因此其工具未知。

版本历史

1
  1. v1.8.0最新Sep 16, 2026

评分

已满足适用检查项的 40%

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

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。