verify[402]
snapshot · block — Run free check

Release note · 7 min read · Nov 13, 2026

What verify402-mcp 1.1.0 ships.

Two free tools, a way to bind a challenge to the terms the seller actually published, durable counters — and a list of the things that did not change.

1.1.0 was published after explicit approval: npm verify402-mcp@1.1.0 (gitHead f5d5d9a), the MCP Registry active/latest, GitHub release mcp-v1.1.0, Render serving 1.1.0, and the listing on mcprush at 8 tools. Eight tools is the headline: the unchanged free preflight, two new free tools to inspect endpoints and watch the list, and the five paid checks — and the two additions are deliberately the ones that cost nothing to call.

Two free tools: read the 402, and watch the list

inspect_402 takes a challenge you already have — pasted bytes, a base64 header, or a URL to a public endpoint — decodes the accepted requirements, and runs the same structural payment preflight an agent runs before signing. It returns the parsed challenge next to the verdict, plus a receipt. It never signs and never settles. What it tells you is narrower than it sounds, and the notChecked list it prints is not boilerplate: it names what a structural PASS cannot see, such as recipient reputation and facilitator settlement.

directory_402 serves the watched list of public x402 endpoints — the same list behind /directory and /directory.json. Each entry keeps the protocol verdict and the sign verdict separate, because they are allowed to disagree: a challenge can be well-formed and still name a network this build cannot settle, and an entry blocked on an unsupported chain is not a malformed 402.

Bind the challenge to what the seller published

The gate can already compare a challenge to what you allow. 1.1.0 adds the other half: policy.sellerTermsManifest, bound to a seller-signed publication on an origin you pin. That is the terms the provider claims, stated by the provider — price, asset, network, timeout — not something reconstructed from inside the 402 asking to be paid.

The binding is strict on purpose. A drift in any of the four fields comes back a BLOCK with terms_mismatch and names the field that drifted. A resource the seller did not list is a CAUTION with terms_resource_unlisted. A bad or stale manifest degrades the same way the payout manifest does. A match records a signed termsBinding in the receipt, so the binding travels with the intent instead of living only in the checker's memory.

It will not tell you the price is fair or that the seller is honest. It tells you the 402 you were handed is the 402 the seller said they publish.

A token registry, instead of guesses

USDC has a different contract on every chain, and testnet USDC is different again. 1.1.0 replaces ad-hoc address checks with a registry (src/tokens.mjs): canonical asset per network, symbol, decimals, and an explicit assumed $1 parity marker when a stable is not the canonical USDC — because an assumed parity is worth something when it is printed out loud and worth nothing when it is silent.

Durable counters, and pings you have to opt into

/usage now reports durable counters when a state path is configured, and says plainly when it is process-local instead — restart resets it, and clients are self-declared labels that are spoofable, not identities. The bridge can also emit an opt-in anonymous ping per tool call (VERIFY402_TELEMETRY=1, payload { tool, ok } only). If you did not switch it on, nothing about your runs leaves your machine.

What 1.1.0 does not change

Where to watch it: the traction ledger, which keeps the zero months visible rather than dropping them when the looking-at-nothing is embarrassing.

Run it

npx -y verify402-mcp. Free mode registers three tools and never spends. Then try inspect_402 against any public 402 you can curl — that is the shortest honest demo of the product.

The ask

A falsifier is more useful than a fan.

Send three intents against the 1.1.0 gate — one you expect to pass, one you are unsure about, one you think should be blocked — and I will reply with raw verdicts and the reason codes.

Previous: Put a pre-signing gate in an MCP agent in 15 minutes. · All notes