InterfaceDeltaBot

Identity and purpose

InterfaceDeltaBot identifies itself as InterfaceDeltaBot/1.0 (+https://interfacedelta.com/bot). It records bounded factual observations of public, machine-readable software interfaces so changes can be compared over time.

Passive boundaries

The bot uses bounded HTTPS GET requests plus bounded, read-only MCP initialization and listing POST exchanges. It does not authenticate, submit forms, invoke tools, follow declared destinations onto another hostname, execute discovered software, or use model inference to decide protocol correctness.

Operating limits

Proactive observation runs only while InterfaceDelta has explicitly activated it, under the controlled-v1 admission profile. That profile permits one scan at a time, at most one scan start per hostname per rolling day, and four scan starts per rolling hour and 24 per rolling day across all hosts, of which at most 12 may come from one discovery source. A target that already has a complete observation from the last seven days is not scanned again.

A scan may make at most 12 requests, including robots.txt and redirects. Requests to a host are spaced by at least one second, with at most 12 per host per rolling hour, and observation makes at most 48 requests per rolling hour and 288 per rolling day across all observed hosts, in addition to the Registry reads below. Responses, time, and retries are also bounded.

Discovery source

The bot finds services to observe in the Official MCP Registry at registry.modelcontextprotocol.io. It reads the Registry with at most four requests per run and 12 per rolling day, spaced by at least two seconds.

Robots and redirects

Proactive observation retrieves and caches robots.txt through the same HTTPS, DNS, address, redirect, request-budget, and pacing controls. Missing robots.txt permits access. Explicit disallow rules are honored. Malformed responses, timeouts, and temporary server failures fail closed. Redirects and secondary protocol requests must retain the exact canonical hostname; DNS CNAME resolution does not itself change the requested application hostname.

Request suppression

An operator may ask us to stop future proactive observation of a hostname by emailing support@interfacedelta.com. Please identify the hostname and your relationship to it. We record suppression rather than deleting historical public evidence. A request already in flight may finish; suppression is rechecked before every subsequent network request. Suppression also removes the hostname’s entries from the Agent Web Atlas.

Publication in the Agent Web Atlas

Observations the bot makes of services listed in the Official MCP Registry may be published in the Agent Web Atlas. An entry shows the service origin, hashes of the endpoint address, its Registry listings, and factual results of up to 20 recent observations. For the latest observation it also shows each capability by its plain identifier (such as a tool name), its input names and declared sign-in schemes, AI-generated readings of what each capability does with their probabilities, and a summary that code writes from those readings. It shows no endpoint paths, links or publisher descriptions, and it never shows a scan that an InterfaceDelta account requested. Each entry links to a way to report an inaccuracy. See how the atlas is built and the Privacy Notice.