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

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

The best live alternatives to mcp-registry/io.github.baneado98/freight-pulse/equipment_availability right now are mcp-registry/io.github.lxxmng/container-loading/plan_load, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_risk_score, mcp-registry/io.github.lxxmng/container-loading/suggest_containers, mcp-registry/com.kubova/container-loading/estimate_capacity, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_total_cost — capability-matched and ranked by current reliability. mcp-registry/io.github.baneado98/freight-pulse/equipment_availability itself is currently "healthy".

alternative	server
mcp-registry/io.github.lxxmng/container-loading/plan_load	io.github.lxxmng/container-loading	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.lxxmng/container-loading/suggest_containers	io.github.lxxmng/container-loading	live status →
mcp-registry/com.kubova/container-loading/estimate_capacity	com.kubova/container-loading	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_total_cost	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/io.github.packrift/packrift-mcp/inventory_status	io.github.Packrift/packrift-mcp	live status →
mcp-registry/io.github.lxxmng/container-loading/list_equipment	io.github.lxxmng/container-loading	live status →
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk	io.github.SupplyMaven-SCR/supply-chain-intelligence	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_vessel_schedule_options	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/io.github.soapyred/freightutils/container_lookup	io.github.SoapyRED/freightutils	live status →
mcp-registry/com.kubova/container-loading/pack_containers	com.kubova/container-loading	live status →

FAQ

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

mcp-registry/io.github.lxxmng/container-loading/plan_load is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_risk_score, mcp-registry/io.github.lxxmng/container-loading/suggest_containers, mcp-registry/com.kubova/container-loading/estimate_capacity, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_total_cost. Glimind ranks alternatives by semantic similarity and live health.

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

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

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