Port Info reveals what services typically run on network ports — from HTTP on 80 to SSH on 22. Call via MCP in Cursor or Windsurf, or hit GET /v1/network/port-info?port=443 directly. Returns service names, protocols, and descriptions. Essential for network debugging and security audits when you need authoritative port data, not guesswork.
curl "https://tinyfn.io/v1/network/port-info" \
-H "X-API-Key: YOUR_API_KEY"const response = await fetch('https://tinyfn.io/v1/network/port-info', {
headers: { 'X-API-Key': 'YOUR_API_KEY' }
});
const data = await response.json();
console.log(data);import requests
response = requests.get('https://tinyfn.io/v1/network/port-info',
headers={'X-API-Key': 'YOUR_API_KEY'})
data = response.json()
print(data)Connect your AI agent (Claude, Cursor, Windsurf, etc.) to TinyFn's network tools:
{
"mcpServers": {
"tinyfn-network": {
"url": "https://tinyfn.io/mcp/network",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}Returns the official service name, protocol (TCP/UDP), port number, and description from IANA registry. For example, port 443 returns HTTPS, TCP protocol, and 'HTTP over SSL/TLS'.
In Claude Code or Cursor, call the port-info tool with port parameter 8080. It'll return 'HTTP Alternate' service running on TCP, commonly used for web servers and proxies.
Yes, but returns 'Unassigned' for ports without official IANA assignments. Covers well-known ports (0-1023), registered ports (1024-49151), and dynamic ports (49152-65535).
No, each call checks one port. For multiple ports, make separate API calls or use the MCP tool multiple times in your AI agent workflow.
Many ports are assigned to both TCP and UDP protocols but for different purposes. Port 53 handles DNS over both, while port 80 is HTTP over TCP only.