mcp-registry/ai.thinkneo/control-plane/thinkneo_provider_status / alternatives

Live alternatives to mcp-registry/ai.thinkneo/control-plane/thinkneo_provider_status

The best live alternatives to mcp-registry/ai.thinkneo/control-plane/thinkneo_provider_status right now are mcp-registry/ai.agentberg/agentberg/query_network_brief, mcp-registry/ai.agentberg/agentberg/query_findings, mcp-registry/io.github.swarmsync-ai/conduit-mcp/swarmsync_discover_agents, mcp-registry/io.github.pipeworx-io/google_calendar/pipeworx_trending, mcp-registry/io.github.pipeworx-io/tfl/pipeworx_trending — capability-matched and ranked by current reliability. mcp-registry/ai.thinkneo/control-plane/thinkneo_provider_status itself is currently "healthy".

alternative	server
mcp-registry/ai.agentberg/agentberg/query_network_brief	ai.agentberg/agentberg	live status →
mcp-registry/ai.agentberg/agentberg/query_findings	ai.agentberg/agentberg	live status →
mcp-registry/io.github.swarmsync-ai/conduit-mcp/swarmsync_discover_agents	io.github.swarmsync-ai/conduit-mcp	live status →
mcp-registry/io.github.pipeworx-io/google_calendar/pipeworx_trending	io.github.pipeworx-io/google_calendar	live status →
mcp-registry/io.github.pipeworx-io/tfl/pipeworx_trending	io.github.pipeworx-io/tfl	live status →
mcp-registry/io.github.pipeworx-io/the-graph/pipeworx_trending	io.github.pipeworx-io/the-graph	live status →
mcp-registry/io.github.pipeworx-io/ssb-no/pipeworx_trending	io.github.pipeworx-io/ssb-no	live status →
mcp-registry/io.github.pipeworx-io/stat-lv/pipeworx_trending	io.github.pipeworx-io/stat-lv	live status →
mcp-registry/io.github.pipeworx-io/statcan/pipeworx_trending	io.github.pipeworx-io/statcan	live status →
mcp-registry/io.github.pipeworx-io/statbank-md/pipeworx_trending	io.github.pipeworx-io/statbank-md	live status →
mcp-registry/io.github.pipeworx-io/stat-gl/pipeworx_trending	io.github.pipeworx-io/stat-gl	live status →
mcp-registry/io.github.pipeworx-io/spoonacular/pipeworx_trending	io.github.pipeworx-io/spoonacular	live status →

FAQ

What is the best alternative to mcp-registry/ai.thinkneo/control-plane/thinkneo_provider_status?

mcp-registry/ai.agentberg/agentberg/query_network_brief is the top capability-matched alternative that's live right now. Other options: mcp-registry/ai.agentberg/agentberg/query_findings, mcp-registry/io.github.swarmsync-ai/conduit-mcp/swarmsync_discover_agents, mcp-registry/io.github.pipeworx-io/google_calendar/pipeworx_trending, mcp-registry/io.github.pipeworx-io/tfl/pipeworx_trending. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/ai.thinkneo/control-plane/thinkneo_provider_status down right now?

mcp-registry/ai.thinkneo/control-plane/thinkneo_provider_status's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fai.thinkneo%2Fcontrol-plane%2Fthinkneo_provider_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%2Fai.thinkneo%2Fcontrol-plane%2Fthinkneo_provider_status or MCP find_alternatives. Check mcp-registry/ai.thinkneo/control-plane/thinkneo_provider_status's live status: https://glimind.com/tool/mcp-registry/ai.thinkneo/control-plane/thinkneo_provider_status.