Is mcp-registry/io.github.cryptomotifs/cipher-x402-mcp/audit_comp_live_listings working right now?
Working alternatives
- mcp-registry/com.contrastcyber/api/tech_stack_cve_audit com.contrastcyber/api
- mcp-registry/com.crosswire-api/crosswire-polymarket-kalshi-arbitrage/list_covered_events com.crosswire-api/crosswire-polymarket-kalshi-arbitrage
- mcp-registry/io.github.disclose/lookup-disclose-io/lookup_security_contact io.github.disclose/lookup-disclose-io
- mcp-registry/xyz.signomy/civitae/admin.stats xyz.signomy/civitae
FAQ
Is mcp-registry/io.github.cryptomotifs/cipher-x402-mcp/audit_comp_live_listings working right now?
As of the latest check, mcp-registry/io.github.cryptomotifs/cipher-x402-mcp/audit_comp_live_listings 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/audit_comp_live_listings?
mcp-registry/io.github.cryptomotifs/cipher-x402-mcp/audit_comp_live_listings 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/audit_comp_live_listings 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/com.contrastcyber/api/tech_stack_cve_audit, mcp-registry/com.crosswire-api/crosswire-polymarket-kalshi-arbitrage/list_covered_events, mcp-registry/io.github.disclose/lookup-disclose-io/lookup_security_contact, mcp-registry/xyz.signomy/civitae/admin.stats.
What are the best alternatives to mcp-registry/io.github.cryptomotifs/cipher-x402-mcp/audit_comp_live_listings?
Working alternatives ranked by capability similarity and live health: mcp-registry/com.contrastcyber/api/tech_stack_cve_audit, mcp-registry/com.crosswire-api/crosswire-polymarket-kalshi-arbitrage/list_covered_events, mcp-registry/io.github.disclose/lookup-disclose-io/lookup_security_contact, mcp-registry/xyz.signomy/civitae/admin.stats. See each one's live status on Glimind.
How do I call mcp-registry/io.github.cryptomotifs/cipher-x402-mcp/audit_comp_live_listings reliably?
Before calling, check mcp-registry/io.github.cryptomotifs/cipher-x402-mcp/audit_comp_live_listings with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.github.cryptomotifs%2Fcipher-x402-mcp%2Faudit_comp_live_listings) 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%2Faudit_comp_live_listings)
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%2Faudit_comp_live_listings. 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:32:54.069Z.