Skip to main content
Glama

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: Domain-MCP

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_recordsB

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).

get_cname_recordsA

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).

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).

get_ns_recordsB

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).

get_txt_recordsB

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).

query_domainC

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).

search_subdomainsA

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.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a specific and distinct DNS record type or operation (individual records, combined query, subdomain search). No overlap or ambiguity.

    Naming Consistency4/5

    Most tools follow the 'get_*_records' pattern, but 'query_domain' and 'search_subdomains' break the pattern. Still, all names are descriptive and predictable.

    Tool Count5/5

    7 tools is an ideal size for a DNS lookup server—covers essential record types and common operations without being overwhelming.

    Completeness4/5

    Covers core DNS records (A, CNAME, MX, NS, TXT) plus subdomains, but lacks some common types like AAAA, SOA, or SRV. Minor gap but main functionality is complete.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol server that enables natural language querying of the Censys Search API for domain, IP, and FQDN reconnaissance, providing information about hosts, DNS, certificates, and services in real-time.
      6
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A simple MCP server that enables AI assistants to perform domain research including availability checking, WHOIS lookups, DNS record retrieval, and finding expired domains without requiring API keys.
      68
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server that exposes multiple OSINT tools to AI assistants like Claude, enabling sophisticated reconnaissance and information gathering tasks using industry-standard OSINT tools.
      249
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that connects AI assistants to your Domain Pilot account, enabling management of domains, DNS records, uptime monitoring, and SSL status through natural language.
      15
      16 npm
      MIT