How the atlas is built

An entry is one exact target that InterfaceDeltaBot observed after finding it in the Official MCP Registry. A listing must be current: its latest Registry record is active or deprecated, not deleted. Only observations made by public discovery are shown. Services that InterfaceDelta customers monitor are shown only through observations public discovery made itself.

The origin, a SHA-256 hash of the full endpoint locator, Registry names and listing dates, and for each observation its time, versions, fingerprint, protocol and MCP endpoint status, capability counts and consistency check results. Endpoint paths, descriptions and other publisher text are not published.

We compare only explicit publisher hints with calibrated AI effect readings, including disputed readings. Shadow and below-threshold answers are excluded. These are readings of tool declarations, not results of calling tools.

• Read-only: a read-only declaration is compared with a reading of creating, changing or deleting records, messaging, moving money or running code.
• Destructive: a destructive declaration is compared with a reading of computing or reading without writing.
• Non-destructive: a non-destructive declaration is compared with a reading of deleting or cancelling records.
• Closed-world: a closed-world declaration is compared with a reading of calling other services or sending messages.

Destructive hints are not compared when read-only is explicitly true. Missing hints do not count. We do not compare idempotentHint: the effect reading says nothing about repeatability. Agreeing means none of these four comparisons disagrees, not that every hint has been verified.

A disagreement is not a finding about the service: either side can be wrong. How we compare declarations and readings.

The Registry pass is partial and proceeds alphabetically, so early coverage favours names early in the alphabet. InterfaceDeltaBot makes at most one scan a day per host and a limited number per source, and honours robots.txt exclusions. Services that customers monitor are usually not listed, because discovery reuses a recent customer observation instead of scanning again. A few hosts serve many listed paths and are over-represented.

Each observation is compared with the previous atlas observation of the same entry using the published compatibility rules. Comparisons recorded for customers are never used.

A service operator can ask for an entry to be removed by emailing support@interfacedelta.com from a verifiable address; see InterfaceDeltaBot. Removal stops further observation and takes the entry off these pages. Observations are evidence and are not edited or deleted.

The atlas is a snapshot regenerated at most every six hours. The current snapshot was generated 3 Nov 2026, 21:26 UTC. Official MCP Registry metadata is published under CC0 1.0.