mcp-server-dns
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dns_lookupC | Look up DNS records for a domain. Returns A, AAAA, MX, TXT, NS, CNAME, SOA, SRV, or PTR records. |
| reverse_dnsB | Perform a reverse DNS (PTR) lookup on an IP address. |
| resolve_allA | Resolve all common DNS record types (A, AAAA, MX, TXT, NS, CNAME) for a domain in one call. |
| check_nameserversC | Get the nameserver (NS) records for a domain. |
| whoisB | Query WHOIS data for a domain. Uses IANA and follows referrals to registrar WHOIS servers. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The tools are mostly distinct with clear purposes: dns_lookup for specific record types, resolve_all for common records in bulk, reverse_dns for PTR lookups, and whois for domain registration data. However, check_nameservers overlaps with dns_lookup (which can also return NS records) and resolve_all (which includes NS), potentially causing confusion in tool selection.
The naming follows a consistent snake_case pattern with descriptive verb-noun combinations (e.g., dns_lookup, reverse_dns). Minor deviations exist: check_nameservers uses 'check' while others use more specific verbs like 'lookup' or 'resolve', but overall the convention is readable and predictable.
With 5 tools, this server is well-scoped for DNS operations. Each tool serves a distinct function in the domain, and the count is neither too sparse nor bloated, making it manageable for agents to handle typical DNS-related tasks effectively.
The toolset covers essential DNS operations: lookup, bulk resolution, reverse lookups, and WHOIS queries. A minor gap exists in lacking explicit tools for DNS record management (e.g., create or update records), but this is reasonable if the server is focused on querying rather than administration, and agents can still perform core diagnostic tasks.