netdiag MCP

PYPI · NETDIAG-MCP · SCANNED AUG 20

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

Available components

63 63 Trust /100

Trust breakdown (6 categories)

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 →

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 native-build step with no shell scripting around it. View diagnostics → Pass
1 of 30 dependencies flagged as unhealthy. View diagnostics → Partial

Provenance & Transparency32

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
License check failed: no license is declared. See how to fix → Fail
Actively maintained (last published 0 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 656 tokens (~65/item across 10 items; 10 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management3

Stability observed for 1 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 (90% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

pypi · netdiag-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add shigechika-netdiag-mcp -- uvx netdiag-mcp

# add to Codex CLI

codex mcp add shigechika-netdiag-mcp -- uvx netdiag-mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shigechika-netdiag-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "netdiag-mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add shigechika-netdiag-mcp --command uvx --arg netdiag-mcp

# ~/.hermes/config.yaml

mcp_servers:
  shigechika-netdiag-mcp:
    command: "uvx"
    args: ["netdiag-mcp"]

// mcp.json

{
  "mcpServers": {
    "shigechika-netdiag-mcp": {
      "command": "uvx",
      "args": [
        "netdiag-mcp"
      ]
    }
  }
}

Changelog

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.

20 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.3.0 → 0.4.0 functional
19 Aug 26 62

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

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 20 Aug 2026 · Analysed pypi/netdiag-mcp@0.4.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result	No attestation
Ecosystem	pypi

Install scripts 1 script

Hook	Tier	Command
build_backend	allowlisted	`setuptools.build_meta`

Dependencies 30 packages

Packages resolved	30
Stale	1
Tree resolution	Complete

MCP tools · 10 exposed · ~656 tokens

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.

Tool Tokens

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.

Input Output Examples

Name	Type	Req	Description
target	string	yes	–

Name	Type	Req	Description
result	string	yes	–

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.

Input Output Examples

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.

Input Output Examples

Name	Type	Req	Description
hostname	string	yes	–
resolver	string	–	–
transport	string	–	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

health_check ~81

Service health: version and which wrapped binaries are present on PATH. 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, "degraded" when at least one is missing (the corresponding tools will fail at call time).

Input Output Examples

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.

Input Output Examples

Name	Type	Req	Description
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.

Input Output Examples

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).

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	–

Name	Type	Req	Description
result	string	yes	–

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

19 Aug 20 Aug