_ registry / mcp http-sse · checked 14m ago

email-dns-preflight-x402

https://email-dns-preflight-x402.copper-crate.workers.dev

Registry code: f748ea37626546d9

api record

Four read-only infrastructure-intelligence tools are available. Every tool call costs $0.001 native USDC on Base through x402. Tool discovery and protocol negotiation are free. Results are DNS/RDAP posture signals and do not claim mailbox existence, inbox delivery, identity or reputation.

endpoint
https://email-dns-preflight-x402.copper-crate.workers.dev/mcp
protocol
http-sse ·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 email-dns-preflight-x402 live?
Yes — it answered the hub's last check (checked 14m ago). It answered 99% of checks over the last 30 days.
Is email-dns-preflight-x402 free to use?
Yes — the hub reached it with no key and no payment.
What tools does email-dns-preflight-x402 have?
4 tools: domain_rdap, email_preflight, domain_preflight, domain_email_security.
Is email-dns-preflight-x402 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
98.6%

90 days 99.1%· all time 99.1%

latency
245ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 317 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
communication email
used for
  • check domain email authentication records
  • preflight an email address dns setup
  • look up domain rdap data
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 5 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
0

distinct

settlements
0

none in the window

received on chain
0 USDC

thin

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 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.

  • domain_rdap reads unknown 22h ago

    Privacy-safe RDAP/WHOIS-successor lookup for domain age, expiry, registrar, statuses, nameservers and DNSSEC delegation. Costs $0.001 native USDC on Base.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "maxLength": 253,
      "minLength": 1
    }
  }
}
    arguments 14 lines
  • email_preflight reads unknown never probed

    Validate practical email syntax and inspect DNS, mail routing, authentication and domain-security posture. DNS-level only; no SMTP mailbox-existence claim. Costs $0.001 native USDC on Base.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string",
      "maxLength": 254,
      "minLength": 3
    }
  }
}
    arguments 14 lines
  • domain_preflight reads unknown 22h ago

    Inspect DNS records, CAA, SPF/DMARC/DKIM/BIMI, DNSSEC, RDAP age/expiry, registrar-lock and nameserver-redundancy posture. Costs $0.001 native USDC on Base.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "maxLength": 253,
      "minLength": 1
    }
  }
}
    arguments 14 lines
  • domain_email_security reads unknown never probed

    Focused SPF/DMARC/DKIM/BIMI diagnostics with bounded recursive SPF lookup analysis, CAA/DNSSEC context and deterministic fixes. Costs $0.001 native USDC on Base.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "maxLength": 253,
      "minLength": 1
    }
  }
}
    arguments 14 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 f748ea37626546d9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f748ea37626546d9/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/f748ea37626546d9/badge.svg)](https://brick.blue/agent/f748ea37626546d9?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
80%

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.