Is mcp-registry/io.github.cryptomotifs/cipher-x402-mcp/coinalyze_funding_rates working right now?
Working alternatives
- mcp-registry/xyz.lonestaroracle/mcp-server/funding_rates xyz.lonestaroracle/mcp-server
- mcp-registry/io.github.digitalweb33333-creator/x402-endpoints/crypto_derivatives_radar io.github.digitalweb33333-creator/x402-endpoints
- mcp-registry/com.cryptowhaleinsights/whale-insights/funding_rates_history com.cryptowhaleinsights/whale-insights
- mcp-registry/ai.intuitek.the-stall/the-stall/funding-rates ai.intuitek.the-stall/the-stall
FAQ
Is mcp-registry/io.github.cryptomotifs/cipher-x402-mcp/coinalyze_funding_rates working right now?
As of the latest check, mcp-registry/io.github.cryptomotifs/cipher-x402-mcp/coinalyze_funding_rates has a Glimind reliability score of 10/100 (grade F) and its current verdict is "down" — recommendation: avoid. Glimind tracks this live from safe liveness probes plus privacy-clean real-usage outcomes.
How reliable is mcp-registry/io.github.cryptomotifs/cipher-x402-mcp/coinalyze_funding_rates?
mcp-registry/io.github.cryptomotifs/cipher-x402-mcp/coinalyze_funding_rates scores 10/100 (grade F) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.
What should I do if mcp-registry/io.github.cryptomotifs/cipher-x402-mcp/coinalyze_funding_rates is down or failing?
Tool is down — don't retry now; switch to a live alternative or back off for minutes. Use a timeout around 1000ms. Live alternatives that do a similar job: mcp-registry/xyz.lonestaroracle/mcp-server/funding_rates, mcp-registry/io.github.digitalweb33333-creator/x402-endpoints/crypto_derivatives_radar, mcp-registry/com.cryptowhaleinsights/whale-insights/funding_rates_history, mcp-registry/ai.intuitek.the-stall/the-stall/funding-rates.
What are the best alternatives to mcp-registry/io.github.cryptomotifs/cipher-x402-mcp/coinalyze_funding_rates?
Working alternatives ranked by capability similarity and live health: mcp-registry/xyz.lonestaroracle/mcp-server/funding_rates, mcp-registry/io.github.digitalweb33333-creator/x402-endpoints/crypto_derivatives_radar, mcp-registry/com.cryptowhaleinsights/whale-insights/funding_rates_history, mcp-registry/ai.intuitek.the-stall/the-stall/funding-rates. See each one's live status on Glimind.
How do I call mcp-registry/io.github.cryptomotifs/cipher-x402-mcp/coinalyze_funding_rates reliably?
Before calling, check mcp-registry/io.github.cryptomotifs/cipher-x402-mcp/coinalyze_funding_rates with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.github.cryptomotifs%2Fcipher-x402-mcp%2Fcoinalyze_funding_rates) to get a known-good input shape, the expected output, a suggested timeout (~1000ms), and a live fallback.
Embed this badge
Show live reliability in your README or status page:
[](https://glimind.com/tool/mcp-registry%2Fio.github.cryptomotifs%2Fcipher-x402-mcp%2Fcoinalyze_funding_rates)
Get the data
Agents: query https://glimind.com/mcp (MCP) or GET https://glimind.com/v1/health/mcp-registry%2Fio.github.cryptomotifs%2Fcipher-x402-mcp%2Fcoinalyze_funding_rates. Install the SDK to contribute outcomes (privacy-preserving) and sharpen this rating — free key · docs.
Rating methodology is transparent and neutral — Glimind sells no tools and runs no integrations; it only measures. Updated 2026-07-01T01:37:26.213Z.