mcp-registry/io.github.lxxmng/ocean-schedules/compare_lanes / alternatives

Live alternatives to mcp-registry/io.github.lxxmng/ocean-schedules/compare_lanes

The best live alternatives to mcp-registry/io.github.lxxmng/ocean-schedules/compare_lanes right now are mcp-registry/io.github.baneado98/freight-pulse/carrier_recommendation, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_reliability, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk, mcp-registry/io.github.baneado98/freight-pulse/get_lane_trend, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_transit — capability-matched and ranked by current reliability. mcp-registry/io.github.lxxmng/ocean-schedules/compare_lanes itself is currently "healthy".

alternative	server
mcp-registry/io.github.baneado98/freight-pulse/carrier_recommendation	io.github.Baneado98/freight-pulse	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_reliability	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.baneado98/freight-pulse/get_lane_trend	io.github.Baneado98/freight-pulse	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_transit	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/io.github.baneado98/freight-pulse/get_port_intel	io.github.Baneado98/freight-pulse	live status →
mcp-registry/io.github.baneado98/freight-pulse/optimize_network	io.github.Baneado98/freight-pulse	live status →
mcp-registry/io.github.baneado98/freight-pulse/door_to_door	io.github.Baneado98/freight-pulse	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_inland_compare	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/io.github.baneado98/freight-pulse/evaluate_bids	io.github.Baneado98/freight-pulse	live status →
mcp-registry/io.github.baneado98/freight-pulse/booking_strategy	io.github.Baneado98/freight-pulse	live status →
mcp-registry/io.github.baneado98/freight-pulse/get_spot_rate	io.github.Baneado98/freight-pulse	live status →

FAQ

What is the best alternative to mcp-registry/io.github.lxxmng/ocean-schedules/compare_lanes?

mcp-registry/io.github.baneado98/freight-pulse/carrier_recommendation is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_reliability, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk, mcp-registry/io.github.baneado98/freight-pulse/get_lane_trend, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_transit. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.lxxmng/ocean-schedules/compare_lanes down right now?

mcp-registry/io.github.lxxmng/ocean-schedules/compare_lanes's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.lxxmng%2Focean-schedules%2Fcompare_lanes.

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.lxxmng%2Focean-schedules%2Fcompare_lanes or MCP find_alternatives. Check mcp-registry/io.github.lxxmng/ocean-schedules/compare_lanes's live status: https://glimind.com/tool/mcp-registry/io.github.lxxmng/ocean-schedules/compare_lanes.