mcp-registry/io.github.tronsave/mcp/tronsave_cancel_order / alternatives

Live alternatives to mcp-registry/io.github.tronsave/mcp/tronsave_cancel_order

The best live alternatives to mcp-registry/io.github.tronsave/mcp/tronsave_cancel_order right now are mcp-registry/io.github.statico-alt/spacemolt/cancel_order, mcp-registry/exchange.merx/mcp/cancel_standing_order, mcp-registry/market.mtok/mcp/cancel_order, mcp-registry/com.b2bware/mcp-server/cancel_order, mcp-registry/io.github.wirternow/agent-bank/cancel_cc_order — capability-matched and ranked by current reliability. mcp-registry/io.github.tronsave/mcp/tronsave_cancel_order itself is currently "healthy".

alternativeserver
mcp-registry/io.github.statico-alt/spacemolt/cancel_orderio.github.statico-alt/spacemoltlive status →
mcp-registry/exchange.merx/mcp/cancel_standing_orderexchange.merx/mcplive status →
mcp-registry/market.mtok/mcp/cancel_ordermarket.mtok/mcplive status →
mcp-registry/com.b2bware/mcp-server/cancel_ordercom.b2bware/mcp-serverlive status →
mcp-registry/io.github.wirternow/agent-bank/cancel_cc_orderio.github.WirterNow/agent-banklive status →
mcp-registry/io.github.toreva/kit/toreva_perps_cancel_orderio.github.toreva/kitlive status →
mcp-registry/network.tenzro/tenzro/cancel_tasknetwork.tenzro/tenzrolive status →
mcp-registry/co.curie/commerce/cancel_checkoutco.curie/commercelive status →
mcp-registry/cloud.theprotocol/registry/theprotocol_cancelExchangeOrdercloud.theprotocol/registrylive status →
mcp-registry/exchange.merx/mcp/create_paid_orderexchange.merx/mcplive status →
mcp-registry/now.shiply/shiply/refund_ordernow.shiply/shiplylive status →
mcp-registry/shop.theothers/theothers/track_ordershop.theothers/theotherslive status →

FAQ

What is the best alternative to mcp-registry/io.github.tronsave/mcp/tronsave_cancel_order?

mcp-registry/io.github.statico-alt/spacemolt/cancel_order is the top capability-matched alternative that's live right now. Other options: mcp-registry/exchange.merx/mcp/cancel_standing_order, mcp-registry/market.mtok/mcp/cancel_order, mcp-registry/com.b2bware/mcp-server/cancel_order, mcp-registry/io.github.wirternow/agent-bank/cancel_cc_order. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.tronsave/mcp/tronsave_cancel_order down right now?

mcp-registry/io.github.tronsave/mcp/tronsave_cancel_order's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.tronsave%2Fmcp%2Ftronsave_cancel_order.

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.tronsave%2Fmcp%2Ftronsave_cancel_order or MCP find_alternatives. Check mcp-registry/io.github.tronsave/mcp/tronsave_cancel_order's live status: https://glimind.com/tool/mcp-registry/io.github.tronsave/mcp/tronsave_cancel_order.