by shigechika
NetDiag MCP is an MCP server that runs network diagnostics on request: DNS, ping, path reports, port checks, HTTP and TLS checks, and WHOIS. It helps triage reports like "can't reach X" without opening a shell on a jump host.
PluginContact for pricing
Step 1: Install the server with pip install netdiag-mcp or uv tool install netdiag-mcp.
Step 2: Install the system tools you want: dig, ping, mtr and whois (for example dnsutils, iputils-ping, mtr-tiny and whois on Debian or Ubuntu).
Step 3: In Claude Code, run claude mcp add netdiag -- netdiag-mcp, or install it as a plugin with /plugin marketplace add shigechika/netdiag-mcp.
Step 4: In Codex, run codex mcp add netdiag -- netdiag-mcp. Other stdio MCP clients can use netdiag-mcp as the command.
Step 5: Run netdiag-mcp --check to see which binaries are missing, then ask your assistant to check DNS, a port or a certificate.
No. Each tool targets a single host, and tcp_port_check connects to exactly one host and port per call. Scanning many hosts or ports is intentionally out of scope.
Only for the tools that wrap them: DNS, ping, path report and WHOIS. The TCP, HTTP and TLS checks work without them.
Yes. dns_lookup and dnssec_check support DNS-over-TLS and DNS-over-HTTPS, which needs a recent dig from BIND 9.18 or later.
No pricing is stated. It is open source under the MIT license.
Requirements
DeviceShelf MCPDeviceShelf MCP lets an AI assistant answer questions about your network from the live inventory and monitoring data in your own DeviceShelf Server. It is local, read-only by default and off until you enable it.Stamp MCPStamp is an MCP server of small tools agents use often: NTP time and clock drift, UUIDs, diffs, safe arithmetic, and tamper-evident attestation. It runs locally over stdio or as a hosted public endpoint.
Q-Ring MCPq-ring stores API keys and other secrets in your operating system's native keychain and exposes them to AI coding agents over MCP. It also ships a command-line tool for managing the same secrets.