mcp-registry/io.github.zman504/conductor-relay-mcp/get_status / alternatives

Live alternatives to mcp-registry/io.github.zman504/conductor-relay-mcp/get_status

The best live alternatives to mcp-registry/io.github.zman504/conductor-relay-mcp/get_status right now are mcp-registry/com.wiselyenterprisesllc/x402-agent-payment-infrastructure/x402_worker_status, mcp-registry/io.tooloracle/conductor/health_check, mcp-registry/io.github.pipeworx-io/kraken/system_status, mcp-registry/com.scanmalware.mcp/scanmalware-mcp/get_health, mcp-registry/io.github.meltingpixelsai/relayzero/health — capability-matched and ranked by current reliability. mcp-registry/io.github.zman504/conductor-relay-mcp/get_status itself is currently "healthy".

alternativeserver
mcp-registry/com.wiselyenterprisesllc/x402-agent-payment-infrastructure/x402_worker_statuscom.wiselyenterprisesllc/x402-agent-payment-infrastructurelive status →
mcp-registry/io.tooloracle/conductor/health_checkio.tooloracle/conductorlive status →
mcp-registry/io.github.pipeworx-io/kraken/system_statusio.github.pipeworx-io/krakenlive status →
mcp-registry/com.scanmalware.mcp/scanmalware-mcp/get_healthcom.scanmalware.mcp/scanmalware-mcplive status →
mcp-registry/io.github.meltingpixelsai/relayzero/healthio.github.meltingpixelsai/relayzerolive status →
mcp-registry/cloud.theprotocol/registry/theprotocol_getRelayStatuscloud.theprotocol/registrylive status →
mcp-registry/io.github.iainkek/flipr-x402/flipr_statusio.github.iainkek/flipr-x402live status →
mcp-registry/io.github.feedoracle/feedoracle-macro-mcp/health_checkio.github.feedoracle/feedoracle-macro-mcplive status →
mcp-registry/io.tooloracle/macroooracle/health_checkio.tooloracle/macroooraclelive status →
mcp-registry/io.tooloracle/newsoracle/health_checkio.tooloracle/newsoraclelive status →
mcp-registry/com.hydrata/hydrata-mcp-server/get_run_statuscom.hydrata/hydrata-mcp-serverlive status →
mcp-registry/com.prereason/mcp/get_healthcom.prereason/mcplive status →

FAQ

What is the best alternative to mcp-registry/io.github.zman504/conductor-relay-mcp/get_status?

mcp-registry/com.wiselyenterprisesllc/x402-agent-payment-infrastructure/x402_worker_status is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.tooloracle/conductor/health_check, mcp-registry/io.github.pipeworx-io/kraken/system_status, mcp-registry/com.scanmalware.mcp/scanmalware-mcp/get_health, mcp-registry/io.github.meltingpixelsai/relayzero/health. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.zman504/conductor-relay-mcp/get_status down right now?

mcp-registry/io.github.zman504/conductor-relay-mcp/get_status's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.zman504%2Fconductor-relay-mcp%2Fget_status.

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.zman504%2Fconductor-relay-mcp%2Fget_status or MCP find_alternatives. Check mcp-registry/io.github.zman504/conductor-relay-mcp/get_status's live status: https://glimind.com/tool/mcp-registry/io.github.zman504/conductor-relay-mcp/get_status.