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

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

The best live alternatives to mcp-registry/io.github.baneado98/freight-pulse/select_provider right now are mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk, mcp-registry/ai.intuitek.the-stall/the-stall/supply-chain-brief, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_inland_search, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_freight_rate_pressure, mcp-registry/io.github.blackboxfoundry/livedatalink/fmcsa_carrier_compare — capability-matched and ranked by current reliability. mcp-registry/io.github.baneado98/freight-pulse/select_provider itself is currently "healthy".

alternative	server
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk	io.github.SupplyMaven-SCR/supply-chain-intelligence	live status →
mcp-registry/ai.intuitek.the-stall/the-stall/supply-chain-brief	ai.intuitek.the-stall/the-stall	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_inland_search	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.blackboxfoundry/livedatalink/fmcsa_carrier_compare	io.github.blackboxfoundry/livedatalink	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.lxxmng/container-loading/plan_load	io.github.lxxmng/container-loading	live status →
mcp-registry/io.github.soapyred/freightutils/shipment_summary	io.github.SoapyRED/freightutils	live status →
mcp-registry/io.github.lxxmng/ocean-schedules/carrier_league	io.github.lxxmng/ocean-schedules	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_inland_haulage	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/com.dropwatchhq/freight-intel/new_carriers	com.dropwatchhq/freight-intel	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/fmcsa_carrier_lookup	io.github.blackboxfoundry/livedatalink	live status →

FAQ

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

mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk is the top capability-matched alternative that's live right now. Other options: mcp-registry/ai.intuitek.the-stall/the-stall/supply-chain-brief, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_inland_search, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_freight_rate_pressure, mcp-registry/io.github.blackboxfoundry/livedatalink/fmcsa_carrier_compare. Glimind ranks alternatives by semantic similarity and live health.

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

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

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