patrickdappollonio/mcp-netutils
Deployment & DevOps이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기
Perform DNS lookups, WHOIS queries, connectivity testing, TLS certificate analysis, HTTP endpoint monitoring, and hostname resolution, all from your trusty AI.
개요
This project is now called mcp-netutils. If you're upgrading, please update your references: - : ghcr.io/patrickdappollonio/mcp-netutils:latest - : patrickdappollonio/tap/mcp-netutils - : Use "netutils" in your MCP server configuration For more details about this change, see issue #52. For local DNS queries, it uses the system's configured DNS servers. For remote DNS queries, it uses Cloudflare DNS-over-HTTPS queries with a fallback to Google DNS-over-HTTPS. This is more than enough for most use cases. For custom DNS-over-HTTPS servers, you can use the --remote-server-address flag. The server endpoint must implement the HTTP response format as defined by RFC 8484. For custom WHOIS servers, you can use the --custom-whois-server flag. The server endpoint must implement the HTTP response format as defined by RFC 3912, although plain text responses are also supported.
README
원문 README의 일부입니다. 원문 보기.
Network and domain utils MCP server mcp-netutils
[!IMPORTANT]
This project is now called
mcp-netutils. If you’re upgrading, please update your references:
- Docker images:
ghcr.io/patrickdappollonio/mcp-netutils:latest- Homebrew:
patrickdappollonio/tap/mcp-netutils- Configuration key: Use
"netutils"in your MCP server configurationFor more details about this change, see issue #52.
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.
For local DNS queries, it uses the system’s configured DNS servers. For remote DNS queries, it uses Cloudflare DNS-over-HTTPS queries with a fallback to Google DNS-over-HTTPS. This is more than enough for most use cases.
For custom DNS-over-HTTPS servers, you can use the --remote-server-address flag. The server endpoint must implement the HTTP response format as defined by RFC 8484.
For custom WHOIS servers, you can use the --custom-whois-server flag. The server endpoint must implement the HTTP response format as defined by RFC 3912, although plain text responses are also supported.
Features
- 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
- TLS Certificate Analysis: Check TLS certificate chains for validity, expiration, and detailed certificate information
- Multiple Record Types: Support for A, AAAA, CNAME, MX, NS, PTR, SOA, SRV, and TXT record types
- Fallback Mechanism: Automatically tries multiple DNS servers for reliable results
- SSE Support: Run as an HTTP server with Server-Sent Events (SSE) for web-based integrations
Installation
설치
docker run -i --rm ghcr.io/patrickdappollonio/mcp-netutils:latest // Add custom options if needed:
// "--remote-server-address=https://your-custom-doh-server.com/dns-query // "--custom-whois-server=whois.yourdomain.com // "--timeout=5s // "--ping-timeout=5s // "--ping-count=4 // "--http-ping-timeout=10s // "--http-ping-count=1 // "--tls-timeout=10s설정
{
"mcpServers": {
"netutils": {
"command": "mcp-netutils",
"args": [
// Uncomment and modify as needed:
// "--remote-server-address=https://your-custom-doh-server.com/dns-query",
// "--custom-whois-server=whois.yourdomain.com",
// "--timeout=5s",
// "--ping-timeout=5s",
// "--ping-count=4",
// "--http-ping-timeout=10s",
// "--http-ping-count=1",
// "--tls-timeout=10s"
],
"env": {}
}
}
}