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

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

The best live alternatives to mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_inland_haulage right now are mcp-registry/io.github.baneado98/freight-pulse/get_all_in_rate, mcp-registry/io.github.baneado98/freight-pulse/door_to_door, mcp-registry/com.onlineshippingcalculator/shipping-rates/get_shipping_rates, mcp-registry/io.github.baneado98/freight-pulse/get_spot_rate, mcp-registry/io.github.adopteunconteneur/delivery-calculator/calculateContainerDeliveryCost — capability-matched and ranked by current reliability. mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_inland_haulage itself is currently "healthy".

alternativeserver
mcp-registry/io.github.baneado98/freight-pulse/get_all_in_rateio.github.Baneado98/freight-pulselive status →
mcp-registry/io.github.baneado98/freight-pulse/door_to_doorio.github.Baneado98/freight-pulselive status →
mcp-registry/com.onlineshippingcalculator/shipping-rates/get_shipping_ratescom.onlineshippingcalculator/shipping-rateslive status →
mcp-registry/io.github.baneado98/freight-pulse/get_spot_rateio.github.Baneado98/freight-pulselive status →
mcp-registry/io.github.adopteunconteneur/delivery-calculator/calculateContainerDeliveryCostio.github.adopteunconteneur/delivery-calculatorlive status →
pulsemcp/adopte-un-conteneur/calculateContainerDeliveryCostAdopte un Conteneurlive status →
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_freight_rate_observationsio.github.SupplyMaven-SCR/supply-chain-intelligencelive status →
mcp-registry/io.github.baneado98/freight-pulse/equipment_availabilityio.github.Baneado98/freight-pulselive status →
mcp-registry/io.github.rccola990-cloud/x402-agent-store/truck_cost_per_mileio.github.rccola990-cloud/x402-agent-storelive status →
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_freight_rate_pressureio.github.SupplyMaven-SCR/supply-chain-intelligencelive status →
mcp-registry/io.github.baneado98/freight-pulse/compare_modesio.github.Baneado98/freight-pulselive status →
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_rail_freight_statusio.github.SupplyMaven-SCR/supply-chain-intelligencelive status →

FAQ

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

mcp-registry/io.github.baneado98/freight-pulse/get_all_in_rate is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.baneado98/freight-pulse/door_to_door, mcp-registry/com.onlineshippingcalculator/shipping-rates/get_shipping_rates, mcp-registry/io.github.baneado98/freight-pulse/get_spot_rate, mcp-registry/io.github.adopteunconteneur/delivery-calculator/calculateContainerDeliveryCost. Glimind ranks alternatives by semantic similarity and live health.

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

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

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