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

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

The best live alternatives to mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk right now are mcp-registry/io.github.baneado98/freight-pulse/lane_risk_index, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_risk_score, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion_news, mcp-registry/xyz.lonestaroracle/mcp-server/supply_chain_intelligence, mcp-registry/io.github.baneado98/freight-pulse/simulate_scenario — capability-matched and ranked by current reliability. mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk itself is currently "healthy".

alternative	server
mcp-registry/io.github.baneado98/freight-pulse/lane_risk_index	io.github.Baneado98/freight-pulse	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.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion_news	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/xyz.lonestaroracle/mcp-server/supply_chain_intelligence	xyz.lonestaroracle/mcp-server	live status →
mcp-registry/io.github.baneado98/freight-pulse/simulate_scenario	io.github.Baneado98/freight-pulse	live status →
mcp-registry/io.github.pipeworx-io/imf-portwatch/chokepoints_list	io.github.pipeworx-io/imf-portwatch	live status →
mcp-registry/ai.intuitek.the-stall/the-stall/supply-chain-brief	ai.intuitek.the-stall/the-stall	live status →
mcp-registry/io.github.baneado98/freight-pulse/market_report	io.github.Baneado98/freight-pulse	live status →
mcp-registry/xyz.lonestaroracle/mcp-server/geo_pulse	xyz.lonestaroracle/mcp-server	live status →
mcp-registry/io.github.getgapup/gapup-mcp/africa_trade_barrier_breaker	io.github.getgapup/gapup-mcp	live status →
mcp-registry/io.github.getgapup/mcp-knowledge/africa_trade_barrier_breaker	io.github.getgapup/mcp-knowledge	live status →
mcp-registry/io.github.baneado98/freight-pulse/sourcing_analysis	io.github.Baneado98/freight-pulse	live status →

FAQ

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

mcp-registry/io.github.baneado98/freight-pulse/lane_risk_index is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_risk_score, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion_news, mcp-registry/xyz.lonestaroracle/mcp-server/supply_chain_intelligence, mcp-registry/io.github.baneado98/freight-pulse/simulate_scenario. Glimind ranks alternatives by semantic similarity and live health.

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

mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk'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%2Fget_corridor_risk.

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