MCP server wrapping dig, ping, mtr, whois and TLS/HTTP checks for on-demand network diagnostics
- capability exposure inferred + 22
- tool safety inferred + 7
- trust mitigators mixed − 17
inferred mixed
The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.
grade last moved 6d ago · see ecosystem CVEs →
- B · 20 → A · 12
No known CVEs for this server.
- medium toxic flow (lethal trifecta)
lethal trifecta reachable across connected servers: this server can exfiltrate (network) while a connected dependency supplies private-data access / untrusted-content ingestion
- low exfiltration combo
sensitive read and network capabilities split across this server's tools
analyzed v0.6.0 · analyzer v33 · 1d ago
danger signals1
- suspicious endpoint 169.254.169.254 (cloud metadata) netdiag_mcp-0.6.0/tests/test_tools.py :264
tools.http_get("http://169.254.169.254/latest/meta-data/")
[](https://mcpobservatory.com/servers/pypi:netdiag-mcp/security) Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of AIKAWA Shigechika.