mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_reliability / alternatives

Live alternatives to mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_reliability

The best live alternatives to mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_reliability right now are mcp-registry/io.github.lxxmng/ocean-schedules/carrier_reliability, mcp-registry/io.github.lxxmng/ocean-schedules/carrier_league, mcp-registry/io.github.foundrynet/weather-intel-mcp/supply_chain_risk, mcp-registry/io.github.lxxmng/ocean-schedules/compare_lanes, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_rail_freight_status — capability-matched and ranked by current reliability. mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_reliability itself is currently "healthy".

alternative	server
mcp-registry/io.github.lxxmng/ocean-schedules/carrier_reliability	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.foundrynet/weather-intel-mcp/supply_chain_risk	io.github.FoundryNet/weather-intel-mcp	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_rail_freight_status	io.github.SupplyMaven-SCR/supply-chain-intelligence	live status →
mcp-registry/io.github.lxxmng/ocean-schedules/transit_time	io.github.lxxmng/ocean-schedules	live status →
mcp-registry/com.gocreativeai.omnicall/agent-tools/finance_carrier	com.gocreativeai.omnicall/agent-tools	live status →
mcp-registry/io.github.colinhughes2121/gocreative-agent-api/finance_carrier	io.github.ColinHughes2121/gocreative-agent-api	live status →
mcp-registry/io.github.foundrynet/currency-intel-mcp/rate_trend	io.github.FoundryNet/currency-intel-mcp	live status →
mcp-registry/io.github.foundrynet/currency-intel-mcp/transaction_cost	io.github.FoundryNet/currency-intel-mcp	live status →
mcp-registry/io.github.foundrynet/currency-intel-mcp/historical_rate	io.github.FoundryNet/currency-intel-mcp	live status →
mcp-registry/io.github.baneado98/freight-pulse/get_scorecard	io.github.Baneado98/freight-pulse	live status →

FAQ

What is the best alternative to mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_reliability?

mcp-registry/io.github.lxxmng/ocean-schedules/carrier_reliability is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.lxxmng/ocean-schedules/carrier_league, mcp-registry/io.github.foundrynet/weather-intel-mcp/supply_chain_risk, mcp-registry/io.github.lxxmng/ocean-schedules/compare_lanes, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_rail_freight_status. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_reliability down right now?

mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_reliability's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.vinaybhosle%2Fshippingrates-mcp-server%2Fshippingrates_reliability.

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.vinaybhosle%2Fshippingrates-mcp-server%2Fshippingrates_reliability or MCP find_alternatives. Check mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_reliability's live status: https://glimind.com/tool/mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_reliability.