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

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

The best live alternatives to mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_facilities right now are mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_freight_rate_observations, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_freight_rate_pressure, mcp-registry/cloud.dchub/mcp-server/get_facility, mcp-registry/io.github.foundrynet/weather-intel-mcp/supply_chain_risk, mcp-registry/com.avnester.mcp/property-intelligence/estimate_stamp_duty_and_registration — capability-matched and ranked by current reliability. mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_facilities itself is currently "healthy".

alternative	server
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_freight_rate_observations	io.github.SupplyMaven-SCR/supply-chain-intelligence	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/cloud.dchub/mcp-server/get_facility	cloud.dchub/mcp-server	live status →
mcp-registry/io.github.foundrynet/weather-intel-mcp/supply_chain_risk	io.github.FoundryNet/weather-intel-mcp	live status →
mcp-registry/com.avnester.mcp/property-intelligence/estimate_stamp_duty_and_registration	com.avnester.mcp/property-intelligence	live status →
mcp-registry/cloud.dchub/mcp-server/search_facilities	cloud.dchub/mcp-server	live status →
mcp-registry/com.gocreativeai.omnicall/agent-tools/finance_carrier	com.gocreativeai.omnicall/agent-tools	live status →
mcp-registry/io.github.colinhughes2121/gocreative-agent-api/finance_carrier	io.github.ColinHughes2121/gocreative-agent-api	live status →
mcp-registry/com.fiatdock/fiatdock-mcp/get_service	com.fiatdock/fiatdock-mcp	live status →
mcp-registry/io.github.baneado98/freight-pulse/get_spot_rate	io.github.Baneado98/freight-pulse	live status →
mcp-registry/io.github.colinhughes2121/gocreative-agent-api/ip	io.github.ColinHughes2121/gocreative-agent-api	live status →
mcp-registry/io.github.baneado98/freight-pulse/get_all_in_rate	io.github.Baneado98/freight-pulse	live status →

FAQ

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

mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_freight_rate_observations 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/cloud.dchub/mcp-server/get_facility, mcp-registry/io.github.foundrynet/weather-intel-mcp/supply_chain_risk, mcp-registry/com.avnester.mcp/property-intelligence/estimate_stamp_duty_and_registration. Glimind ranks alternatives by semantic similarity and live health.

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

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

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