Skip to main content
Glama
README.md
# dns-mcp

[![npm](https://img.shields.io/npm/v/@mukundakatta/dns-mcp.svg)](https://www.npmjs.com/package/@mukundakatta/dns-mcp)
[![mcp](https://img.shields.io/badge/protocol-MCP-blue.svg)](https://modelcontextprotocol.io)
[![license](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)

MCP server: resolve DNS records for a hostname. No external deps — uses
Node's built-in `dns/promises` resolver, which respects the host's
nameserver configuration.

## Tool

### `resolve`

```json
{ "hostname": "example.com", "type": "MX" }
```

→

```json
{
  "hostname": "example.com",
  "type": "MX",
  "records": [{ "priority": 0, "exchange": "." }]
}
```

Supported types: `A`, `AAAA`, `MX`, `TXT`, `CNAME`, `NS`, `SOA`, `SRV`,
`PTR`, `ANY`. Default is `A`.

## Configure

```json
{ "mcpServers": { "dns": { "command": "npx", "args": ["-y", "@mukundakatta/dns-mcp"] } } }
```

## License

MIT.

## Repository Health

This repository includes a dependency-free health check for core documentation, metadata, and CI wiring. Run it locally before publishing changes:

```sh
python3 scripts/check_repository_health.py
```

The same check runs in GitHub Actions on pushes and pull requests.

TDQS

A3.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap.

Naming Consistency5/5

The single tool name 'resolve' is clear and descriptive, and there is no inconsistency.

Tool Count5/5

One tool for DNS resolution is well-scoped and appropriate for the server's purpose.

Completeness5/5

The tool covers all major DNS record types (A, AAAA, MX, TXT, CNAME, NS, SOA, SRV, PTR, ANY), providing comprehensive resolution capabilities.

Maintenance

ActivityInactive
ResponsivenessNo issues