dns-check
Live DNS lookups for agents: A/MX/TXT/SPF/CNAME/PTR with TTLs and DNSSEC, via Google Public DNS.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"dns-check": {
"url": "https://api.kaiv.ai/api/bridge/mcp/dns-check-e159a722"
}
}
}Remote endpoints
https://api.kaiv.ai/api/bridge/mcp/dns-check-e159a722streamable-httpWhat it can do
Tool inventory
Tools (1)
🟢resolve_dns(do, name, type)
Resolve any DNS record live via Google Public DNS. Answers: is DNS propagated? What are the MX/TXT/SPF/DKIM records? Where does this CNAME point? For reverse lookup pass name=<reversed-ip>.in-addr.arpa with type=PTR (e.g. 90.57.149.3.in-addr.arpa for 3.149.57.90). Returns Status (0 = NOERROR, 3 = NXDOMAIN), Answer records with TTLs, and the AD flag for DNSSEC validation.
Input Schema
{
"type": "object",
"properties": {
"do": {
"type": "string",
"x-in": "query",
"description": "Set 'true' to include DNSSEC records (RRSIG) in the response"
},
"name": {
"type": "string",
"x-in": "query",
"description": "Domain name to resolve, e.g. 'kaiv.ai' (or reversed IP + .in-addr.arpa for PTR)"
},
"type": {
"enum": [
"A",
"AAAA",
"MX",
"TXT",
"NS",
"CNAME",
"SOA",
"CAA",
"PTR",
"SRV"
],
"type": "string",
"x-in": "query",
"default": "A",
"description": "Record type: A, AAAA, MX, TXT, NS, CNAME, SOA, CAA, PTR, SRV. Default A."
}
},
"required": [
"name"
]
}Community
Evidence