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

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

The best live alternatives to mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_local_charges right now are mcp-registry/io.github.foundrynet/currency-intel-mcp/transaction_cost, mcp-registry/io.github.foundrynet/weather-intel-mcp/supply_chain_risk, mcp-registry/io.github.colinhughes2121/gocreative-agent-api/calc_tax, mcp-registry/io.github.baneado98/freight-pulse/door_to_door, mcp-registry/io.github.adopteunconteneur/delivery-calculator/calculateContainerDeliveryCost — capability-matched and ranked by current reliability. mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_local_charges itself is currently "healthy".

alternative	server
mcp-registry/io.github.foundrynet/currency-intel-mcp/transaction_cost	io.github.FoundryNet/currency-intel-mcp	live status →
mcp-registry/io.github.foundrynet/weather-intel-mcp/supply_chain_risk	io.github.FoundryNet/weather-intel-mcp	live status →
mcp-registry/io.github.colinhughes2121/gocreative-agent-api/calc_tax	io.github.ColinHughes2121/gocreative-agent-api	live status →
mcp-registry/io.github.baneado98/freight-pulse/door_to_door	io.github.Baneado98/freight-pulse	live status →
mcp-registry/io.github.adopteunconteneur/delivery-calculator/calculateContainerDeliveryCost	io.github.adopteunconteneur/delivery-calculator	live status →
pulsemcp/adopte-un-conteneur/calculateContainerDeliveryCost	Adopte un Conteneur	live status →
mcp-registry/com.onlineshippingcalculator/shipping-rates/get_shipping_rates	com.onlineshippingcalculator/shipping-rates	live status →
mcp-registry/io.github.foundrynet/currency-intel-mcp/historical_rate	io.github.FoundryNet/currency-intel-mcp	live status →
mcp-registry/io.github.colinhughes2121/gocreative-agent-api/calc_sales_tax_reverse	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 →
mcp-registry/io.github.pipeworx-io/hts/hts_lookup	io.github.pipeworx-io/hts	live status →
mcp-registry/io.github.colinhughes2121/gocreative-agent-api/calc_fuel	io.github.ColinHughes2121/gocreative-agent-api	live status →

FAQ

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

mcp-registry/io.github.foundrynet/currency-intel-mcp/transaction_cost is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.foundrynet/weather-intel-mcp/supply_chain_risk, mcp-registry/io.github.colinhughes2121/gocreative-agent-api/calc_tax, mcp-registry/io.github.baneado98/freight-pulse/door_to_door, 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_local_charges down right now?

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

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