run_nmap_scanLABSCO SUMMARY
Read the warning at the top of the repository before you install this one.
The author's own first line is that you should not use it unless you accept the exposure that comes from prompt injection, and that the project is not maintained — which is exactly the right framing for a tool that hands network scanning to a model reading untrusted text. If you do run it, scope it: name the target explicitly, keep the timing template modest, and treat every scan as something you authorised rather than something the model decided to do.
What it is
A Node MCP server that wraps NMAP's own command-line interface, so scans behave exactly as they would from a terminal, and exposes them to an AI client as a single parameterised function.
What you get
run_nmap_scan— takes a target host or network and returns NMAP's output- Three scan types: quick, full port scan, and version detection
- Port specification, either as a list or a range
- NMAP timing templates 0 through 5, defaulting to 3
- A pass-through for any additional NMAP flags you need
Requirements
Windows, with NMAP installed and callable from the command line, and Node.js v18 or higher. Install mcp-nmap-server globally or locally, then point your client's config at the built entry point. The repository states plainly that it is not being actively worked on, and that exposing a scanner to a model carries prompt-injection risk.
Setup effort
One command — npm install -g mcp-nmap-server
USE CASES
01
Checking what is listening on a machine you own
Run a quick scan against the host by name and read the open ports back in the conversation.
02
Identifying service versions on a specific port range
Set the scan type to version detection and give the port range explicitly.
03
Keeping a scan gentle on a shared network
Lower the timing template rather than accepting the default pace.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- Windows
- Node.js v18 or higher
- NMAP installed and on the Windows command line
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g mcp-nmap-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"nmap": {
"command": "node",
"args": [
"C:\\Users\\<YOUR_USERNAME>\\Downloads\\mcp-nmap-server\\dist\\index.js"
]
}
}
}The args path is the README's example. After npm install -g, point it at the installed package instead: run npm root -g and use the mcp-nmap-server\dist\index.js file inside the folder it prints.
