mcp-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_dnsA | Resolve DNS records (A, AAAA, MX, TXT, NS, CNAME) for any host |
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 1 tool
With only one tool, there is no possibility of overlapping purposes. The tool's purpose is singular and unambiguous.
The single tool follows the verb_noun pattern (resolve_dns), which is clear and consistent. With only one tool, there are no conflicting conventions.
A single tool for DNS resolution is minimal but functional. It feels slightly thin for a server, but the one tool does cover the primary domain adequately.
The tool covers common record types (A, AAAA, MX, TXT, NS, CNAME) but omits less common types like PTR, SRV, or SOA. This is a minor gap for most DNS use cases.