Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@DNS MCP Server look up A records for example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Python MCP server providing comprehensive DNS lookup capabilities.
dns_lookup: Query any DNS record type (A, AAAA, MX, TXT, NS, SOA, CNAME, SRV, CAA, DNSSEC records)
dns_reverse: Reverse DNS lookup (PTR) for IPv4/IPv6 addresses
dns_bulk: Query multiple domains in one call
dns_reverse_bulk: Reverse lookup for multiple IPs
Related MCP server: BasicSec MCP Server
docker compose up -dThe server will be available at https://localhost:8088/mcp.
Self-signed certificates are automatically generated on first startup.
Environment variables:
Variable | Default | Description |
|
| External HTTPS port |
|
| Domain for certificate generation |
|
| Server bind address |
|
| Server port |
|
| Query timeout in seconds |
|
| Max retry attempts |
| (system) | Default DNS resolver IP |
|
| Logging level |
To use this server with Claude Desktop, you'll need mcp-proxy to bridge the HTTP transport.
pip install mcp-proxy
# or
uv tool install mcp-proxydocker compose up -dEdit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"dns-lookup": {
"command": "mcp-proxy",
"args": [
"--transport=streamablehttp",
"--no-verify-ssl",
"https://localhost:8088/mcp"
]
}
}
}Note: Use the full path to mcp-proxy if Claude shows ENOENT errors (run
which mcp-proxyto find it).
The DNS tools will now be available in Claude Desktop.
Tool | Description |
| Query DNS records (A, AAAA, MX, TXT, NS, etc.) |
| Reverse DNS lookup for an IP address |
| Query multiple domains at once |
| Reverse lookup for multiple IPs |
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"pytestdns-mcp-serverdns-mcp-server-httpMIT
Query DNS records for multiple domains in one call.
Inputs: queries (required), resolver.
Query DNS records for a domain. Supports all record types including DNSSEC.
Inputs: domain (required), resolver, record_types.
Reverse DNS lookup (PTR) for an IP address.
Inputs: ip (required), resolver.
Reverse DNS lookup for multiple IP addresses.
Inputs: ips (required), resolver.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 4 tools
Each tool has a clearly distinct purpose: single forward lookup, single reverse lookup, bulk forward lookup, and bulk reverse lookup. There is no overlap between them, and an agent can easily choose the right one based on the operation and cardinality.
The naming follows a predictable pattern: 'dns_' prefix with an action and optional '_bulk' suffix. However, 'dns_bulk' deviates from the pattern used by 'dns_lookup' — a more consistent name would be 'dns_lookup_bulk'.
Four tools is well-scoped for a DNS lookup server. The set covers the essential operations without unnecessary bloat.
The domain is DNS queries, and the tools cover both forward and reverse lookups in singular and bulk forms. All record types are supported, including DNSSEC, so there are no obvious gaps for a read-only DNS lookup server.
Look up DNS information for any domain to troubleshoot issues and gather insights. Get fast, relia…
Unlock the power of DNS lookups with our DNS Lookup service using Google DNS-over-HTTPS. Whether
DNS records, SSL certificate, WHOIS/RDAP and website tech scan for any domain
DNS, WHOIS, SSL, IP geolocation, email validation, DNSBL blacklist, HTTP headers, subnet calc.