
Dns
io.github.ofershapPublished by GitHub account ofershapv1.0.1Updated Oct 24, 2026
MCP server for DNS lookups, reverse DNS, WHOIS, and domain checks — zero auth, zero config
Overview
Lets an assistant run DNS lookups, reverse DNS, nameserver checks, and WHOIS queries for domains and IP addresses.
- What you can do
- Provides tools for querying DNS records: dns_lookup covers A, AAAA, MX, TXT, NS, CNAME, SOA, SRV, and PTR records; reverse_dns performs PTR lookups on IP addresses; resolve_all returns A, AAAA, MX, TXT, NS, and CNAME in one call; check_nameservers returns NS records; and whois queries registration data, following IANA referrals to the registrar. It uses Node.js built-in DNS resolution and public WHOIS servers.
- When to use it
- Useful during development when you need to inspect DNS records or domain ownership, such as debugging email delivery via MX records, checking nameservers for a new domain, or investigating a suspicious URL through WHOIS.
- Requirements
- Runs locally over stdio as an npm package (mcp-server-dns), typically started with npx, so Node.js is required. No accounts, API keys, environment variables, or headers are declared. Network access is needed for DNS and WHOIS queries.
Installation
In SourceWeft
- Open Dns in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-server-dns
[npm version] [npm downloads] [CI] [TypeScript] [License: MIT]
DNS lookups, reverse DNS, WHOIS, and domain checks from your AI assistant. No API keys, no config. Powered by Node.js built-in DNS.
Works with Claude Desktop, Cursor, VS Code Copilot, and any MCP client. Uses Node.js native
dnsmodule, so there's nothing to sign up for.
[MCP server for DNS lookups, WHOIS queries, and domain checks]
Demo built with remotion-readme-kit
Why
DNS and WHOIS lookups come up more often than you'd think during development. Debugging email delivery? You need MX records. Setting up a new domain? Check the nameservers. Investigating a suspicious URL? WHOIS tells you who owns it. The existing MCP options for this require paid API keys (like WhoisXML API). This server uses Node.js built-in DNS resolution and public WHOIS servers, so it works out of the box with zero accounts or credentials.
Tools
Quick Start
Cursor
Add to .cursor/mcp.json:
Claude Desktop
Add to claude_desktop_config.json:
VS Code
Add to user settings or .vscode/mcp.json:
Examples
- "What are the DNS records for example.com?"
- "Do a reverse DNS lookup on 8.8.8.8"
- "Show me the WHOIS info for github.com"
- "What nameservers does cloudflare.com use?"
- "Resolve all record types for google.com"
- "Check the MX records for my-company.com"
Development
See also
More MCP servers and developer tools on my portfolio.
Author
README built with README Builder
License
MIT © 2026 Ofer Shapira
Source: README.md at commit f557553
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts