Log inSubmit server
Netdiag MCP logo

Netdiag MCP

On-demand MCP network diagnostics for DNS, reachability, HTTP, TLS, WHOIS, ASN, and path checks.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Netdiag MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "netdiag-mcp": {
      "command": "uvx",
      "args": [
        "netdiag-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The netdiag MCP MCP server exposes on-demand network diagnostics through MCP tools for DNS, reachability, HTTP, TLS, WHOIS, ASN, and time checks. It wraps local utilities such as dig, ping, mtr, and whois, while using Python networking libraries for TCP, HTTP, and TLS operations. Use it to investigate connectivity, DNS propagation, certificate details, or routing without manually accessing a shell or jump host. Checks are read-only, single-target operations rather than batch scans.

Use cases

  • Investigate DNS propagation and DNSSEC validation
  • Check whether a host or TCP port is reachable
  • Inspect HTTP redirects, response latency, and text content
  • Review TLS certificate details for a hostname
  • Trace packet loss and identify network path problems

Key features

  • DNS record queries over plain DNS, DoT, or DoH
  • DNSSEC AD-bit validation checks
  • Ping, MTR path, and single-port TCP checks
  • HTTP status, redirect, latency, and text retrieval tools
  • TLS certificate, WHOIS, ASN, and health inspection

Tools12

What Netdiag MCP lets your agent do. Expand a tool for its parameters.

Self-reported~373 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 39d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · netdiag-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit2d agoMost recent push to the default branch.
Tools exposed12Callable tools this server registers over MCP.

How Netdiag MCP works

What netdiag MCP MCP server does

The netdiag MCP MCP server provides a collection of single-target, read-only checks for common network troubleshooting tasks. DNS tools can query A, AAAA, MX, TXT, NS, CNAME, SOA, PTR, and CAA records, use a selected resolver, and send queries over plain DNS, DNS-over-TLS, or DNS-over-HTTPS. A separate DNSSEC check examines the AD bit returned by a known-validating resolver.

Reachability tools cover ICMP ping, an mtr --report hop and packet-loss summary, and a TCP connection test for one host and port. HTTP tools report status, redirects, and latency, or retrieve a textual response body. TLS inspection returns the presented certificate's subject, issuer, validity period, and SANs. WHOIS, ASN, timezone, and service health checks round out the diagnostic set.

How it works

The server delegates DNS, ping, path, and domain WHOIS operations to dig, ping, mtr, and whois found on the process PATH. TCP, HTTP, and TLS checks use Python's socket, SSL, and HTTP client functionality instead of external nc, curl, or openssl commands. ASN lookups use Team Cymru's WHOIS service and do not require an API key or a GeoIP database.

DNS-over-TLS and DNS-over-HTTPS require BIND dig version 9.18 or newer. An older binary rejects those transport options rather than silently performing an unencrypted query. health_check reports the server version and whether the wrapped command-line programs are available.

Setup and configuration

Install the package with pip install netdiag-mcp or uv tool install netdiag-mcp. On Debian or Ubuntu, the optional command-line dependencies can be installed with dnsutils, iputils-ping, mtr-tiny, and whois. The Python-based TCP, HTTP, and TLS tools can still operate when those binaries are absent.

The netdiag MCP MCP server requires no environment variables or application configuration. Claude Code can install it through the repository's plugin marketplace, or add it manually with claude mcp add netdiag -- netdiag-mcp. The executable must be available to the process launching the MCP client. mtr may need raw-socket capability; Debian and Ubuntu's mtr-tiny package normally configures this for its helper.

Tools and capabilities

  • dns_lookup and dnssec_check inspect records and DNSSEC validation status.
  • ping_host, traceroute_path, and tcp_port_check test reachability and one port.
  • http_check follows and reports redirects; http_get returns textual bodies up to 1 MiB.
  • tls_cert_check examines the certificate presented by a host.
  • whois_lookup, asn_lookup, current_time, and health_check provide supporting context.

The netdiag MCP MCP server rejects loopback, link-local, and cloud-metadata destinations for HTTP retrieval, including redirects. Inputs are validated and range-limited, and external commands receive argument lists rather than shell strings.

Limitations and notes

There is no batch, sweep, or nmap-style multi-host or multi-port scanning. Ping counts are limited to 1–10, and the path report uses fixed mtr cycles rather than a continuous session. TLS or HTTP checks against a bare IP can fail on SNI-dependent or CDN-fronted services; use the hostname in those cases. http_get supports textual content types only and limits responses to 1 MiB.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Netdiag MCP

netdiag MCP is an MCP server that connects AI agents to local network diagnostic commands and Python networking functions. Its main tools perform DNS and DNSSEC checks, ping, MTR path reports, TCP port tests, HTTP and TLS checks, WHOIS, ASN lookups, time checks, and health reporting for troubleshooting individual targets.

Install it with `pip install netdiag-mcp` or `uv tool install netdiag-mcp`. Optional system packages provide `dig`, `ping`, `mtr`, and `whois`; TCP, HTTP, and TLS checks do not depend on those binaries. No environment variables are required.

Yes, netdiag MCP works with Claude Code through its plugin marketplace or a manual MCP registration. Use `/plugin marketplace add shigechika/netdiag-mcp` followed by the plugin install command, or run `claude mcp add netdiag -- netdiag-mcp`.

No, netdiag MCP does not perform batch or sweep scans. `tcp_port_check` connects to exactly one host and port per call, and the other diagnostic operations are also single-target. Nmap-style multi-host or multi-port probing is intentionally outside the server's scope.

A TLS check against an IP can fail when the service depends on SNI, as with many CDN-fronted origins. TLS SNI carries hostnames, so an IP literal may not select the expected certificate. Use the service hostname instead of its address for that case.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNetdiag MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/netdiag-mcp?style=directory)](https://allmcps.com/mcp/netdiag-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/netdiag-mcp"><img src="https://allmcps.com/api/badge/netdiag-mcp?style=directory" alt="Netdiag MCP on AllMCPs" /></a>