mcp-registry/io.github.baneado98/freight-pulse/cold_chain / alternatives
mcp-registry/io.github.baneado98/freight-pulse/cold_chainThe best live alternatives to mcp-registry/io.github.baneado98/freight-pulse/cold_chain right now are mcp-registry/io.github.soapyred/freightutils/shipment_summary, mcp-registry/io.github.soapyred/freightutils/emissions_calculator, mcp-registry/xyz.lonestaroracle/mcp-server/supply_chain_intelligence, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/risk_pillar_breakdown, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk — capability-matched and ranked by current reliability. mcp-registry/io.github.baneado98/freight-pulse/cold_chain itself is currently "healthy".
mcp-registry/io.github.soapyred/freightutils/shipment_summary is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.soapyred/freightutils/emissions_calculator, mcp-registry/xyz.lonestaroracle/mcp-server/supply_chain_intelligence, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/risk_pillar_breakdown, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.baneado98/freight-pulse/cold_chain's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.baneado98%2Ffreight-pulse%2Fcold_chain.
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.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.baneado98%2Ffreight-pulse%2Fcold_chain
or MCP find_alternatives. Check mcp-registry/io.github.baneado98/freight-pulse/cold_chain's live status: https://glimind.com/tool/mcp-registry/io.github.baneado98/freight-pulse/cold_chain.