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

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

The best live alternatives to mcp-registry/io.github.baneado98/freight-pulse/get_lane_trend right now are mcp-registry/io.github.lxxmng/ocean-schedules/find_sailings, mcp-registry/io.github.lxxmng/ocean-schedules/get_schedules, mcp-registry/io.github.lxxmng/ocean-schedules/find_best_sailings, pulsemcp/adbutler/get_placement_forecast, mcp-registry/com.adbutler/mcp-server/get_placement_forecast — capability-matched and ranked by current reliability. mcp-registry/io.github.baneado98/freight-pulse/get_lane_trend itself is currently "healthy".

alternative	server
mcp-registry/io.github.lxxmng/ocean-schedules/find_sailings	io.github.lxxmng/ocean-schedules	live status →
mcp-registry/io.github.lxxmng/ocean-schedules/get_schedules	io.github.lxxmng/ocean-schedules	live status →
mcp-registry/io.github.lxxmng/ocean-schedules/find_best_sailings	io.github.lxxmng/ocean-schedules	live status →
pulsemcp/adbutler/get_placement_forecast	AdButler	live status →
mcp-registry/com.adbutler/mcp-server/get_placement_forecast	com.adbutler/mcp-server	live status →
mcp-registry/io.github.lxxmng/ocean-schedules/compare_lanes	io.github.lxxmng/ocean-schedules	live status →
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_freight_rate_observations	io.github.SupplyMaven-SCR/supply-chain-intelligence	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_rates	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/io.github.lxxmng/ocean-schedules/watch_lane	io.github.lxxmng/ocean-schedules	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_reliability	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_vessel_schedule_options	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 →

FAQ

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

mcp-registry/io.github.lxxmng/ocean-schedules/find_sailings is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.lxxmng/ocean-schedules/get_schedules, mcp-registry/io.github.lxxmng/ocean-schedules/find_best_sailings, pulsemcp/adbutler/get_placement_forecast, mcp-registry/com.adbutler/mcp-server/get_placement_forecast. Glimind ranks alternatives by semantic similarity and live health.

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

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

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