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

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

The best live alternatives to mcp-registry/io.github.baneado98/freight-pulse/optimize_network right now are mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk, mcp-registry/io.github.lxxmng/ocean-schedules/compare_lanes, mcp-registry/io.github.lxxmng/ocean-schedules/carrier_league, mcp-registry/io.github.lxxmng/container-loading/plan_load, mcp-registry/io.github.lxxmng/ocean-schedules/find_best_sailings — capability-matched and ranked by current reliability. mcp-registry/io.github.baneado98/freight-pulse/optimize_network itself is currently "healthy".

alternative	server
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.lxxmng/ocean-schedules/compare_lanes	io.github.lxxmng/ocean-schedules	live status →
mcp-registry/io.github.lxxmng/ocean-schedules/carrier_league	io.github.lxxmng/ocean-schedules	live status →
mcp-registry/io.github.lxxmng/container-loading/plan_load	io.github.lxxmng/container-loading	live status →
mcp-registry/io.github.lxxmng/ocean-schedules/find_best_sailings	io.github.lxxmng/ocean-schedules	live status →
mcp-registry/io.github.lxxmng/ocean-schedules/carrier_reliability	io.github.lxxmng/ocean-schedules	live status →
mcp-registry/io.github.lxxmng/container-loading/export_plan	io.github.lxxmng/container-loading	live status →
mcp-registry/io.github.getgapup/mcp-knowledge/geo_logistics_intel	io.github.getgapup/mcp-knowledge	live status →
mcp-registry/io.github.getgapup/gapup-mcp/geo_logistics_intel	io.github.getgapup/gapup-mcp	live status →
mcp-registry/ai.intuitek.the-stall/the-stall/supply-chain-brief	ai.intuitek.the-stall/the-stall	live status →

FAQ

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

mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.lxxmng/ocean-schedules/compare_lanes, mcp-registry/io.github.lxxmng/ocean-schedules/carrier_league, mcp-registry/io.github.lxxmng/container-loading/plan_load, mcp-registry/io.github.lxxmng/ocean-schedules/find_best_sailings. Glimind ranks alternatives by semantic similarity and live health.

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

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

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