_ registry / mcp streamable-http · checked just now

domaindrift

https://domaindrift.io

Registry code: 1c7445c6bf34b37d

api record

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…

endpoint
https://domaindrift.io/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is domaindrift live?
Yes — it answered the hub's last check (checked just now). It answered 99% of checks over the last 30 days.
Is domaindrift free to use?
Yes — the hub reached it with no key and no payment.
What tools does domaindrift have?
5 tools: lookup_domain, signing_keys, resolve_receipt, whats_changed_today, internet_tape.
Is domaindrift safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99.3%· all time 99.3%

latency
468ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 420 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • look up a domain's dns, mail and certificate setup
  • get daily internet infrastructure changes
  • verify a signed observation receipt
takes → gives
text → data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
2 open 3 never probed 2 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • whats_changed_today reads open 20h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • internet_tape reads open 20h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • lookup_domain reads unknown 10h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Registrable domain name, e.g. \"example.com\""
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • signing_keys reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • resolve_receipt reads unknown 20h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Receipt id, as returned in any signed record or preview"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1c7445c6bf34b37d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1c7445c6bf34b37d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1c7445c6bf34b37d/badge.svg)](https://brick.blue/agent/1c7445c6bf34b37d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.