DNS And WHOIS Query MCP Server

DNS And WHOIS Query MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Perform DNS lookups, WHOIS queries, connectivity testing, TLS certificate analysis, HTTP endpoint monitoring, and hostname resolution, all from your trusty AI.

What you get

mcp-netutils is a Model Context Protocol (MCP) server providing comprehensive network and domain analysis capabilities for AI assistants. It enables AI models to perform DNS lookups, WHOIS queries, connectivity testing, TLS certificate analysis, HTTP endpoint monitoring, and hostname resolution.

• Local DNS Queries — Perform DNS lookups using the OS-configured DNS servers
• Remote DNS-over-HTTPS — Perform secure DNS queries via Cloudflare and Google DNS-over-HTTPS services
• WHOIS Lookups — Perform WHOIS queries to get domain registration information
• Hostname Resolution — Convert hostnames to their corresponding IP addresses (IPv4, IPv6, or both)
• Ping Operations — Test connectivity and measure response times to hosts using ICMP
• HTTP Ping Operations — Test HTTP endpoints and measure detailed response times including DNS, connection, TLS, and TTFB timing

What the assistant can call

Once DNS And WHOIS Query is connected, these are the calls the assistant has available:

• Ping — Performs ICMP ping operations to test connectivity and measure response times to hosts

Setting it up

ghcr.io/patrickdappollonio/mcp-netutils on a container image is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. DNS And WHOIS Query's toolset — Ping — is a fair guide to whether it matches your workflow. It is maintained by patrickdappollonio; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the dns and whois query mcp server does with a few real requests.