netdiag MCP
PYPI · NETDIAG-MCP
MCP server wrapping dig, ping, mtr, whois and TLS/HTTP checks for on-demand network diagnostics
Available components
Last scanned (4 hours ago)
Scores higher than 91% of PyPI servers
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to shigechika/netdiag-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 859 tokens (~71/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (83% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −20
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.70 functional
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 28 Oct 26 0
- Package version: 0.8.0 → 0.8.1 functional
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.8.0 → 0.8.1 functional
- 23 Oct 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/netdiag-mcp@0.8.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | shigechika/netdiag-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/shigechika/netdiag-mcp/.github/workflows/release.yml@refs/tags/v0.8.1 |
| Rekor log index | 3478659100 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:04cdd91b7a37b7183bf83aa6130000624e7915f5c4d46e9b91d04a96992ef045 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
asn_lookup ~87
ASN + country-code lookup for an IP, or org info for an AS number (e.g. AS15169 or 15169). Via Team Cymru's whois service — no API key or GeoIP database needed. Takes an IP literal or AS number, not a hostname; resolve first with dns_lookup if you only have a name.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
current_time ~95
Current date, time and weekday in an IANA timezone (e.g. "Asia/Tokyo"). Call this rather than deriving the weekday from a date yourself — that is calendar arithmetic and it fails silently. Returns the date, the 24h time, the weekday in English and Japanese, the offset, UTC and the epoch, so it also serves as a clock check on this server.
| Name | Type | Req | Description |
|---|---|---|---|
| timezone | string | – | – |
No output schema declared.
No examples provided.
dns_lookup ~162
Resolve a DNS record via `dig`. record_type: A/AAAA/MX/TXT/NS/CNAME/SOA/PTR/CAA. Pass resolver to query a specific nameserver instead of the host default (e.g. to check whether a change has propagated to a given resolver). transport: "plain" (UDP/TCP 53, default), "dot" (DNS-over-TLS, 853) or "doh" (DNS-over-HTTPS, 443). Requires dig from BIND 9.18+; an older dig rejects dot/doh outright instead of silently querying over plain DNS.
| Name | Type | Req | Description |
|---|---|---|---|
| hostname | string | yes | – |
| record_type | string | – | – |
| resolver | – | – | – |
| transport | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
dnssec_check ~83
Check whether a name validates DNSSEC against a known-validating resolver (AD bit). transport: "plain" (default), "dot" or "doh" — compare validation over plain DNS vs. an encrypted transport when port 53 may be intercepted.
| Name | Type | Req | Description |
|---|---|---|---|
| hostname | string | yes | – |
| resolver | string | – | – |
| transport | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
health_check ~106
Service health: version, which wrapped binaries are present on PATH, and the http_get auth prefixes. Returns a fixed shape (status/service/version + backend fields) so a monitoring caller never has to branch on missing keys. status is "healthy" when every wrapped binary is found and NETDIAG_HTTP_AUTH (if set) parses, "degraded" otherwise (the affected tools fail at call time). http_auth lists the configured URL prefixes, never the header values.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
http_check ~36
HEAD/GET a URL and report status, redirect chain and latency.
| Name | Type | Req | Description |
|---|---|---|---|
| timeout | number | – | – |
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
http_get ~83
GET a URL and return the response body (text/JSON/XML only, capped at max_bytes, hard cap 1 MiB). Use this to read a JSON endpoint or inspect an error page. For status/latency only, use http_check instead.
| Name | Type | Req | Description |
|---|---|---|---|
| max_bytes | integer | – | – |
| timeout | number | – | – |
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ping_host ~40
ICMP ping a host or IP. count is clamped to 1-10.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| host | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
tcp_port_check ~46
Check whether a TCP port is open (plain socket connect, no port scanning).
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | – |
| port | integer | yes | – |
| timeout | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
tls_cert_check ~44
Fetch the TLS certificate presented on host:port and report subject/issuer/validity/SANs.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | – |
| port | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
traceroute_path ~54
Path/MTU-style hop report via `mtr --report` (fixed cycles, not a live run). cycles clamped 1-10.
| Name | Type | Req | Description |
|---|---|---|---|
| cycles | integer | – | – |
| host | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
whois_lookup ~23
WHOIS lookup for a domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the netdiag MCP server?
netdiag MCP runs locally as a PyPI package, launched with uvx netdiag-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · netdiag-mcp
claude mcp add shigechika-netdiag-mcp -- uvx netdiag-mcp
What is the netdiag MCP server?
netdiag MCP is listed in the public MCP registry as io.github.shigechika/netdiag-mcp. MCP server wrapping dig, ping, mtr, whois and TLS/HTTP checks for on-demand network diagnostics. This page covers its PyPI package (netdiag-mcp).
Is the netdiag MCP server safe to use?
netdiag MCP scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the netdiag MCP server expose?
netdiag MCP exposes 12 tools: health_check, dns_lookup, dnssec_check, ping_host, traceroute_path, and 7 more. Their descriptions and schemas cost roughly 859 tokens of context every time the server is loaded.
Is the netdiag MCP server still maintained?
netdiag MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the netdiag MCP server under?
netdiag MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the netdiag MCP server?
VerifyMCP ran 16 checks on netdiag MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.