NmapMCP MCP Server

Nmapmcp mcp server connects NmapMCP to AI assistants that speak the Model Context Protocol. NmapMCP is a robust integration of the Nmap scanning tool with the Model Context Protocol (MCP), enabling seamless network scanning capabilities within MCP-compatible environments. This project allows users to perform various network scans, such as top ports scanning, DNS brute force, and more.

What NmapMCP does

NmapMCP is a robust integration of the Nmap scanning tool with the Model Context Protocol (MCP), enabling seamless network scanning capabilities within MCP-compatible environments. This project allows users to perform various network scans, such as top ports scanning, DNS brute force, and more, directly through MCP interfaces.

Key capabilities

• Top Ports Scanning: — Quickly identify the most commonly used ports on target hosts to assess potential entry points
• DNS Brute Force: — Discover subdomains associated with a target domain, aiding in comprehensive domain mapping
• List Scan: — Obtain a list of active hosts within a specified range without port scanning, useful for network inventory
• OS Detection: — Determine the operating system of a target host by analyzing network responses, assisting in vulnerability assessment
• Version Detection: — Identify service versions running on open ports to detect outdated or vulnerable services
• FIN Scan: — Perform stealthy scans by sending FIN packets to detect open ports without establishing a full connection
• Idle Scan: — Conduct highly stealthy scans by leveraging idle hosts to probe target systems, minimizing detection risks
• Ping Scan: — Detect active hosts in a network by sending ICMP echo requests, useful for network mapping

Installing the nmapmcp mcp server

The server is distributed via npm as @smithery/cli, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. NmapMCP sits in that group. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• Maintained by 0xPratikPatil.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the nmapmcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.