Skip to main content
Glama
Sign In
DNSDumpster MCP Server

DNSDumpster MCP Server

by anhhung04
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

DNSDumpster - MCP Server

A Model Context Protocol (MCP) server for interacting with the DNSDumpster API, enabling AI assistants to perform detailed DNS reconnaissance through natural language requests.

Features

  • Query domain DNS records through AI assistants

  • Retrieve detailed information about:

    • A records (with associated IP and ASN information)

    • CNAME records

    • MX records

    • TXT records

    • NS records

    • Banner information where available

  • Support for pagination (Plus accounts)

  • Rate limiting and caching

PyPI version

Related MCP server: dnsdumpster

Installation

# Install from PyPI
uv pip install mcp-dnsdumpster

# Or from source
git clone https://github.com/yourusername/mcp-dnsdumpster.git
cd mcp-dnsdumpster
uv pip install -e .

Claude Desktop Configuration

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %AppData%\Claude\claude_desktop_config.json on Windows):

{
  "mcpServers": {
    "dnsdumpster": {
      "command": "uvx",
      "args": ["mcp-dnsdumpster"],
      "env": {
        "DNSDUMPSTER_API_KEY": "your_api_key_here"
      }
    }
  }
}

Usage

  1. Set your API key:

export DNSDUMPSTER_API_KEY=your_api_key_here

  1. Run the server:

# Using uvx (recommended)
uvx mcp-dnsdumpster

# Or if installed from source
uv run server.py

Example Prompts

  • "Show me all subdomains for example.com"

  • "What are the mail servers for microsoft.com?"

  • "Tell me about the DNS infrastructure for twitter.com"

Development

  • Python 3.10+

  • Uses uv for dependency management

  • Built with MCP SDK 1.4+

License

MIT

Available Tools

7 tools
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

Inputs: domain (required). Returns: result

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

Inputs: domain (required). Returns: result

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

Inputs: domain (required). Returns: result

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

Inputs: domain (required). Returns: result

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

Inputs: domain (required). Returns: result

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

Inputs: domain (required). Returns: result

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

Inputs: domain (required), page. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • iDig DNS MCP Server

      kbhave
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes 19 professional DNS diagnostic tools from the iDig API, enabling AI clients to perform DNS lookups, email security audits, DNSSEC validation, propagation checks, and more through natural language.
      -

    • CyberMCP

      mrobi27
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to perform cybersecurity analysis including RDAP lookup, DNS analysis, SSL inspection, security header detection, and more, returning structured security reports.
      -

    Appeared in Searches