mcpbeat

DNS Lookup API MCP Server

io.github.Br0ski777/dns-lookup
answering

DNS Lookup API is answering right now. Last checked 15 min ago. It exposes 1 tools. Last commit 19 Jul 2026.

DNS record lookup — A, AAAA, MX, TXT, CNAME, NS via Cloudflare. x402 micropayment.

Uptime history 42 hours of history
42 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
27 ms
Response time
average over 24h
0
Stars
last commit 19 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add dns-lookup --transport http https://dns-lookup.api.klymax402.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "dns-lookup": {
      "url": "https://dns-lookup.api.klymax402.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.dns-lookup]
url = "https://dns-lookup.api.klymax402.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "dns-lookup": {
      "url": "https://dns-lookup.api.klymax402.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "dns-lookup": {
      "url": "https://dns-lookup.api.klymax402.com/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

network
network_lookup_dns
Use this when you need to look up DNS records for a domain. Returns all matching records in JSON via Cloudflare DNS-over-HTTPS. Returns: 1. records array with type, name, data, TTL 2. Supports A, AAAA, MX, TXT, CNAME, NS, SOA, SRV 3. queryTime in ms 4. resolver info (Cloudflare 1.1.1.1). Example output: {"domain":"example.com","type":"A","records":[{"name":"example.com","type":"A","data":"93.184.216.34","ttl":3600}],"queryTime":12,"resolver":"cloudflare"} Use this FOR verifying DNS configuration, checking MX records before email setup, auditing TXT records for SPF/DKIM/DMARC, and debugging domain resolution issues. Do NOT use for SSL certificate check -- use security_check_ssl instead. Do NOT use for WHOIS domain info -- use domain_lookup_intelligence instead. Do NOT use for HTTP header analysis -- use network_analyze_headers instead.

Endpoints

URLTransportStateLatencyChecked
https://dns-lookup.api.klymax402.com/mcp sse answering 24 ms 15 min ago

DNS Lookup API — questions

Answers built from our own checks of this server.

What can DNS Lookup API do?
It exposes 1 tools, read directly from the server on our last check. Among them: network_lookup_dns. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is DNS Lookup API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 27 ms. The bar chart above shows every period we have measured.
How do I connect DNS Lookup API?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does DNS Lookup API need an API key?
No. DNS Lookup API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is DNS Lookup API?
It answers our handshake in 27 ms on average, which is faster than 99% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is DNS Lookup API open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.