Server facts
mcp-server-dns
Project
- Author
- ofershap
- Repository
- github.com/ofershap/mcp-server-dns
- License
- Not specified
- Category
- Cloud & DevOps
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 3
- Last commit
- Data as of
Overview
Domain and email troubleshooting shape the tools in mcp-server-dns. Developers can use dns_lookup to request individual record types, including MX for mail routing and NS for nameservers, alongside A, AAAA, TXT, CNAME, SOA, SRV, and PTR. For a broader view, resolve_all retrieves address, mail, text, nameserver, and canonical-name records together. The dedicated check_nameservers tool focuses on a domain’s NS records, while reverse_dns accepts an IP address for a PTR lookup. These operations support tasks such as investigating delivery problems or checking DNS when setting up a domain.
Registration research is handled separately by whois, which starts with IANA and follows referrals to registrar WHOIS services. The project combines public WHOIS servers with the DNS functionality built into Node.js, without requiring API keys or account registration. Its documentation provides client configuration examples for Claude Desktop, Cursor, and VS Code Copilot, and states compatibility with other MCP clients. Communication uses the stdio transport.
mcp-server-dns setup notes
- mcp-server-dns records stdio only; confirm a network transport upstream before planning remote access.
- mcp-server-dns has no recorded license; confirm reuse terms in its repository.