x402 MCP Registry observed changes
Across the seven newest captured dates, 2026-08-01 through 2026-08-07, the sealed series supports 13 registry-publication or version-change events. A name crossing the 100-result boundary is never called new.
Coverage limit. This is not a complete registry census. The source request is capped at 100 latest-version search results, so absence is not evidence that a server is unregistered. Names, versions, statuses, and dates reproduce Registry Data; they are not security reviews or endorsements.
| Observed | Registry name | Change | Prior version | Current version |
|---|---|---|---|---|
| 2026-08-06 | io.github.ZadenGG/x402-snap | registry publication date | not applicable | 1.0.0 |
| 2026-08-06 | io.github.Nikolife2016/pulsefeed-x402 | version changed | 1.0.6 | 1.0.7 |
| 2026-08-06 | io.github.Nikolife2016/pulsefeed-x402 | registry publication date | not applicable | 1.0.7 |
| 2026-08-05 | io.github.hypeprinter007-stack/anchor-x402 | version changed | 0.3.0 | 0.3.1 |
| 2026-08-04 | io.github.hypeprinter007-stack/anchor-x402 | registry publication date | not applicable | 0.3.1 |
| 2026-08-04 | io.github.Senpi-Station/x402-web-extract | registry publication date | not applicable | 1.0.1 |
| 2026-08-03 | io.github.michaelhutchings626-hub/alien-plugg-x402 | registry publication date | not applicable | 2.1.0 |
| 2026-08-03 | io.github.Mahesvannan/tx402 | registry publication date | not applicable | 0.2.0 |
| 2026-08-02 | io.github.liminalpepe/x402-repohealth-mcp | registry publication date | not applicable | 0.1.0 |
| 2026-08-02 | io.github.liminalpepe/x402-dataviz-mcp | registry publication date | not applicable | 0.1.0 |
| 2026-08-02 | io.github.liminalpepe/x402-codesearch-mcp | registry publication date | not applicable | 0.1.0 |
| 2026-08-02 | io.github.hypeprinter007-stack/anchor-x402 | version changed | 0.2.0 | 0.3.0 |
| 2026-08-02 | com.acjlabs/x402-listing-monitor | registry publication date | not applicable | 0.1.0 |
Why absence is not a change event
The source search returns at most 100 latest-version matches. A server can move outside that response without being removed from the Registry. We therefore publish only a registry-authored publication date inside the window or a version transition seen for the same exact registry name on two captured dates.
What these observed changes can support
The observed changes ledger answers a narrow procurement question: did the Official MCP Registry metadata for an exact named x402 server show a different version during our captured window? It does not test the server, inspect its tools, verify a payment, or infer that an update improved security. Reviewers can cite the dated source receipt and compare a version transition without turning registry presence into a trust judgment.
A continuity report retains the same evidence discipline over a longer customer-specified window. Each observed change travels with the two capture dates, the exact registry identity, and the collection seal. If a name appears on only one side of a capture, the report labels the comparison unavailable instead of manufacturing a publication or removal event.
Official MCP Registry API query · Method and privacy boundary · Monthly continuity-report offer.