Scan TCP ports on remote hosts and get back open/closed status without spinning up nmap yourself. This is a remote SSE server hosted at klymax402.com that wraps port scanning functionality behind an x402 micropayment requirement, so you'll need to handle the payment flow to use it. The GitHub repo is sparse on implementation details, but the premise is straightforward: point it at a host, specify your port range, and let it probe what's listening. Reach for this when you need programmatic port discovery in a Claude workflow and don't want to manage local scanning tools or deal with firewall complications on your own infrastructure.
Public tool metadata for what this MCP can expose to an agent.
network_scan_portsUse this when you need to check which TCP ports are open on a host. Returns port status and response times in JSON. Returns: 1. host scanned 2. ports array with port number, status (open/closed/filte2 paramsUse this when you need to check which TCP ports are open on a host. Returns port status and response times in JSON. Returns: 1. host scanned 2. ports array with port number, status (open/closed/filte
hoststringportsarrayScan TCP ports on any host -- check open/closed status, response time. 16 common ports by default. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"port-scanner": {
"url": "https://port-scanner.api.klymax402.com/mcp"
}
}
}
curl -X POST "https://port-scanner.api.klymax402.com/api/scan" \
-H "Content-Type: application/json" \
-d '{"host":"..."}'
# -> 402 Payment Required, with an x402 payment challenge in the response body
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
network_scan_ports | POST | /api/scan | $0.003 | Scan common ports on a host to check which are open |
network_scan_portsUse this when you need to check which TCP ports are open on a host. Returns port status and response times in JSON.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
host | string | yes | The hostname or IP address to scan |
ports | array | no | Array of port numbers to scan (default: [21,22,25,53,80,110,143,443,993,995,3306,3389,5432,6379,8080,8443]) |
Example response:
{"host":"example.com","ports":[{"port":80,"status":"open","responseTime":45},{"port":443,"status":"open","responseTime":52},{"port":22,"status":"closed","responseTime":null}],"openCount":2,"totalScanned":16,"scanDuration":1200}
When to use: server reconnaissance, verifying firewall rules, checking service availability, and infrastructure auditing.
Not for: DNS resolution (use network_lookup_dns), SSL certificate checks (use security_check_ssl), HTTP header analysis (use network_analyze_headers).
eip155:8453)100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
MIT