CONTINUOUS INTERNET TELEMETRY24H DRIFT10,473 material changesacross 10,074 domains · last 24h · -156 vs yesterdayDNS DRIFT663 domains changed DNS providertop destination cloudflare.com · -117 vs yesterdayEMAIL DRIFT180 domains switched email providertop destination google.com · +10 vs yesterdayCERT DRIFT224 domains switched issuing CA24h · -6 vs yesterdayNOW703 curated domains not reachable-646 vs yesterdaySITE ERRORS18,070 sites serving errorslast probe · 5xx / 404 / TLSTHROTTLED96,657 throttled or blocked our scanner429 rate-limit / 403 bot-block
MCP adoption

Who speaks MCP.

The Model Context Protocol is how AI agents connect to live tools, and a domain can advertise its MCP endpoint in its own DNS: a TXT record at _mcp._tcp.<domain>. DomainDrift already reads that record on every scan of the catalog, so this page is the running index of domains observed advertising MCP.

0

domains currently advertising MCP in DNS, of the continuously scanned catalog

DomainObserved (UTC)
None observed yet in the current enrichment cycle.

An advertisement is a claim the domain makes about itself, not a verification that a working MCP server answers there. Each row reflects the domain's most recent enrichment pass, so the set updates on the scan cadence, not in real time. Every underlying observation is Ed25519-signed like everything else in the record.

Advertise yours

Publish a TXT record at _mcp._tcp.<your-domain> naming your endpoint (ours reads v=mcp1 endpoint=https://domaindrift.io/mcp) and the scanner will pick it up on its next pass. DomainDrift's own MCP door and connect instructions live on the agents page.