mcp-registry/com.coinbucha/bitcoin-signals/get_network_signal / alternatives
mcp-registry/com.coinbucha/bitcoin-signals/get_network_signalThe best live alternatives to mcp-registry/com.coinbucha/bitcoin-signals/get_network_signal right now are mcp-registry/io.github.pipeworx-io/mempool-space/hashrate, mcp-registry/com.prereason/mcp/get_metric, mcp-registry/ai.dynamicfeed/dynamic-feed/bitcoin_network, mcp-registry/io.emc2ai/einstein/bitcoin_onchain_analytics, mcp-registry/ai.aarna/atars-mcp/get_signal_history — capability-matched and ranked by current reliability. mcp-registry/com.coinbucha/bitcoin-signals/get_network_signal itself is currently "healthy".
mcp-registry/io.github.pipeworx-io/mempool-space/hashrate is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.prereason/mcp/get_metric, mcp-registry/ai.dynamicfeed/dynamic-feed/bitcoin_network, mcp-registry/io.emc2ai/einstein/bitcoin_onchain_analytics, mcp-registry/ai.aarna/atars-mcp/get_signal_history. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/com.coinbucha/bitcoin-signals/get_network_signal's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.coinbucha%2Fbitcoin-signals%2Fget_network_signal.
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.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fcom.coinbucha%2Fbitcoin-signals%2Fget_network_signal
or MCP find_alternatives. Check mcp-registry/com.coinbucha/bitcoin-signals/get_network_signal's live status: https://glimind.com/tool/mcp-registry/com.coinbucha/bitcoin-signals/get_network_signal.