mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/port_congestion_monitor / alternatives

Live alternatives to mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/port_congestion_monitor

The best live alternatives to mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/port_congestion_monitor right now are mcp-registry/io.github.baneado98/freight-pulse/get_port_intel, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion, mcp-registry/io.github.lxxmng/ocean-schedules/port_reliability, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion_news, mcp-registry/io.github.pipeworx-io/imf-portwatch/chokepoint_daily_traffic — capability-matched and ranked by current reliability. mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/port_congestion_monitor itself is currently "healthy".

alternative	server
mcp-registry/io.github.baneado98/freight-pulse/get_port_intel	io.github.Baneado98/freight-pulse	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/io.github.lxxmng/ocean-schedules/port_reliability	io.github.lxxmng/ocean-schedules	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion_news	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/io.github.pipeworx-io/imf-portwatch/chokepoint_daily_traffic	io.github.pipeworx-io/imf-portwatch	live status →
mcp-registry/io.github.pipeworx-io/imf-portwatch/recent_disruptions	io.github.pipeworx-io/imf-portwatch	live status →
mcp-registry/com.moltravel/travel/ferryhopper_get_ports	com.moltravel/travel	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_risk_score	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/com.chartercaptain/charter-captain/list_harbors	com.chartercaptain/charter-captain	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_port	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_vessel_schedule	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/com.moltravel/travel/ferryhopper_get_direct_connections_for_ports	com.moltravel/travel	live status →

FAQ

What is the best alternative to mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/port_congestion_monitor?

mcp-registry/io.github.baneado98/freight-pulse/get_port_intel is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion, mcp-registry/io.github.lxxmng/ocean-schedules/port_reliability, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion_news, mcp-registry/io.github.pipeworx-io/imf-portwatch/chokepoint_daily_traffic. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/port_congestion_monitor down right now?

mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/port_congestion_monitor's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.supplymaven-scr%2Fsupply-chain-intelligence%2Fport_congestion_monitor.

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.supplymaven-scr%2Fsupply-chain-intelligence%2Fport_congestion_monitor or MCP find_alternatives. Check mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/port_congestion_monitor's live status: https://glimind.com/tool/mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/port_congestion_monitor.