io.domaindrift/domaindrift
REMOTE · DOMAINDRIFT.IO · SCANNED SEP 22
Signed internet telemetry, read-only: DNS, TLS, WHOIS, reachability. Every record Ed25519-signed.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 553 tokens (~92/item across 6 items; 5 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
How do I install the io.domaindrift/domaindrift MCP server?
io.domaindrift/domaindrift is a hosted endpoint at https://domaindrift.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · domaindrift.io
claude mcp add --transport http io-domaindrift-domaindrift 'https://domaindrift.io/mcp'
{
"mcpServers": {
"io-domaindrift-domaindrift": {
"url": "https://domaindrift.io/mcp"
}
}
} {
"servers": {
"io-domaindrift-domaindrift": {
"type": "http",
"url": "https://domaindrift.io/mcp"
}
}
} [mcp_servers.io-domaindrift-domaindrift] url = "https://domaindrift.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-domaindrift-domaindrift": {
"type": "remote",
"url": "https://domaindrift.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-domaindrift-domaindrift --url 'https://domaindrift.io/mcp' --transport streamable-http
mcp_servers:
io-domaindrift-domaindrift:
url: "https://domaindrift.io/mcp" {
"McpServers": {
"io-domaindrift-domaindrift": {
"Transport": "http",
"Url": "https://domaindrift.io/mcp"
}
}
} assistant mcp add io-domaindrift-domaindrift -t streamable-http -u 'https://domaindrift.io/mcp'
{
"mcpServers": {
"io-domaindrift-domaindrift": {
"type": "http",
"url": "https://domaindrift.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 0
- Server version: 1.201.2 → 1.202.0 functional
- 18 Sept 26 0
- Server version: 1.200.4 → 1.201.2 functional
- 17 Sept 26 0
- Server version: 1.200.3 → 1.200.4 functional
- 11 Sept 26 0
- Server version: 1.200.2 → 1.200.3 functional
- 10 Sept 26 0
- Server version: 1.200.0 → 1.200.2 functional
- 7 Sept 26 0
- Server version: 1.199.1 → 1.200.0 functional
- 2 Sept 26 0
- Server version: 1.196.0 → 1.199.1 functional
- 31 Aug 26 0
- Server version: 1.195.5 → 1.196.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://domaindrift.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=domaindrift.io | CN=WE1,O=Google Trust Services,C=US | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b777b4bcd6d3b460e016d485533a0c0 |
| SANs: domaindrift.io, www.domaindrift.io, *.www.domaindrift.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of domaindrift.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| domaindrift.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://domaindrift.io/mcp | Verified | 200 | |
| http (plaintext) | http://domaindrift.io/mcp | HTTPS enforced | 301 | https://domaindrift.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
internet_tape The 24-hour tape ~52
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. Public and keyless.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_domain Look up one domain ~126
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. Keyless calls get this reduced preview, throttled to 1 request per 15 seconds per IP under a shared daily ceiling. Connect with a DomainDrift API key in an Authorization: Bearer header to get the complete signed record instead, metered against your account like any API request.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Registrable domain name, e.g. "example.com" |
No output schema declared.
No examples provided.
resolve_receipt Resolve a provenance receipt ~80
Resolve any DomainDrift provenance receipt by id: the public Ed25519 commitment (output hash, signing key, timestamp, chain link) for one observation. Public and keyless. Verify the signing key against /.well-known/domaindrift-keys.json.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Receipt id, as returned in any signed record or preview |
No output schema declared.
No examples provided.
signing_keys Published signing keys ~45
The Ed25519 public keys that sign every DomainDrift observation, with derivation paths and validity windows. Public and keyless. Use these to verify receipts and signed records offline.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
whats_changed_today Today's change digest ~74
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. Public and keyless. The complete change wire with sync cursors is the keyed /v1/changes endpoint.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.domaindrift/domaindrift MCP server?
io.domaindrift/domaindrift is an MCP server listed in the public MCP registry as io.domaindrift/domaindrift. Signed internet telemetry, read-only: DNS, TLS, WHOIS, reachability. Every record Ed25519-signed. This page covers its hosted endpoint (https://domaindrift.io/mcp).
Is the io.domaindrift/domaindrift MCP server safe to use?
io.domaindrift/domaindrift scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.domaindrift/domaindrift MCP server expose?
io.domaindrift/domaindrift exposes 5 tools: lookup_domain, whats_changed_today, resolve_receipt, internet_tape, signing_keys. Their descriptions and schemas cost roughly 377 tokens of context every time the server is loaded.
Does the io.domaindrift/domaindrift MCP server require authentication?
No. We connected to io.domaindrift/domaindrift without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.domaindrift/domaindrift MCP server still maintained?
io.domaindrift/domaindrift is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.