ofershap/mcp-server-dns · Archived

dns-lookup

DNS lookups, reverse DNS, WHOIS, and domain checks via MCP. Use when asked to check DNS records or domain ownership.

First seen Mar 5, 2026

Installation

$ npx skills add ofershap/mcp-server-dns --skill dns-lookup

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,580 B
  • docs SUMMARY.md 134 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

DNS Lookup via MCP

Use this skill when you need to look up DNS records, perform reverse DNS, check WHOIS data, or verify nameservers. Zero auth required.

Available Tools

Tool What it does
dns_lookup Look up A, AAAA, MX, TXT, NS, CNAME, SOA, SRV, or PTR records
reverse_dns Reverse DNS (PTR) lookup on an IP address
resolve_all Resolve A, AAAA, MX, TXT, NS, CNAME in one call
check_nameservers Get nameserver (NS) records for a domain
whois Query WHOIS data (follows IANA referrals to registrar)

Workflow

  1. For general domain investigation: start with resolve_all to see everything at once
  2. For specific record types: use dns_lookup with the type parameter
  3. For IP investigation: use reverse_dns to find the hostname
  4. For domain ownership: use whois

Key Patterns

  • dns_lookup with type: "MX" is the go-to for email delivery debugging
  • resolve_all returns all common record types in one call — most efficient for initial investigation
  • whois follows IANA referrals automatically, so it works for any TLD
  • No API keys or auth needed — uses Node.js built-in DNS and public WHOIS servers