io.github.Omodaka9375/netexpert-mcp
NPM · NETEXPERT-MCP
Cross-platform local-network diagnostics & security-posture MCP server — 31 tools.
Available components
Last scanned (12 hours ago)
Scores higher than 35% of npm servers
Category Security
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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 39 of 106 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 991 tokens (~31/item across 31 items; 31 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 31 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 31 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
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 npm/netexpert-mcp@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 106 packages
| Packages resolved | 106 |
|---|---|
| Stale | 39 |
| 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 →
dns.hijackcheck ~29
Killer check: known-good domains via system resolver vs trusted DoH; mismatch ⇒ Finding.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dns.lookup ~52
A/AAAA/CNAME/MX/TXT/NS/SRV/PTR lookup, optional nameserver override.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| nameserver | string | – | – |
| record | string | – | – |
No output schema declared.
No examples provided.
dns.propagation ~38
Same record queried at trusted resolvers + DoH; diff table.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| record | string | – | – |
No output schema declared.
No examples provided.
dns.resolvers ~18
Which DNS resolvers the OS actually uses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dns.reverse ~14
PTR names for an IP.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lan.arp ~21
ARP/neighbor cache, parsed, stale entries filtered.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lan.devices ~31
Inventory: ARP ∪ RFC1918 filter, enriched with vendor (OUI) + hostname (PTR).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lan.gateway ~18
Default gateway + interface + local subnet CIDR.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lan.hostname ~30
All known names for an IP: PTR, NetBIOS (win).
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | – |
No output schema declared.
No examples provided.
lan.interfaces ~25
Network interfaces (Nic[]): name, mac, ipv4[], ipv6[], type.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lan.newdevices ~30
Diff live devices vs latest snapshot ⇒ Finding[] (new MAC, MAC change). First run saves baseline.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lan.snapshot ~28
Save current lan.devices to a dated snapshot; or list snapshots.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | – |
No output schema declared.
No examples provided.
lan.sweep ~35
Ping-probe an RFC1918 subnet (cap 1024 hosts) → live set.
| Name | Type | Req | Description |
|---|---|---|---|
| subnet | string | – | – |
No output schema declared.
No examples provided.
lan.wol ~57
Wake-on-LAN magic packet (UDP broadcast). Mutating: dry-run returns confirmToken; re-call with token to execute.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmToken | string | – | – |
| mac | string | yes | – |
| port | integer | – | – |
No output schema declared.
No examples provided.
net.deepscan ~62
Optional nmap deep scan (LAN RFC1918 targets). Requires nmap on PATH AND nmap.enabled=true in config. Opt-in by design.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | – |
| ports | string | – | – |
| topPorts | integer | – | – |
No output schema declared.
No examples provided.
net.health ~19
Server version, platform, capability matrix, config caps.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
net.httpcheck ~55
GET/HEAD with timing split (dns/connect/ttfb/total), status, headers, size. LAN-safe.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | – |
| timeoutMs | integer | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
net.ping ~48
ICMP ping (min/avg/max/mdev), TCP-connect fallback reported honestly.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| host | string | yes | – |
| timeoutMs | integer | – | – |
No output schema declared.
No examples provided.
net.portcheck ~33
Single TCP connect: open/closed + latency.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | – |
| port | integer | yes | – |
No output schema declared.
No examples provided.
net.portscan ~38
Bounded TCP connect scan, default top common ports, cap 256.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | – |
| ports | array | – | – |
No output schema declared.
No examples provided.
net.publicip ~24
Public IPv4 (+ASN/org). Explicitly user-requested external call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
net.ssl ~48
TLS cert inspection: subject, SANs, issuer, expiry, daysLeft, grade.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | – |
| port | integer | – | – |
| timeoutMs | integer | – | – |
No output schema declared.
No examples provided.
net.trace ~44
Traceroute hop list (ttl, ip, latency).
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | – |
| maxHops | integer | – | – |
| timeoutMs | integer | – | – |
No output schema declared.
No examples provided.
sec.connections ~15
Active sockets with owning PID/process.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sec.exposure ~25
Composite security report: exposed listeners × firewall state × risky ports ⇒ Finding[].
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sec.firewall ~25
Firewall profile state per platform (win profiles / ufw / socketfilterfw).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sec.listening ~20
Listening ports per process; flags non-loopback exposures.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sec.speedtest ~28
Bounded download speed test (Cloudflare default, configurable). Rate-limited 1/min.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wifi.health ~25
WiFi interpretation: RSSI bands, channel overlap, band mismatch ⇒ Finding[].
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wifi.networks ~25
Nearby AP survey: SSID, BSSID, band, channel, security.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wifi.status ~31
Current WiFi link: SSID, BSSID, band, channel, RSSI, PHY rate, quality.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.Omodaka9375/netexpert-mcp server?
io.github.Omodaka9375/netexpert-mcp runs locally as an npm package, launched with npx -y netexpert-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · netexpert-mcp
claude mcp add omodaka9375-netexpert-mcp -- npx -y netexpert-mcp
What is the io.github.Omodaka9375/netexpert-mcp server?
io.github.Omodaka9375/netexpert-mcp is listed in the public MCP registry as io.github.Omodaka9375/netexpert-mcp. Cross-platform local-network diagnostics & security-posture MCP server, 31 tools. This page covers its npm package (netexpert-mcp).
Is the io.github.Omodaka9375/netexpert-mcp server safe to use?
io.github.Omodaka9375/netexpert-mcp scores 67 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.Omodaka9375/netexpert-mcp server expose?
io.github.Omodaka9375/netexpert-mcp exposes 31 tools: net.health, net.ping, net.trace, net.httpcheck, net.portcheck, and 26 more. Their descriptions and schemas cost roughly 991 tokens of context every time the server is loaded.
Is the io.github.Omodaka9375/netexpert-mcp server still maintained?
io.github.Omodaka9375/netexpert-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 io.github.Omodaka9375/netexpert-mcp server under?
io.github.Omodaka9375/netexpert-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.