DNSDumpster MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DNSDUMPSTER_API_KEY | Yes | Your DNSDumpster API key |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_domainA | Query DNSDumpster for all DNS records related to a domain. Args: domain: The domain name to query (e.g., example.com) ctx: Request context Returns: JSON string containing all DNS records |
| get_a_recordsC | Get A records for a domain. Args: domain: The domain name to query (e.g., example.com) ctx: Request context Returns: Formatted string containing A records |
| get_mx_recordsB | Get MX (mail) records for a domain. Args: domain: The domain name to query (e.g., example.com) ctx: Request context Returns: Formatted string containing MX records |
| get_ns_recordsC | Get NS (nameserver) records for a domain. Args: domain: The domain name to query (e.g., example.com) ctx: Request context Returns: Formatted string containing NS records |
| get_txt_recordsC | Get TXT records for a domain. Args: domain: The domain name to query (e.g., example.com) ctx: Request context Returns: Formatted string containing TXT records |
| get_cname_recordsC | Get CNAME records for a domain. Args: domain: The domain name to query (e.g., example.com) ctx: Request context Returns: Formatted string containing CNAME records |
| search_subdomainsC | Search for subdomains of a given domain. Args: domain: The parent domain name to query (e.g., example.com) ctx: Request context page: Page number for pagination (Plus accounts only) Returns: Formatted string containing subdomains found |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| lookup_domain | Look up DNS information for a domain. |
| check_dns_security | Check the DNS security configuration of a domain. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Every tool has a clearly distinct purpose targeting specific DNS record types or broader queries. The first five tools each handle a different record type (A, CNAME, MX, NS, TXT), while query_domain retrieves all records and search_subdomains focuses on subdomain discovery. There is no functional overlap between tools.
All tools follow a consistent verb_noun pattern with snake_case naming. The pattern is perfectly uniform: get_<record_type>_records for specific queries, query_domain for comprehensive retrieval, and search_subdomains for subdomain discovery. No deviations or mixed conventions exist.
With 7 tools, this server is well-scoped for DNS reconnaissance. The count covers all major DNS record types plus comprehensive and subdomain queries, making each tool essential without redundancy. This aligns perfectly with typical DNS investigation needs.
The toolset provides complete coverage for DNS domain investigation. It includes all common record types (A, CNAME, MX, NS, TXT), a comprehensive query tool, and subdomain search functionality. There are no obvious gaps for the server's stated purpose of DNS data retrieval.