mcp-registry/io.github.imviky-ctrl/tickerr/get_tool_status / alternatives

Live alternatives to mcp-registry/io.github.imviky-ctrl/tickerr/get_tool_status

The best live alternatives to mcp-registry/io.github.imviky-ctrl/tickerr/get_tool_status right now are mcp-registry/io.github.shawndei/glimind/check_tool_reliability, mcp-registry/io.github.lazymac2x/ai-provider-status/get_all_status, mcp-registry/ai.tooldirectory/catalog/check_tool_status, mcp-registry/io.github.lazymac2x/ai-provider-status/get_provider_status, mcp-registry/io.github.rippermercs/terminalfeed/tf_service_status — capability-matched and ranked by current reliability. mcp-registry/io.github.imviky-ctrl/tickerr/get_tool_status itself is currently "healthy".

alternative	server
mcp-registry/io.github.shawndei/glimind/check_tool_reliability	io.github.shawndei/glimind	live status →
mcp-registry/io.github.lazymac2x/ai-provider-status/get_all_status	io.github.lazymac2x/ai-provider-status	live status →
mcp-registry/ai.tooldirectory/catalog/check_tool_status	ai.tooldirectory/catalog	live status →
mcp-registry/io.github.lazymac2x/ai-provider-status/get_provider_status	io.github.lazymac2x/ai-provider-status	live status →
mcp-registry/io.github.rippermercs/terminalfeed/tf_service_status	io.github.RipperMercs/terminalfeed	live status →
mcp-registry/com.dropwatchhq/ai-api-radar/status	com.dropwatchhq/ai-api-radar	live status →
mcp-registry/io.github.a0985344368-glitch/tsung-ai/status	io.github.a0985344368-glitch/tsung-ai	live status →
mcp-registry/ai.dynamicfeed/dynamic-feed/service_status	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/io.github.pipeworx-io/ai-briefing/get_ai_toolbelt	io.github.pipeworx-io/ai-briefing	live status →
mcp-registry/io.github.saloprj/dialogbrain/agents_ask	io.github.saloprj/dialogbrain	live status →
mcp-registry/io.github.pipeworx-io/exchange/pipeworx_trending	io.github.pipeworx-io/exchange	live status →
mcp-registry/io.github.pipeworx-io/f1/pipeworx_trending	io.github.pipeworx-io/f1	live status →

FAQ

What is the best alternative to mcp-registry/io.github.imviky-ctrl/tickerr/get_tool_status?

mcp-registry/io.github.shawndei/glimind/check_tool_reliability is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.lazymac2x/ai-provider-status/get_all_status, mcp-registry/ai.tooldirectory/catalog/check_tool_status, mcp-registry/io.github.lazymac2x/ai-provider-status/get_provider_status, mcp-registry/io.github.rippermercs/terminalfeed/tf_service_status. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.imviky-ctrl/tickerr/get_tool_status down right now?

mcp-registry/io.github.imviky-ctrl/tickerr/get_tool_status's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.imviky-ctrl%2Ftickerr%2Fget_tool_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.imviky-ctrl%2Ftickerr%2Fget_tool_status or MCP find_alternatives. Check mcp-registry/io.github.imviky-ctrl/tickerr/get_tool_status's live status: https://glimind.com/tool/mcp-registry/io.github.imviky-ctrl/tickerr/get_tool_status.