Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Network scanner for AI agents: discover hosts, scan TCP and UDP ports, query DNS and mDNS.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
NETSCLI_MCP_ALLOW_PUBLIC_TARGETSYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"netscli": {
"command": "npx",
"args": [
"-y",
"netscli",
"serve"
],
"env": {
"NETSCLI_MCP_ALLOW_PUBLIC_TARGETS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add netscli --env NETSCLI_MCP_ALLOW_PUBLIC_TARGETS=your-value -- npx -y netscli serveFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"netscli": {
"command": "npx",
"args": [
"-y",
"netscli",
"serve"
],
"env": {
"NETSCLI_MCP_ALLOW_PUBLIC_TARGETS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"netscli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"netscli",
"serve"
],
"env": {
"NETSCLI_MCP_ALLOW_PUBLIC_TARGETS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
NETSCLI_MCP_ALLOW_PUBLIC_TARGETS envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account fstubner, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.3.4) reached the registry 33 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Dechonet MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
*A network scanner written in Rust. CLI, terminal UI, desktop app, and MCP server. One library behind all four.*
[Documentation](https://netscli.com/docs/) · [Install](https://netscli.com/docs/install/) · [Changelog](https://netscli.com/changelog/)
The terminal UI came first. I wanted to understand how the newer TUIs work, the ones coding agents like Claude Code have put real effort into. Autocomplete, command history, in-place progress, and a UI that does not take over the terminal, so scrollback and copying text keep working. Building one seemed like the way to learn it, and a network scanner gave it something to do.
The MCP server came next. I thought it would be interesting to let an agent work with a network that way. Ask which device just joined, or whether port 22 is open on some host, instead of shelling out to another tool and parsing output that was written for a person to read.
Then the CLI, for programmatic use. A script or a cron job wants one command and JSON back, not an interactive session.
The desktop app came last. Some people would rather have a GUI than a terminal, and honestly I sometimes prefer it myself over running the commands locally.
Three of them are the same binary. netscli is the CLI, netscli on its own opens the terminal UI, and netscli serve starts the MCP server. The desktop app is a separate download over the same core.
# macOS / Linux
brew tap fstubner/tap && brew install netscli
winget install netscli # CLI, TUI and MCP server winget install netscli-gui # desktop app
cargo install netscli
Desktop installers for Windows, macOS and Linux are attached to every release.
Scoop, the AUR, the one-line install scripts, packet-capture builds and signature verification are all covered in the [install guide](https://netscli.com/docs/install/).
netscli discover # find hosts on the local subnet
netscli scan 192.168.1.10 -p 22,80,443 netscli inspect example.com # ping + scan + resolve netscli dns example.com # all record types netscli arp # ARP table with vendor lookup netscli interfaces
Every command that returns a result takes --json or --yaml, so results pipe straight into jq, and the ones that return a list also take --csv and --md.
Run netscli with no arguments for the terminal UI: slash commands with autocomplete, command history, scrollback and /export.
Full command reference: [CLI](https://netscli.com/docs/cli/) · [TUI](https://netscli.com/docs/tui/) · [desktop app](https://netscli.com/docs/desktop/)
{
"mcpServers": { "netscli": { "command": "netscli", "args": ["serve"] } } }
That form needs netscli installed. To skip the install, use npx as the command ("command": "npx", "args": ["-y", "netscli", "serve"]), or open an .mcpb bundle from the latest release in a client that supports them.
Nine tools by default: discover, scan, ping, DNS, ARP, inspect, sweep, interfaces and mDNS. Packet-capture builds add four more. Details and the full schemas are in the [MCP guide](https://netscli.com/docs/mcp/).
| Page | Covers |
|---|---|
| Overview | What it does, the interface model, safety limits |
| Installation | Every install route, per platform |
| CLI | Commands, flags, structured output |
| Terminal UI | Slash commands and session behaviour |
| Desktop app | Tabs, filters, exports |
| MCP server | Tools, schemas, agent setup |
| Interface coverage | Which capabilities each interface exposes |
| Operations | What each scan actually does |
| Result model | Shape of the JSON and YAML output |
| Packet capture | Requirements and the pcap builds |
| Core library | Using netscli-core directly |
Issues and pull requests are welcome. Building from source, the desktop app dev loop, packet-capture builds and the repository layout are all in CONTRIBUTING.md.
MIT. See LICENSE.