Diagrams · Fig. 10

The drift network loop

The crawler catches the drift before you do, so you are warned on call one.

The drift network loopmcpindex crawls the public MCP registry every day, re-derives every tool contract, and records each silent change as a fingerprint-only ledger entry anchored to Bitcoin via OpenTimestamps and published on the public ledger. When your gate pins a tool it can query that network and warn you on the very first call. The corroboration count floors at the crawler as a single first-party source; forgeable install reports are excluded from the public number. The advisory rides alongside the verdict and never moves a PROCEED or a HOLD.01daily crawl of the public MCP registryevery reachable remote server02re-derive every tool contractthe same derivation your gate runs03change detectedrecorded as a fingerprint-only entry04your gate queries the network on pinGET /api/v1/drift/any?fp=…OTS anchor → the public drift ledger/ledger · fingerprint-only, hash-chained, timestampedwarned on the FIRST calladvisory only · it never moves a PROCEED or a HOLDCORROBORATION FLOORS AT THE CRAWLER (SOURCES=1). FORGEABLE INSTALL REPORTS ARE EXCLUDED FROM THE PUBLIC COUNT.
Fig. 10 · The crawler catches the drift before you do, so you are warned on call one.
Read Fig. 10 as text
        daily crawl of the public MCP registry
                     |
                     v
        re-derive every tool contract
                     |
                     v
        change detected --> fingerprint-only ledger entry --> OTS anchor --> /ledger
                     |                                                        public
                     v
        fleet query  GET /api/v1/drift/any?fp=...
                     |
                     v
        your gate warns you on the FIRST call
        advisory only - it never moves a PROCEED or a HOLD

  corroboration floors at the crawler (sources=1). forgeable install reports are
  excluded from the public count. entries are fingerprint-only: no schema, no
  argument, no description, no URL, no server or tool name.
What the figure says

mcpindex crawls the public MCP registry every day, re-derives every tool contract, and records each silent change as a fingerprint-only ledger entry anchored to Bitcoin via OpenTimestamps and published on the public ledger. When your gate pins a tool it can query that network and warn you on the very first call. The corroboration count floors at the crawler as a single first-party source; forgeable install reports are excluded from the public number. The advisory rides alongside the verdict and never moves a PROCEED or a HOLD.

Where this is explained
/ledger/methodology
Use this diagram

Licensed CC BY 4.0. Use it anywhere, including commercially. Keep the credit.

Credit line (HTML)

Paste under the figure. That is the whole licence obligation.

<a href="https://mcpindex.ai/diagrams/drift-network-loop">The drift network loop - mcpindex.ai</a> (CC BY 4.0)
Direct SVG

Standalone image/svg+xml. Vector, editable, no stylesheet needed.

https://mcpindex.ai/diagrams/drift-network-loop/svg

Last reviewed 2026-07-27

Questions this answers

mcp drift ledger &middot; mcp registry crawl &middot; mcp contract change history &middot; mcpindex drift network