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

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

The best live alternatives to mcp-registry/io.github.baneado98/freight-pulse/get_spot_rate right now are mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_rates, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_freight_rate_pressure, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_risk_score, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_freight_rate_observations, mcp-registry/com.currencyguard/guard-pricing/get_spot_rate — capability-matched and ranked by current reliability. mcp-registry/io.github.baneado98/freight-pulse/get_spot_rate itself is currently "healthy".

alternative	server
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_rates	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_freight_rate_pressure	io.github.SupplyMaven-SCR/supply-chain-intelligence	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_risk_score	io.github.vinaybhosle/shippingrates-mcp-server	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/com.currencyguard/guard-pricing/get_spot_rate	com.currencyguard/guard-pricing	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/market.mtok/mcp/get_spot	market.mtok/mcp	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_fx	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_inland_haulage	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/dev.goldprice/mcp/get_spot_price	dev.goldprice/mcp	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_cfs_tariffs	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_spot_rate?

mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_rates is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_freight_rate_pressure, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_risk_score, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_freight_rate_observations, mcp-registry/com.currencyguard/guard-pricing/get_spot_rate. Glimind ranks alternatives by semantic similarity and live health.

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

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

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