MCP.so
ログイン

DNS and WHOIS query MCP server

@patrickdappollonio

DNS and WHOIS query MCP server について

Perform DNS lookups, WHOIS queries, connectivity testing, TLS certificate analysis, HTTP endpoint monitoring, and hostname resolution, all from your trusty AI.

基本情報

カテゴリ

その他

ライセンス

MIT

ランタイム

go

トランスポート

stdio

公開者

patrickdappollonio

投稿者

Patrick D'appollonio

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "dns": {
      "command": "mcp-domaintools",
      "args": [],
      "env": {}
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is DNS and WHOIS query MCP server?

mcp-netutils is a Model Context Protocol (MCP) server that provides 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. It uses local OS‑configured DNS servers for local queries and Cloudflare/Google DNS‑over‑HTTPS for remote queries, with optional custom DNS and WHOIS servers.

How to use DNS and WHOIS query MCP server?

Install via Homebrew (brew install patrickdappollonio/tap/mcp-netutils), Docker (ghcr.io/patrickdappollonio/mcp-netutils:latest), or download a pre‑built binary from the GitHub releases page. Configure it in your editor’s MCP settings with the command mcp-netutils (or a Docker run command) and optional flags such as --remote-server-address, --custom-whois-server, or timeouts. The server exposes 7 tools: local_dns_query, remote_dns_query, whois_query, resolve_hostname, ping, http_ping, and tls_certificate_check.

Key features of DNS and WHOIS query MCP server

  • Local DNS queries using OS‑configured DNS servers
  • Remote DNS‑over‑HTTPS queries via Cloudflare and Google
  • WHOIS lookups for domain registration information
  • Hostname resolution to IPv4, IPv6, or both
  • ICMP ping operations with configurable count and timeout
  • HTTP ping with detailed timing (DNS, TLS, TTFB, total)
  • TLS certificate chain analysis with expiry checks

Use cases of DNS and WHOIS query MCP server

  • Debug DNS resolution issues with local or remote resolvers
  • Retrieve domain registration data for security investigations
  • Monitor HTTP endpoint availability and response times
  • Verify TLS certificate validity and expiration dates
  • Test network connectivity and latency to hosts

FAQ from DNS and WHOIS query MCP server

What DNS servers are used for local versus remote queries?

Local queries use the system’s configured DNS servers. Remote queries use Cloudflare DNS‑over‑HTTPS with a fallback to Google DNS‑over‑HTTPS.

Can I use a custom DNS‑over‑HTTPS or WHOIS server?

Yes. Use the --remote-server-address flag for a custom DoH server (must implement RFC 8484) and --custom-whois-server for a custom WHOIS server (RFC 3912 or plain text responses).

How do I run the server in SSE mode?

Add the --sse flag and optionally --sse-port (default 3000). The server then listens on HTTP and communicates via Server‑Sent Events.

What record types are supported for DNS queries?

Supported types: A, AAAA, CNAME, MX, NS, PTR, SOA, SRV, and TXT.

Is Docker required to use this server?

No. You can install and run the binary directly via Homebrew or GitHub releases. Docker is an alternative deployment method.

コメント

「その他」の他のコンテンツ