verify[402]
snapshot · block — Run free check

Release note · 6 min read · Nov 16, 2026

What verify402-mcp 1.1.1 ships.

The release where the recovery path became real: five defects in the settlement-recovery flow, all fatal to the feature's promise, fixed — and a marker republish so the installed version agrees with the deployed service.

1.1.1 was published after explicit approval: npm verify402-mcp@1.1.1 (gitHead 7c43cbf5406d73d9ae396ed1363170414a2cc74e), the MCP Registry active/latest, GitHub release mcp-v1.1.1, and Render serving 1.1.1. The bridge has no runtime change; 1.1.1 exists as a marker so the version you install is the version the service reports. All the change is in the service — the six things that were broken between “we say settlement recovery exists” and the code actually doing it.

The one that hurt: durable recovery was unreachable for every real caller

The service read the legacy x-payment header for the payment's identity — but the x402 v2 SDK sends PAYMENT-SIGNATURE, and our own bridge sends that too. Every genuine v2 caller therefore staged a recovery record with no payment reference and could never reconcile a lost response. The durable-recovery feature worked only for clients that don't exist. The bridge is untouched here; the fix is in the service, and a v2 settlement reference test now guards it.

The Solana rail had the same problem in the other direction — there is no EIP-3009 nonce to match — so a Solana-exact settlement could never be reconciled at all. It is now identified by its signed transaction.

The second: the evidence hash a receiver cannot reproduce

Every paid response advertises a responseHash. Before 1.1.1, the service hashed the body before the honesty arrays (checked / notChecked) were merged in — so the advertised hash disagreed with the documented recompute recipe for every handler that did not already return them. A verification artifact you cannot verify is worse than none. The fix is one projection (projectionCore) feeding both sides: the evidence bundle a receiver recomputes, and the record used for replay promotion. A new test asserts the advertised recipe names every key the projection excludes, so the prose cannot drift from the implementation again.

The third: spec 0.9 existed on paper, not in the wire

The extension said 409 operation_in_flight while a settlement can still resolve and 503 payment_unresolved once it is stuck. The service answered 503 recovery_unavailable instead. 1.1.1 implements it:

The smaller ones

Independent verification, and what it found

The spec review thread on x402-foundation/x402#3848 is where the substance of this work lives. Two independent implementers came at it from code rather than prose: Hitek-cel (Detent) ran crash-fault injection across its seven journal writes and published a 29-vector control-12 set derived from the suite; cv-scvd re-verified a Durable-Object claim/begin window in their own purchase flow, found the non-covered gap, and published the corrected trace publicly. The extension is not done when it is written down; it is done when two codebases survive the same crash.

The service ships with those implementation gaps closed. The vectors have not yet been run against this build; a conformance harness is queued, and results will be reported in the thread, not asserted here.

What 1.1.1 does not change

Upgrade

npx -y verify402-mcp@1.1.1. If you pinned @1.1.0, nothing about your tools changes; the service behind them is what got fixed.

The ask

Bring the crash, not the complaint.

If you build x402 flows, the thing we need is not opinions about the extension — it is a failing reproduction. The control-12 vector format and the crash harness the adjacent implementations have both landed in the public thread; the shortest path to making this spec real is running both against your own rail and posting what breaks.

Previous: What verify402-mcp 1.1.0 ships. · All notes