
Port Scanner API
io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 24, 2026
TCP port scanning — check open ports on any host. x402 micropayment.
The publisher's own server: Port
Overview
A remote MCP server that scans TCP ports on a host and returns open/closed status and response times, paid per call via x402 micropayments.
- What you can do
- Scan TCP ports on a hostname or IP address, choosing a custom port list or the 16 common defaults (21, 22, 25, 53, 80, 110, 143, 443, 993, 995, 3306, 3389, 5432, 6379, 8080, 8443). Get back JSON with each port's status, response time, open count, total scanned and scan duration. Use results for server reconnaissance, firewall verification, service availability checks and infrastructure auditing.
- When to use it
- When an assistant needs to check which TCP ports are open on a host, confirm firewall rules, verify that a service is reachable, or do light infrastructure auditing. Not intended for DNS lookups, SSL certificate checks or HTTP header analysis.
- Requirements
- A remote MCP endpoint added by URL to an MCP client; no API key or signup. Each call is paid in USDC on Base L2 through the x402 protocol, so an x402-aware client or wallet that can sign the payment challenge is needed. Network access to the endpoint is required.
Installation
In SourceWeft
- Open Port Scanner API in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fport-scanner/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"port-scanner-api": {
"type": "sse",
"url": "https://port-scanner.api.klymax402.com/mcp"
}
}
}README
Port Scanner API
[MCP Server] [x402] [License: MIT]
Scan 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.
Quickstart -- MCP
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
Quickstart -- HTTP (x402)
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
Tools
network_scan_ports
Use this when you need to check which TCP ports are open on a host. Returns port status and response times in JSON.
Parameters
Example response:
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).
Example agent prompts
- "Check which TCP ports are open on a host"
Payment
- Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
- Network: Base L2 (
eip155:8453) - Asset: USDC
- Facilitator: Coinbase CDP (primary), PayAI (fallback)
- Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)
Part of klymax402
100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
Source: README.md at commit be93c53
Tools
0Version history
1- v1.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Port integrations

Port
io.portOfficial publisher
Port's remote MCP server connects Port.io to an IDE, LLM or agent platform, letting an assistant work with your Port.io environment through OAuth-authenticated,

GravityPort
Published by GitHub account fengseekling-coder
MCP server bundled with the GravityPort desktop app that lets Claude, Codex and other clients search and record a local library of AI-generated images, videos…

Worktrack Port
Published by GitHub account CloudCorpRecords
Jira issues and Confluence pages via the REST APIs, as MCP tools.

Videohub Port
Published by GitHub account CloudCorpRecords
YouTube videos, channels, playlists, comments and transcripts as MCP tools.

Tasklist Port
Published by GitHub account CloudCorpRecords
Tasklist Port's local MCP server; no sign-in required; STDIO.