DomainDrift 1.17: plug an AI agent straight into signed internet telemetry

DomainDrift watches more than a million domains on a continuous loop and signs every observation the moment it is made: DNS, certificates, mail posture, registration, reachability. Version 1.17 gives that record a native door for AI agents.

The Model Context Protocol is how agents connect to live tools. DomainDrift now speaks it directly at `https://domaindrift.io/mcp`, with a machine-readable descriptor at `/.well-known/mcp.json`. Point a client at the URL and the tools are just there.

Five tools, one URL

The server is read-only and deliberately small. lookup_domain returns the latest observation of any domain: who runs its nameservers, mail, and CDN, the certificate issuer and expiry, reachability, and the receipt pointer. whats_changed_today is the daily change digest, the ranked top of what moved on the internet in the last 24 hours. resolve_receipt turns any receipt id into its public Ed25519 commitment. internet_tape is the rolling 24-hour aggregate. signing_keys fetches the published keys everything verifies against.

Connecting takes one line in most clients.

claude mcp add --transport http domaindrift https://domaindrift.io/mcp

https://domaindrift.io/mcp  (Claude connectors, ChatGPT developer mode, any streamable-HTTP MCP client)

The first look is free, and the meter is the same

A keyless agent gets a real, current preview of any single domain: derived facts and counts, throttled to one request every fifteen seconds per address under a shared daily ceiling. That is enough to see the product work before anyone signs up for anything.

An API key, minted free with a DRM3 account, opens the complete signed record on the account's metered allowance. MCP uses the same pay gate as the API: same keys, same limits, same honest 429s and 402s. There is no separate agent tier to reason about, because the tools are the API.

A card your agent can show

Clients that render components get more than JSON. The lookup tool ships a live domain card: providers, certificate, reachability, and a link to the Ed25519 receipt, rendered inline in the conversation. Clients that only read text lose nothing; the same result arrives either way.

Verify it, do not take it

Every full record is signed, every receipt resolves publicly, and the signing keys are published at a well-known URL. A signature proves who observed a thing and that the record has not been altered since; it is added accountability that travels with the data, into whatever your agent builds from it.

Start at domaindrift.io/agents: the connect snippets, the tool list, and the access model, all on one page.