Skip to main content
Glama
MaxWeeden

dnsdumpster

by MaxWeeden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DNSDUMPSTER_API_KEYYesYour 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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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
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
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_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
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
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
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

Prompts

Interactive templates invoked by user choice

NameDescription
lookup_domainLook up DNS information for a domain.
check_dns_securityCheck the DNS security configuration of a domain.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

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
ResponsivenessNo issues

Resources