mcp-dns
by tudadada
README.md
# mcp-dns
[](https://www.npmjs.com/package/mcp-dns)
[](https://opensource.org/licenses/MIT)
[](https://modelcontextprotocol.io)
Model Context Protocol (MCP) server for deep DNS resolution, nameserver propagation, and DNSSEC validation.
---
## ⚡ Core Capabilities
- **`resolve_dns`**: Resolve DNS records (A, AAAA, MX, TXT, NS, CNAME) for any host
### Planned Ecosystem Sub-Branches
- `mcp-dns-lookup`
- `mcp-dns-records`
- `mcp-dns-propagation`
---
## 🚀 Quick Start (Running with AI Clients)
### Claude Desktop Integration
Add this configuration snippet to your `claude_desktop_config.json`:
```json
{
"mcpServers": {
"dns": {
"command": "npx",
"args": ["-y", "mcp-dns"]
}
}
}
```
### Cursor IDE Integration
Add as a new stdio transport server:
- **Command:** `npx -y mcp-dns`
---
## 📦 Local Usage
```bash
npx mcp-dns
```
---
## 📄 License
MIT License. Designed and maintained for the global Model Context Protocol ecosystem.
TDQS
A4.1/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of overlapping purposes. The tool's purpose is singular and unambiguous.
Naming Consistency5/5
The single tool follows the verb_noun pattern (resolve_dns), which is clear and consistent. With only one tool, there are no conflicting conventions.
Tool Count3/5
A single tool for DNS resolution is minimal but functional. It feels slightly thin for a server, but the one tool does cover the primary domain adequately.
Completeness4/5
The tool covers common record types (A, AAAA, MX, TXT, NS, CNAME) but omits less common types like PTR, SRV, or SOA. This is a minor gap for most DNS use cases.
Maintenance
ActivityMaintained
ResponsivenessNo issues