INDIVIDUAL MCP TOOL

top_domains

The DNS health of the top 100 domains as of the last DAILY snapshot: rcode, addresses, DNSSEC, nameservers and rank movement for each.

isitdns.netnone authenticationAvailability not checked

LIVE ENDPOINT

https://isitdns.net/mcp

No auth detected

Connect to this endpoint to inspect the live schema for top_domains and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

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

Codex

~/.codex/config.toml

[mcp_servers.isitdns]
url = "https://isitdns.net/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "isitdns": {
      "type": "http",
      "url": "https://isitdns.net/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: isitdns
Remote MCP URL: https://isitdns.net/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": {
    "isitdns": {
      "url": "https://isitdns.net/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "isitdns": {
      "type": "http",
      "url": "https://isitdns.net/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "isitdns",
  "transport": "streamable-http",
  "url": "https://isitdns.net/mcp"
}

MCP Inspector

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

dig — Ask a public DNS resolver, or any public address, for a record, live, from the isitdns seat.
check_domain — The five-check DNS audit for a domain: parent and child nameservers agree, no open recursion, DNSSEC chain, TTL sanity, mail posture.
trace — Walk the delegation from the root servers down to the authoritative server for a name, like dig +trace, and say in plain steps whether the delegation is healthy.
resolver_status — The live board: is public DNS OK right now?
resolver_history — The incident record for the public resolvers: start time, duration and severity of each.
dns_events — Days when several resolvers were unhealthy at once, as episodes: when each began, how long it ran, how many resolvers were affected at the peak, and which.
ksk_board — The RFC 8509 root key sentinel across the public resolvers: which resolvers trust which root KSK, and the root DNSKEY set as read now.