DomainDrift 1.18: the evidence bundle becomes a product, and a public index of who speaks MCP

DomainDrift watches more than a million domains continuously and signs every observation as it is made. Two things in 1.18: the export you hand to someone else grew up, and a piece of data we were already collecting became a public page.

The evidence bundle is its own product now

A bundle is a single self-contained export of one domain's signed record: the observations, the Ed25519 receipts that commit to them, and the keys those receipts verify against. Its whole purpose is to leave our hands. Someone who has never heard of DomainDrift, holding nothing but the file and the published keys, can check it offline without an account and without calling us.

That is a different kind of thing from an API read, so it stopped being priced and packaged like one. Bundles now have their own page explaining what is inside, what a signature does and does not prove, and how a recipient verifies it. They also have their own plan entitlement, included on Pro plans and up, rather than being a line item inside a request allowance.

The honest part is worth stating plainly: a signature proves attribution and integrity, that we observed this at this time and the record has not been altered since. It is added accountability, not a claim that the world was correctly described. What the bundle does is make that accountability portable.

Who speaks MCP

A domain can advertise where its AI agent endpoint lives by publishing a TXT record at `_mcp._tcp` on its own name. DomainDrift has read that record on every scan for a while, and until now it went into the signed record and stopped there.

It is now a page. Who speaks MCP is the running index of domains observed advertising a Model Context Protocol endpoint in their DNS, each linked to its own signed record so you can see when we saw it. The list grows as the scanner works through the catalog, so it climbs rather than arriving complete.

One caveat we would rather state than let you infer: an advertisement is a claim a domain makes about itself. It is not a verification that a working server answers there. The page says so on the page.

Connecting your own agent

DomainDrift's own MCP server has been live since 1.17, and there is now a step-by-step connect guide covering Claude, Claude Code, ChatGPT developer mode, and any other client that speaks streamable HTTP. It works today, in developer mode, without waiting on any app directory.

Start at domaindrift.io/bundle or domaindrift.io/mcp-adoption.