NetsCLI
NPM · NETSCLI
Network scanner for AI agents: discover hosts, scan TCP and UDP ports, query DNS and mDNS.
Available components
Last scanned (23 hours ago)
Scores higher than 97% 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 5 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to fstubner/netscli). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 31 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 795 tokens (~88/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 37% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 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 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 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.
- 19 Oct 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.
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 4 Nov 2026 · Analysed npm/netscli@0.3.4
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | fstubner/netscli |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/fstubner/netscli/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3076197535 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3a4e1643fbc81337a69725aa4c2e33ac8b2d96f3f78e2de01002403379f63d0d9bb352bd7d34ceb06773550d9cfbf37ae6f1273fdf6fe1977e2c7a021 |
Background: How many MCP packages publish verified provenance →
Dependencies 5 packages
| Packages resolved | 5 |
|---|---|
| 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 →
discover_mdns ~139
Discover devices on the local network via mDNS/DNS-SD (Bonjour). Returns services with their hostnames, resolved IPs, ports, and TXT properties. Much friendlier than IP-based discovery for named devices like printers, Chromecasts, or Homebridge accessories.
| Name | Type | Req | Description |
|---|---|---|---|
| service_types | array | – | Explicit service types to browse (e.g. ["_http._tcp.local.", "_airplay._tcp.local."]). Omit to use a curated default set. |
| timeout_ms | number | – | How long to browse for responses. 3000-5000ms is typical; many devices re-announce on a multi-second cadence. |
No output schema declared.
No examples provided.
discover_network ~90
Discover live hosts on a network subnet
| Name | Type | Req | Description |
|---|---|---|---|
| maxConcurrent | number | – | – |
| resolveHostnames | boolean | – | – |
| subnet | string | – | IPv4 CIDR, at most a /16. Defaults to the local subnet. |
| timeout | number | – | Milliseconds, applied to every step. Omit for the defaults: ping 1000, scan 500, DNS 1500. |
No output schema declared.
No examples provided.
dns_lookup ~72
DNS lookup (A, AAAA, CNAME, MX, NS, TXT, SRV, PTR, SOA, CAA, or ALL/ANY for every record type)
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | – |
| type | string | – | Record type. Omit, or pass ALL, for every type. |
No output schema declared.
No examples provided.
get_arp_table ~20
Get ARP/neighbor table with vendor information
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
inspect_host ~162
Inspect a host: ping, port scan, reverse DNS, MAC vendor on the local segment, and an OS hint (family, detail and the evidence behind it, from SMB, SSH/HTTP banners, open ports, MAC vendor and ping TTL). The hint is a guess, not a fingerprint. ports lists only open, open|filtered and errored ports unless include_closed is true.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | – |
| include_closed | boolean | – | Also list closed and filtered ports in ports, one entry each. |
| maxConcurrent | number | – | – |
| ports | array | – | – |
| timeout | number | – | Milliseconds, applied to every step. Omit for the defaults: ping 1000, scan 500, DNS 1500. |
No output schema declared.
No examples provided.
list_network_interfaces ~15
List network interfaces with details
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ping_host ~59
Ping a host (ICMP with TCP-connect fallback). Returns a PingSummary with aggregate loss and min/avg/max RTT when count > 1.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | – |
| host | string | yes | – |
| timeout | number | – | – |
No output schema declared.
No examples provided.
scan_ports ~139
Scan TCP ports on a host, or UDP ports with udp: true. UDP without ports probes DNS, NTP, NetBIOS, SSDP and mDNS; a UDP port that neither replies nor refuses is open|filtered. Returns only open, open|filtered and errored ports unless include_closed is true, so an empty list means every port scanned was closed or filtered.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | – |
| include_closed | boolean | – | Also return closed and filtered ports, one entry each. |
| maxConcurrent | number | – | – |
| ports | array | – | – |
| timeout | number | – | – |
| udp | boolean | – | – |
No output schema declared.
No examples provided.
sweep_network ~99
Sweep a network (discover hosts then scan ports)
| Name | Type | Req | Description |
|---|---|---|---|
| maxConcurrent | number | – | – |
| ports | array | – | – |
| resolveHostnames | boolean | – | – |
| subnet | string | – | IPv4 CIDR, at most a /16. Defaults to the local subnet. |
| timeout | number | – | Milliseconds, applied to every step. Omit for the defaults: ping 1000, scan 500, DNS 1500. |
No output schema declared.
No examples provided.
How do I install the NetsCLI MCP server?
NetsCLI runs locally as an npm package, launched with npx -y netscli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · netscli
claude mcp add fstubner-netscli -- npx -y netscli
What is the NetsCLI MCP server?
NetsCLI is an MCP server listed in the public MCP registry as io.github.fstubner/netscli. Network scanner for AI agents: discover hosts, scan TCP and UDP ports, query DNS and mDNS. This page covers its npm package (netscli).
Is the NetsCLI MCP server safe to use?
NetsCLI scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. 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 NetsCLI MCP server expose?
NetsCLI exposes 9 tools: discover_network, scan_ports, ping_host, dns_lookup, get_arp_table, and 4 more. Their descriptions and schemas cost roughly 795 tokens of context every time the server is loaded.
Is the NetsCLI MCP server still maintained?
NetsCLI is still listed as active in the MCP registry. We last reached this channel on 4 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 NetsCLI MCP server under?
NetsCLI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.