mcp-registry/io.github.br0ski777/port-scanner/network_scan_ports / alternatives

Live alternatives to mcp-registry/io.github.br0ski777/port-scanner/network_scan_ports

The best live alternatives to mcp-registry/io.github.br0ski777/port-scanner/network_scan_ports right now are mcp-registry/com.geekflare/mcp/openPorts, mcp-registry/com.portscan/port-scanner/fast_scan, mcp-registry/com.portscan/port-scanner/deep_scan, mcp-registry/io.github.astafford8488/agentaegis/vuln_scan_network, mcp-registry/io.github.pipeworx-io/isc-sans/port_activity — capability-matched and ranked by current reliability. mcp-registry/io.github.br0ski777/port-scanner/network_scan_ports itself is currently "healthy".

alternative	server
mcp-registry/com.geekflare/mcp/openPorts	com.geekflare/mcp	live status →
mcp-registry/com.portscan/port-scanner/fast_scan	com.portscan/port-scanner	live status →
mcp-registry/com.portscan/port-scanner/deep_scan	com.portscan/port-scanner	live status →
mcp-registry/io.github.astafford8488/agentaegis/vuln_scan_network	io.github.astafford8488/agentaegis	live status →
mcp-registry/io.github.pipeworx-io/isc-sans/port_activity	io.github.pipeworx-io/isc-sans	live status →
mcp-registry/io.github.cthulhutoo/agentry/trigger_scan_api_scanner_scan_post	io.github.cthulhutoo/agentry	live status →
mcp-registry/com.moltravel/travel/ferryhopper_get_ports	com.moltravel/travel	live status →
mcp-registry/io.github.br0ski777/http-headers/network_analyze_headers	io.github.Br0ski777/http-headers	live status →
mcp-registry/io.github.sam-moreton/openqr/get_scans	io.github.sam-moreton/openqr	live status →
mcp-registry/io.github.cthulhutoo/agentry/get_scan_results_api_scanner_results_get	io.github.cthulhutoo/agentry	live status →
pulsemcp/abbyseo/get_scan_status	AbbySEO	live status →
mcp-registry/com.abbyseo/mcp-server/get_scan_status	com.abbyseo/mcp-server	live status →

FAQ

What is the best alternative to mcp-registry/io.github.br0ski777/port-scanner/network_scan_ports?

mcp-registry/com.geekflare/mcp/openPorts is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.portscan/port-scanner/fast_scan, mcp-registry/com.portscan/port-scanner/deep_scan, mcp-registry/io.github.astafford8488/agentaegis/vuln_scan_network, mcp-registry/io.github.pipeworx-io/isc-sans/port_activity. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.br0ski777/port-scanner/network_scan_ports down right now?

mcp-registry/io.github.br0ski777/port-scanner/network_scan_ports's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.br0ski777%2Fport-scanner%2Fnetwork_scan_ports.

How does Glimind pick alternatives?

By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.br0ski777%2Fport-scanner%2Fnetwork_scan_ports or MCP find_alternatives. Check mcp-registry/io.github.br0ski777/port-scanner/network_scan_ports's live status: https://glimind.com/tool/mcp-registry/io.github.br0ski777/port-scanner/network_scan_ports.