x402 MCP Registry continuity methodology
The reader accepted 1,687 sealed Official MCP Registry observations across 17 dated captures. An unsuccessful newest source receipt makes every page unavailable; it never becomes a plausible empty catalogue.
This methodology keeps source scope, comparison rules, and privacy exclusions mechanical so a later page cannot silently widen them.
Feed-level privacy and legality boundary
The SQL reader selects only exact registry identity, snapshot date, a bounded detail projection, content hash, and collection time. It never selects raw JSON, wallet or client addresses, endpoint headers, descriptions, repository handles, price observations, on-chain reputation events, or mcp.so records. That exclusion happens before template code can access a value.
Comparison rule
Versions are compared only when the same exact registry name appears on two captured dates. We do not join by a similar name, repository, endpoint, or operator. A publication event uses the Registry's own published date. We publish volume and version history, never a score or a claim that one server is safer than another. The methodology treats every missing comparison as unavailable.
Capture boundary
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. The captured window is 2026-07-22 through 2026-08-07. The Registry remains authoritative.
Source receipt
The newest successful response was 93,110 bytes, collected 2026-08-07T12:50:16+00:00. Source hash: 37762451b2aa9ac7a9743a563f4d986718c9cbfd50ee5ce1c1c70bd25b585f3b. Collection batch seal: c2e922199569173ce7fdea49c46ac123950a821c9f429ae842b9280a13b0b9f3.
Official MCP Registry API query · Registry terms and CC0 dedication · Return to the continuity-report offer.