DNS MCP Server
Let your coding agent run live DNSSEC, email-authentication, and RDAP checks while you debug domains, email deliverability, or incident leads.
Overview
DNS MCP Server is an MCP server for the Ship phase that performs real-time DNS security analysis including DNSSEC, email authentication, and RDAP for agent-driven investigations.
What is this MCP server?
- Real-time DNS security analysis from the agent without leaving the IDE
- DNSSEC validation signals for trust-chain and signing problems
- Email authentication checks aligned with deliverability and spoofing review
- RDAP lookups for registrar and ownership context during triage
- Packaged as OCI image mclose/dns-mcp:1.3.4 with stdio MCP transport
- Server version 1.3.4 in MCP registry metadata
- Distributed as OCI identifier docker.io/mclose/dns-mcp:1.3.4
- stdio MCP transport per server.schema.json
What problem does it solve?
You need authoritative DNS and mail-auth answers fast while debugging domains, but jumping between CLI tools and browser checkers breaks your agent workflow.
Who is it for?
Solo builders shipping on custom domains, running transactional email, or doing lightweight incident triage on DNS and deliverability.
Skip if: Teams that need full passive DNS corpora, commercial threat intel feeds, or automated blocking—this is live lookup analysis, not a SIEM.
What do I get? / Deliverables
After you add the server, your agent can pull DNSSEC, email-auth, and RDAP findings in-thread so you can fix records or escalate with evidence attached.
- Agent-readable DNS security analysis for the queried zone
- DNSSEC and email-authentication signal summary for triage
- RDAP registration context for ownership and registrar checks
Recommended MCP Servers
Journey fit
DNS and mail-auth misconfigurations are classic pre-launch and post-incident risks; this server fits the Ship phase where you harden and verify external-facing identity before or after going live. Security subphase covers verifying domain integrity, spoofing resistance, and registrar metadata—the exact outputs this MCP exposes for investigations.
How it compares
MCP DNS security integration, not a passive threat-intel platform or a generic dig wrapper skill.
Common Questions / FAQ
Who is DNS MCP Server for?
Indie developers and small teams who use Claude Code or similar agents and need DNSSEC, email-auth, and RDAP answers during security checks or deliverability debugging.
When should I use DNS MCP Server?
Use it in Ship (security) when validating a production domain, investigating spoofing or DNSSEC failures, or confirming registrar data before you change MX, SPF, or DKIM.
How do I add DNS MCP Server to my agent?
Configure MCP stdio to run the OCI package docker.io/mclose/dns-mcp:1.3.4 per server.json, then restart your client so tools appear in the agent tool list.