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

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

The best live alternatives to mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion right now are mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/port_congestion_monitor, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_port_congestion_trends, mcp-registry/io.github.baneado98/freight-pulse/get_port_intel, mcp-registry/io.github.lxxmng/ocean-schedules/port_reliability, mcp-registry/io.github.foundrynet/weather-intel-mcp/supply_chain_risk — capability-matched and ranked by current reliability. mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion itself is currently "healthy".

alternativeserver
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/port_congestion_monitorio.github.SupplyMaven-SCR/supply-chain-intelligencelive status →
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_port_congestion_trendsio.github.SupplyMaven-SCR/supply-chain-intelligencelive status →
mcp-registry/io.github.baneado98/freight-pulse/get_port_intelio.github.Baneado98/freight-pulselive status →
mcp-registry/io.github.lxxmng/ocean-schedules/port_reliabilityio.github.lxxmng/ocean-scheduleslive status →
mcp-registry/io.github.foundrynet/weather-intel-mcp/supply_chain_riskio.github.FoundryNet/weather-intel-mcplive status →
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_chokepoint_trafficio.github.SupplyMaven-SCR/supply-chain-intelligencelive status →
mcp-registry/io.github.baneado98/freight-pulse/get_spot_rateio.github.Baneado98/freight-pulselive status →
mcp-registry/io.github.pipeworx-io/imf-portwatch/chokepoint_daily_trafficio.github.pipeworx-io/imf-portwatchlive status →
mcp-registry/io.github.foundrynet/currency-intel-mcp/rate_trendio.github.FoundryNet/currency-intel-mcplive status →
mcp-registry/io.github.foundrynet/financial-signals-mcp/anomaly_alertio.github.FoundryNet/financial-signals-mcplive status →
mcp-registry/io.github.baneado98/freight-pulse/rate_benchmarkio.github.Baneado98/freight-pulselive status →
mcp-registry/io.github.foundrynet/currency-intel-mcp/transaction_costio.github.FoundryNet/currency-intel-mcplive status →

FAQ

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

mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/port_congestion_monitor is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_port_congestion_trends, mcp-registry/io.github.baneado98/freight-pulse/get_port_intel, mcp-registry/io.github.lxxmng/ocean-schedules/port_reliability, mcp-registry/io.github.foundrynet/weather-intel-mcp/supply_chain_risk. Glimind ranks alternatives by semantic similarity and live health.

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

mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion'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_congestion.

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