Nmap MCP server

Which servers in the official MCP registry are Nmap's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-18

← Back to Nmap

Whose server it is

Registry namecom.portscan/port-scannerverified in the MCP registry

The registry name sits under portscan.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-18

Stateanswerschecked 2026-10-18
Tools2
Server calls itselfportscan
Server version1.0.0
Protocol version2025-06-18

On 2026-10-18 the server answered initialize and tools/list without a sign-in. First answer in 244 ms.

Tools it offers2 tools · read 2026-10-18

fast_scan
Scan the 32 most common TCP ports (~20s) of YOUR OWN public IP address - the egress IP of the machine running this MCP client. There is no target argument: by policy portscan only scans the requester's own IP. The call is non-blocking and…
deep_scan
Scan all 65535 TCP ports (~1-5 min) of YOUR OWN public IP address - the egress IP of the machine running this MCP client. There is no target argument: by policy portscan only scans the requester's own IP. The call is non-blocking and…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "port-scanner": {
      "type": "http",
      "url": "https://api.portscan.com/mcp"
    }
  }
}

OpenAPI spec

4 paths, read 2026-10-18. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.