mcp-registry/io.github.baneado98/freight-pulse/contingency_plan / alternatives

Live alternatives to mcp-registry/io.github.baneado98/freight-pulse/contingency_plan

The best live alternatives to mcp-registry/io.github.baneado98/freight-pulse/contingency_plan right now are mcp-registry/io.github.davidmosiah/delx-mcp-a2a/logistics_disruption_recovery, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion_news, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk, mcp-registry/io.github.pipeworx-io/imf-portwatch/recent_disruptions, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_chokepoint_traffic — capability-matched and ranked by current reliability. mcp-registry/io.github.baneado98/freight-pulse/contingency_plan itself is currently "healthy".

alternative	server
mcp-registry/io.github.davidmosiah/delx-mcp-a2a/logistics_disruption_recovery	io.github.davidmosiah/delx-mcp-a2a	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.supplymaven-scr/supply-chain-intelligence/get_corridor_risk	io.github.SupplyMaven-SCR/supply-chain-intelligence	live status →
mcp-registry/io.github.pipeworx-io/imf-portwatch/recent_disruptions	io.github.pipeworx-io/imf-portwatch	live status →
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_chokepoint_traffic	io.github.SupplyMaven-SCR/supply-chain-intelligence	live status →
mcp-registry/io.github.pipeworx-io/tfl/disruptions	io.github.pipeworx-io/tfl	live status →
mcp-registry/io.github.lxxmng/ocean-schedules/port_reliability	io.github.lxxmng/ocean-schedules	live status →
mcp-registry/io.tooloracle/conductor/plan_remediation	io.tooloracle/conductor	live status →
mcp-registry/io.github.lxxmng/ocean-schedules/find_best_sailings	io.github.lxxmng/ocean-schedules	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_risk_score	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/port_congestion_monitor	io.github.SupplyMaven-SCR/supply-chain-intelligence	live status →
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/supply_chain_disruption_alerts	io.github.SupplyMaven-SCR/supply-chain-intelligence	live status →

FAQ

What is the best alternative to mcp-registry/io.github.baneado98/freight-pulse/contingency_plan?

mcp-registry/io.github.davidmosiah/delx-mcp-a2a/logistics_disruption_recovery is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion_news, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk, mcp-registry/io.github.pipeworx-io/imf-portwatch/recent_disruptions, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_chokepoint_traffic. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.baneado98/freight-pulse/contingency_plan down right now?

mcp-registry/io.github.baneado98/freight-pulse/contingency_plan's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.baneado98%2Ffreight-pulse%2Fcontingency_plan.

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.baneado98%2Ffreight-pulse%2Fcontingency_plan or MCP find_alternatives. Check mcp-registry/io.github.baneado98/freight-pulse/contingency_plan's live status: https://glimind.com/tool/mcp-registry/io.github.baneado98/freight-pulse/contingency_plan.