Analytics

domaindrift.io

Monitors and analyzes changes in domain infrastructure (DNS, TLS, WHOIS) and provides daily digests and provenance receipts.

1 endpoint5 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://domaindrift.io/mcp

No auth detected

MCP server metadata

Name: domaindrift
Version: 1.195.5

Capabilities

toolsresources

Server instructions

DomainDrift is continuously observed, Ed25519-signed internet telemetry. Every tool here is read-only and is a name for an existing HTTP route, served through the same access lanes as the rest of the API: keyless calls get real but reduced data under a per-IP throttle and a shared daily ceiling; connect with a DomainDrift API key in an Authorization: Bearer header (a DRM3 account mints one at https://domaindrift.io/api) to open the complete signed record on your metered allowance. A 402 tool error is the x402 pay-per-call menu (USDC on Base, X-PAYMENT header). A signature proves attribution and integrity; it is added trust, not correctness.

Known tools 5

lookup_domain

The latest signed observation of one domain: who runs its nameservers, mail, and CDN; certificate issuer and expiry; HTTPS reachability; per-record-type counts; and the Ed25519 receipt pointer.

Inferred read-only

whats_changed_today

The daily "what changed on the internet" digest: a ranked top-20 of the most significant DNS, TLS, WHOIS, and infrastructure changes observed across the tracked catalog in the last 24 hours.

Inferred read-only

resolve_receipt

Resolve any DomainDrift provenance receipt by id: the public Ed25519 commitment (output hash, signing key, timestamp, chain link) for one observation.

Inferred read-only

internet_tape

The rolling 24-hour aggregate rollup: how many domains changed DNS provider, switched certificate authority, moved mail, went unreachable, and the other tape legs, each with a live count.

Inferred read-only

signing_keys

The Ed25519 public keys that sign every DomainDrift observation, with derivation paths and validity windows.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.domaindrift]
url = "https://domaindrift.io/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "domaindrift": {
      "type": "http",
      "url": "https://domaindrift.io/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: domaindrift
Remote MCP URL: https://domaindrift.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "domaindrift": {
      "url": "https://domaindrift.io/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "domaindrift": {
      "type": "http",
      "url": "https://domaindrift.io/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "domaindrift",
  "transport": "streamable-http",
  "url": "https://domaindrift.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for domaindrift.io was fetched 2026-07-27T02:30:29.242Z and is being refreshed.

Trust status Neutral

domaindrift.io is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.