netdiag-mcp
English | 日本語
MCP server for on-demand network diagnostics — DNS lookups (with a DNSSEC AD-bit check), ping, an mtr-based path report, TCP port checks, HTTP status/redirect checks, TLS certificate inspection, and WHOIS, all from one server.
Built for triaging "can't reach X" / "is DNS propagated yet" reports without shelling into a jump host for each one-off dig/ping/curl.
Tools
| Tool | Purpose |
|---|---|
dns_lookup |
Resolve a DNS record via dig (A/AAAA/MX/TXT/NS/CNAME/SOA/PTR/CAA), optionally against a specific resolver and over plain DNS/DoT/DoH |
dnssec_check |
Query a known-validating resolver and report whether the AD bit is set (plain/DoT/DoH) — the only reliable way to confirm DNSSEC validation, since an RRSIG being present in a plain dig reply does not by itself prove anything validated it |
ping_host |
ICMP ping (count clamped to 1-10) |
traceroute_path |
Hop-by-hop path/loss report via mtr --report (fixed cycles, not a live/continuous run) |
tcp_port_check |
Is a TCP port open — a plain socket connect, not a port scan |
http_check |
HEAD/GET a URL and report status, redirect chain, and latency |
tls_cert_check |
Fetch the certificate a host presents and report subject/issuer/validity/SANs |
whois_lookup |
WHOIS lookup for a domain |
asn_lookup |
ASN + country-code lookup for an IP, or org info for an AS number, via Team Cymru's whois service — no API key or GeoIP database needed |
health_check |
Version and which wrapped binaries (dig/ping/mtr/whois) are present on PATH |
All tools are read-only and single-target (no batch/sweep mode) — this is a
convenience wrapper around checks an operator would run by hand, not a
scanning tool. nmap-style multi-host/multi-port scanning is intentionally
out of scope; deliberately probing many hosts or ports is a different,
higher-blast-radius action that deserves its own tooling and approval flow.
tcp_port_check, http_check and tls_cert_check use Python's own
socket/ssl/httpx stack rather than shelling out to nc/curl/openssl, so
those three tools work even on a host with only the dig/ping/mtr/whois
binaries installed (or none of them — health_check reports which are
missing without failing the whole server).
dns_lookup/dnssec_check support DNS-over-TLS and DNS-over-HTTPS via
transport="dot"/"doh" (dig's +tls/+https). This needs dig from
BIND 9.18+ — an older dig rejects the flag outright rather than silently
falling back to plain DNS, so a stale binary fails loudly instead of giving
a false sense of having checked over an encrypted transport.
tls_cert_check/http_check against a bare IP address can fail TLS
handshake with a "handshake failure" or similar error on SNI-hosted /
CDN-fronted origins (e.g. behind Cloudflare) — TLS's SNI extension only
carries hostnames, so an IP literal can't route to the right certificate on
a shared edge. This is normal TLS behavior, not a tool bug; check by
hostname when the target is CDN-fronted.
Setup
1. System dependencies
dns_lookup, dnssec_check, ping_host, traceroute_path and
whois_lookup shell out to dig, ping, mtr and whois respectively.
Install whichever of these you want available:
# Debian/Ubuntu
sudo apt install dnsutils iputils-ping mtr-tiny whois
mtr needs raw-socket access. Debian/Ubuntu's mtr-tiny package grants
cap_net_raw to the mtr-packet helper at install time, so it normally
works for an unprivileged service user without further setup — verify with
getcap "$(command -v mtr-packet)" if traceroute_path reports a socket
permission error. Without that capability, traceroute_path fails cleanly
with a ToolError rather than crashing the server.
2. Install
pip install netdiag-mcp
# or
uv tool install netdiag-mcp
3. Claude Code (manual)
claude mcp add netdiag -- netdiag-mcp
No environment variables are required.
CLI
netdiag-mcp --version # print version
netdiag-mcp --check # report which wrapped binaries are present (exit 0 when all are)
Security notes
- Every external-binary call passes an argv list (never a shell string), so no tool argument can break out into shell syntax.
- Hostname/IP and port arguments are validated and size/range-clamped before use — tool input is model-driven and treated as untrusted, the same as any other tool-calling surface.
tcp_port_checkconnects to exactly one host:port per call; there is no loop or range argument, by design.
Development
Live smoke test
Unit tests check logic against fixtures; they cannot tell you that a tool has
stopped returning real data (a dead dig/ping/mtr/whois binary, a
broken TLS trust store, a network that blocks outbound ICMP). scripts/ smoke_test.py runs every registered tool against real public endpoints
and fails on empty, malformed or error answers:
uv run python scripts/smoke_test.py
uv run python scripts/smoke_test.py --only ping --traceback
- No inventory, so every target is a fixed public endpoint — Cloudflare's
1.1.1.1and IANA'sexample.com(reserved for documentation/testing use, RFC 2606). This server takes no config and has nothing to discover a target from, unlike a device-fleet MCP server in this family. tests/test_smoke_probes.pyis the offline half: it only checks that every registered tool has a probe spec (and vice versa), so CI catches a tool added without deciding how anyone would know it works, without needing network access.
License
MIT
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file netdiag_mcp-0.3.0.tar.gz.
File metadata
- Download URL: netdiag_mcp-0.3.0.tar.gz
- Upload date:
- Size: 18.5 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
be03f1bdc6643672493892824d504044af7b4943394d11e64d931d9a31c1da82
|
|
| MD5 |
b5af7f080cfce6de8a76127f67a01016
|
|
| BLAKE2b-256 |
af95fdac44b049c97d15d0314814dacb77022f15d3179dbb10d1804d11ff3fc1
|
Provenance
The following attestation bundles were made for netdiag_mcp-0.3.0.tar.gz:
Publisher:
release.yml on shigechika/netdiag-mcp
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
netdiag_mcp-0.3.0.tar.gz -
Subject digest:
be03f1bdc6643672493892824d504044af7b4943394d11e64d931d9a31c1da82 - Sigstore transparency entry: 2514013350
- Sigstore integration time:
-
Permalink:
shigechika/netdiag-mcp@b2e4ba64dd5575fe5cf14dbc59112cb6e0471be7 -
Branch / Tag:
refs/tags/v0.3.0 - Owner: https://github.com/shigechika
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
release.yml@b2e4ba64dd5575fe5cf14dbc59112cb6e0471be7 -
Trigger Event:
release
-
Statement type:
File details
Details for the file netdiag_mcp-0.3.0-py3-none-any.whl.
File metadata
- Download URL: netdiag_mcp-0.3.0-py3-none-any.whl
- Upload date:
- Size: 13.7 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
dd47b243e8232f330135cfcd218e22f7ffff0eea47c4c7a875eab237a27e6dd5
|
|
| MD5 |
ba7294d5bda4af3003f124da210cfc50
|
|
| BLAKE2b-256 |
b4b8f99b8903a334e75f18205d7d560c047ce3708fa4d44bb23ce8e2e37cf6be
|
Provenance
The following attestation bundles were made for netdiag_mcp-0.3.0-py3-none-any.whl:
Publisher:
release.yml on shigechika/netdiag-mcp
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
netdiag_mcp-0.3.0-py3-none-any.whl -
Subject digest:
dd47b243e8232f330135cfcd218e22f7ffff0eea47c4c7a875eab237a27e6dd5 - Sigstore transparency entry: 2514013541
- Sigstore integration time:
-
Permalink:
shigechika/netdiag-mcp@b2e4ba64dd5575fe5cf14dbc59112cb6e0471be7 -
Branch / Tag:
refs/tags/v0.3.0 - Owner: https://github.com/shigechika
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
release.yml@b2e4ba64dd5575fe5cf14dbc59112cb6e0471be7 -
Trigger Event:
release
-
Statement type: