mcpbeat

Port Scanner API MCP Server

com.portscan/port-scanner
answering

Port Scanner API is answering right now. Last checked 1 min ago. It exposes 2 tools.

Scan the open TCP ports of your own public IP. Fast (32) or deep (65535). No key, no signup.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
92 of 92 checks
2
Tools
read from the server
184 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add port-scanner --transport http https://api.portscan.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "port-scanner": {
      "url": "https://api.portscan.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.port-scanner]
url = "https://api.portscan.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "port-scanner": {
      "url": "https://api.portscan.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "port-scanner": {
      "url": "https://api.portscan.com/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

deep
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 keyed by your IP: it starts a scan if none is running, otherwise returns the current state. Call deep_scan repeatedly to poll until status is "complete" (or "incomplete"/"failed"); open ports and service banners are in the result. Pass rescan:true to force a fresh scan when a previous result already exists.
fast
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 keyed by your IP: it starts a scan if none is running, otherwise returns the current state. Call fast_scan repeatedly to poll until status is "complete" (or "incomplete"/"failed"); open ports and service banners are in the result. Pass rescan:true to force a fresh scan when a previous result already exists.

Endpoints

URLTransportStateLatencyChecked
https://api.portscan.com/mcp streamable-http answering 223 ms 1 min ago

Port Scanner API — questions

Answers built from our own checks of this server.

What can Port Scanner API do?
It exposes 2 tools, read directly from the server on our last check. Among them: deep_scan, fast_scan. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Port Scanner API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 184 ms. The bar chart above shows every period we have measured.
How do I connect Port Scanner API?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Port Scanner API need an API key?
No. Port Scanner API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Port Scanner API?
It answers our handshake in 184 ms on average, which is faster than 66% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.