MCP.Market

netdiag MCP server

by shigechika·io.github.shigechika/netdiag-mcp·v0.8.1

MCP server wrapping dig, ping, mtr, whois and TLS/HTTP checks for on-demand network diagnostics

A85/100grade A
What users say
No reviews yet
Be the first
Safety scan
A85/100

not scanned yet

Adoption
Growing

0 stars154 downloads/wk

Reviews

Write one

Nobody has reviewed netdiag MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

netdiag MCP tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How netdiag MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,255 servers
Downloads a week
154
more than 71% of 12,191 servers with a package

Release history: 4 versions in the registry since 2026-09-16, latest 2026-10-26, typically one every 13 days.

Install netdiag MCP in Claude Code, Cursor or VS Code

claude mcp add netdiag-mcp -- uvx netdiag-mcp
Add to Cursor

What the publisher says

From the netdiag MCP repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.shigechika/netdiag-mcp -->

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

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.

tcpportcheck, httpcheck, httpget and tlscertcheck use Python's own socket/ssl/httpx stack rather than shelling out to nc/curl/openssl, so those four 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).

dnslookup/dnsseccheck 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.

tlscertcheck/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

dnslookup, dnsseccheck, pinghost, traceroutepath 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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

netdiag MCP: common questions

Is netdiag MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the netdiag MCP safety report
How do I install netdiag MCP?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does netdiag MCP need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is netdiag MCP maintained?
The last commit was 33 days ago (2026-10-02). The latest release is v0.8.1.
What can I use instead of netdiag MCP?
Servers from other publishers that do the same job: Domain Liveness MCP server.
How does netdiag MCP compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,255 servers); downloads a week 154 (more than 71% of 12,191 servers with a package). Full comparison.

Alternatives to netdiag MCP

Same job from other publishers: the closest match first, then the best rated.

  • Domain Liveness
    Is this business's website still there? Checks apex and www, and DNS separately from HTTP.
    A

More from shigechika →