General Tools
isitdns.net
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://isitdns.net/mcp
MCP server metadata
- Name
- isitdns
- Version
- 2026-09-10
Live DNS from isitdns.net. dig asks any public resolver (or any public address) for a record and returns the answer, flags, rcode, EDE and latency. check_domain audits a domain (delegation, DNSSEC, nameservers, mail posture); given a hostname, the zone-level checks are about the zone it sits in, and the answer names that zone. trace walks the delegation from the root. resolver_status is the live board of the public resolvers, read every 3 minutes over DoT. resolver_history is their incident record. top_domains is the DNS health of the top 100 domains as of the last daily snapshot. dns_events is the days several resolvers were unhealthy at once. ksk_board is the RFC 8509 root-key sentinel across those resolvers. Every reading carries the time it was read and the seat it was read from (the isitdns seat, never the user's network). Free, no key, 100 calls a minute per address. Docs: https://isitdns.net/agents
Known tools 8
digAsk a public DNS resolver, or any public address, for a record, live, from the isitdns seat.
Inferred read-onlycheck_domainThe five-check DNS audit for a domain: parent and child nameservers agree, no open recursion, DNSSEC chain, TTL sanity, mail posture.
Inferred read-onlytraceWalk 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.
Inferred read-onlyresolver_historyThe incident record for the public resolvers: start time, duration and severity of each.
Inferred read-onlytop_domainsThe DNS health of the top 100 domains as of the last DAILY snapshot: rcode, addresses, DNSSEC, nameservers and rank movement for each.
Inferred read-onlydns_eventsDays 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.
Inferred read-onlyksk_boardThe RFC 8509 root key sentinel across the public resolvers: which resolvers trust which root KSK, and the root DNSKEY set as read now.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
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.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.