Public data indexx402 MCP Registry › Weekly changes

x402 MCP Registry observed changes

Across the seven newest captured dates, 2026-09-01 through 2026-09-07, the sealed series supports 33 registry-publication or version-change events. A name crossing a historical capture's 100-result boundary is never called new; a missing name is never called removed.

Coverage limit. This is not a complete registry census. The Official Registry API returns 100 records per page. Newest collections can seal a cursor walk only after reaching a terminal page; historical captures predate that terminal-pagination proof. Absence is therefore not evidence that a server is unregistered. Names, versions, statuses, and dates reproduce Registry Data; they are not security reviews or endorsements.

ObservedRegistry nameChangePrior versionCurrent version
2026-09-07io.sslip.249.111.77.187/x402-mcp-toolsversion changed1.0.01.1.0
2026-09-07io.github.ZadenGG/x402-zadenworksregistry publication datenot applicable2.1.0
2026-09-07io.github.AgentTanuki/x402-payment-safetyversion changed2.6.42.7.0
2026-09-07io.github.AgentTanuki/x402-payment-safetyregistry publication datenot applicable2.7.0
2026-09-07dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schemaversion changed1.0.01.1.0
2026-09-07dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schemaregistry publication datenot applicable1.1.0
2026-09-06io.sslip.249.111.77.187/x402-mcp-toolsregistry publication datenot applicable1.1.0
2026-09-06io.github.runningoffcode/wormhole-x402version changed0.6.20.8.0
2026-09-06io.github.runningoffcode/wormhole-x402registry publication datenot applicable0.8.0
2026-09-06io.github.kadopi/x402-mcp-starterregistry publication datenot applicable0.2.0
2026-09-06io.github.arden-instance/x402lintregistry publication datenot applicable0.5.2
2026-09-06com.scriptmasterlabs/x402-gatewayversion changed1.1.01.3.0
2026-09-05world.agentindex/x402registry publication datenot applicable1.0.0
2026-09-05io.github.chico10117/x402-preflightversion changed1.0.01.0.1
2026-09-05com.scriptmasterlabs/x402-payregistry publication datenot applicable1.0.0
2026-09-05com.scriptmasterlabs/x402-gatewayregistry publication datenot applicable1.3.0
2026-09-04io.github.chico10117/x402-preflightregistry publication datenot applicable1.0.1
2026-09-04com.hergertsynthora/synthora-x402version changed1.1.11.1.2
2026-09-04app.vercel.ora-x402-gateway/sensations-mergulhoregistry publication datenot applicable0.3.0
2026-09-03io.github.kevin2003050666-coder/x402-micro-tollgateversion changed0.3.00.3.3
2026-09-03io.github.kevin2003050666-coder/x402-micro-tollgateregistry publication datenot applicable0.3.3
2026-09-03com.hergertsynthora/synthora-x402version changed1.1.01.1.1
2026-09-03com.hergertsynthora/synthora-x402registry publication datenot applicable1.1.2
2026-09-02io.github.kevin2003050666-coder/x402-micro-tollgateversion changed0.2.10.3.0
2026-09-02io.github.entreprisedaney33-rgb/x402-seller-mcpregistry publication datenot applicable0.1.1
2026-09-02com.scriptmasterlabs/x402-gatewayversion changed1.0.01.1.0
2026-09-01io.github.nanotools-x402/nanotoolsregistry publication datenot applicable1.0.1
2026-09-01io.github.forgemeshlabs/x402-scan-mcpregistry publication datenot applicable0.1.2
2026-09-01io.github.forgemeshlabs/x402-notary-mcpregistry publication datenot applicable0.1.8
2026-09-01io.github.forgemeshlabs/x402-ads-mcpregistry publication datenot applicable0.2.2
2026-09-01fr.humanmirror/x402registry publication datenot applicable1.2.0
2026-09-01dev.workers.clankerceo.multichain-rpc/x402-toolsregistry publication datenot applicable1.2.0
2026-09-01com.x402-list/x402-list-mcpregistry publication datenot applicable0.5.1

Why absence is not a change event

The source API returns 100 latest-version matches per page. Newer receipts can prove a terminal cursor walk, but historical receipts cannot. 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 hybrid continuity-record offer.