_ registry / mcp streamable-http · checked 1h ago

dns.pizza

https://dns.pizza

Registry code: 2444a60930331a4c

api record

Free domain-intelligence checks from dns.pizza: domain age/registration (check_domain_age), email authentication (check_email_auth), live TLS certificates (check_ssl), and DNS records (dns_lookup). Network checks share the site's anonymous rate limit (30/minute per IP).

When a check finds a problem, get_fix_guide returns provider-specific, doc-verified steps to publish the fix (SPF/DMARC/CAA). To keep a domain watched continuously — uptime, DNS changes, certificate expiry, blacklists, with alerts by email/Slack/Discord/webhook — see list_monitoring_plans; signup at https://dns.pizza/pricing.…

endpoint
https://dns.pizza/api/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 dns.pizza live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is dns.pizza free to use?
Yes — the hub reached it with no key and no payment.
What tools does dns.pizza have?
10 tools: check_ssl, check_email_auth, dns_lookup, get_fix_guide, get_checkout_link, zone_intel, zone_census, check_domain_age, ….
Is dns.pizza 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
100%

90 days 100%· all time 100%

latency
269ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 10 tools
2 open 8 never probed 2 of 10 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.

  • list_monitoring_plans open 1h ago

    dns.pizza monitoring plans: prices, monitor limits, check-interval floors, monitor types, and notification channels. Monitors keep watching what these tools check once — uptime, DNS changes, certificate expiry, blacklists — and alert by email, Slack, Discord, or webhook. Signup at https://dns.pizza/pricing.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • zone_risk_list open 1h ago

    Newborn domains the risk scorer flagged on a day (default: newest scored day), highest score first, each with the matched signals, the matching text and any model opinion. tier is the minimum tier (default high). Signals, not verdicts: nothing here is a finding that a site is malicious; present the evidence and the dispute link, never a bare label.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "day": {
      "type": "string",
      "description": "YYYY-MM-DD; omit for newest"
    },
    "tld": {
      "type": "string",
      "description": "Restrict to one TLD, e.g. xyz"
    },
    "tier": {
      "enum": [
        "critical",
        "high",
        "medium",
        "low"
      ],
      "type": "string",
      "description": "Minimum tier to include (default high)"
    },
    "brand": {
      "type": "string",
      "description": "Restrict to rows matching this brand token"
    },
    "limit": {
      "type": "integer",
      "description": "Rows to return, 1-100 (default 25)"
    }
  }
}
    arguments 31 lines
  • check_ssl unknown never probed

    Live TLS handshake against port 443: issuer, subject, SANs, validity window, days until expiry, protocol and cipher. valid:false plus an error field is an answer (the host's TLS is broken), not a tool failure.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Registrable domain or hostname, e.g. example.com"
    }
  }
}
    arguments 12 lines
  • check_email_auth unknown never probed

    Email authentication posture: SPF record and qualifier, DKIM keys across common selectors, DMARC policy/alignment/reporting, and MX records — with a 0-100 score and plain-language recommendations. A DKIM selector not found here can still exist under a custom name.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Registrable domain or hostname, e.g. example.com"
    }
  }
}
    arguments 12 lines
  • dns_lookup unknown never probed

    DNS records for a domain. records[type] === null together with a queryErrors entry means that lookup could not be completed — NOT that the records don't exist.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain to resolve, e.g. example.com"
    },
    "recordTypes": {
      "type": "array",
      "items": {
        "enum": [
          "A",
          "AAAA",
          "MX",
          "NS",
          "TXT",
          "SOA",
          "CAA",
          "CNAME",
          "PTR",
          "SRV",
          "NAPTR",
          "DNSKEY",
          "DS"
        ],
        "type": "string"
      },
      "description": "Record types to resolve; omit for the default set (A, AAAA, MX, NS, TXT, SOA, CAA)"
    }
  }
}
    arguments 34 lines
  • get_fix_guide unknown never probed

    Step-by-step instructions for publishing an SPF, DMARC, or CAA record on a specific DNS provider — exact field names, provider quirks, and verification steps, fact-checked against the provider's docs. Use provider 'generic' when the provider isn't known or listed.

    mcp-tool

    {
  "type": "object",
  "required": [
    "record"
  ],
  "properties": {
    "record": {
      "enum": [
        "spf",
        "dmarc",
        "caa"
      ],
      "type": "string",
      "description": "Which record to publish"
    },
    "provider": {
      "enum": [
        "cloudflare",
        "route53",
        "godaddy",
        "squarespace",
        "namecheap",
        "wix",
        "generic"
      ],
      "type": "string",
      "description": "DNS provider (where the domain's nameservers point). Defaults to 'generic'."
    }
  }
}
    arguments 30 lines
  • get_checkout_link unknown never probed

    Mint a checkout link for a dns.pizza monitoring plan to hand to the user. The link opens the pricing page, survives sign-in/signup, and then launches Stripe Checkout for the chosen plan automatically — the user only enters payment in their own browser; accounts already on a paid plan are shown a manage-plan message instead of being charged twice. Use after diagnosing a problem the user wants watched continuously.

    mcp-tool

    {
  "type": "object",
  "required": [
    "plan"
  ],
  "properties": {
    "plan": {
      "enum": [
        "starter",
        "pro",
        "business"
      ],
      "type": "string",
      "description": "Paid plan to check out"
    },
    "interval": {
      "enum": [
        "monthly",
        "yearly"
      ],
      "type": "string",
      "description": "Billing interval; yearly is two months free. Defaults to monthly."
    }
  }
}
    arguments 25 lines
  • zone_intel unknown never probed

    What dns.pizza's daily zone census saw for a domain: the day it first appeared in a DNS zone (~1,050 gTLDs plus a .com/.net sample), what was behind it that day (active site / parked / registered-no-site / nothing, and the subject when live), and every day the risk scorer flagged it with the matched signals and any model opinion. born:null with risk:[] means NO RECORD in the retained window — never 'old' or 'safe'. Signals, not verdicts.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Registrable domain or hostname, e.g. example.com"
    }
  }
}
    arguments 12 lines
  • zone_census unknown never probed

    Daily zone-census aggregates: births and deaths across the watched zones, the five-way split of newborns, what live newborn sites are about, per-TLD counts, parking vendors, platforms, and the day's risk-scorer summary (tiers, opinion counts, per-TLD flagged rates). Omit day for the newest day. Aggregates only — no domain is named.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "day": {
      "type": "string",
      "description": "UTC zone day, YYYY-MM-DD. Omit for the newest day."
    }
  }
}
    arguments 9 lines
  • check_domain_age unknown 1h ago

    Domain registration and history: creation/expiry dates and registrar from RDAP/WHOIS, plus first/latest Internet Archive captures. Partial results are normal — registry data still returns when archive.org is down, and vice versa.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Registrable domain or hostname, e.g. example.com"
    }
  }
}
    arguments 12 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 2444a60930331a4c.

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

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
1
ok
1
failed
0
success rate
100%
median latency
2,622ms
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
—

1 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.