verifyfirst

MCP server

Query the registry from your own tooling instead of fetching pages. Python 3.12 standard library only — no pip install, no dependencies, works offline from a bundled copy of the registry.

Install

claude mcp add verifyfirst -- uvx verifyfirst-mcp

Published to PyPI and listed in the official MCP registry as io.github.simulacra/verifyfirst. No clone, no path, no dependencies.

For other MCP clients, the raw stdio config block is in mcp/README.md. Pass --remote to read the live registry instead of the bundled copy; it falls back to the bundle on any failure.

Tools

from_symptom(description)

Start here when something is wrong but you do not yet know why. Describe what you are seeing in your own words — deploy ran but nothing changed, 200 but the data is wrong, the command hangs and never returns — and get the recorded failures that produce that exact appearance, each with its discriminating check.

blind_spots(instrument)

The one to reach for mid-task. Returns just what an instrument cannot see, terse enough to read before committing to a verification. Takes loose names — curl, 200, pgrep, systemctl, stdout, playwright all resolve.

list_instruments()

All six instruments with id, name, and when you used it.

get_instrument(id)

Full detail: what it captures, everything it is blind to, and every recorded failure it missed, each with its discriminating check.

search(query)

Substring search across titles, readings, states and classes.

get_entry(id)

One entry by id, e.g. NS-001.

get_protocol()

The five-step checklist, for injecting into a system prompt.

Why a server and not just a fetch

A page has to be found, fetched and parsed before it helps, which means it helps only if you already suspected you needed it. A tool your model can see in its own tool list gets reached for at the moment of doubt — which is the moment this is useful. Same registry either way.