mcp-registry/ai.trydock/dock/upgrade_plan / alternatives

Live alternatives to mcp-registry/ai.trydock/dock/upgrade_plan

The best live alternatives to mcp-registry/ai.trydock/dock/upgrade_plan right now are mcp-registry/io.github.pipeworx-io/elexon/subscribe, mcp-registry/io.github.pipeworx-io/librivox/subscribe, mcp-registry/io.github.pipeworx-io/jikan/subscribe, mcp-registry/io.github.pipeworx-io/istat-it/subscribe, mcp-registry/io.github.pipeworx-io/polygon-io/subscribe — capability-matched and ranked by current reliability. mcp-registry/ai.trydock/dock/upgrade_plan itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/elexon/subscribe	io.github.pipeworx-io/elexon	live status →
mcp-registry/io.github.pipeworx-io/librivox/subscribe	io.github.pipeworx-io/librivox	live status →
mcp-registry/io.github.pipeworx-io/jikan/subscribe	io.github.pipeworx-io/jikan	live status →
mcp-registry/io.github.pipeworx-io/istat-it/subscribe	io.github.pipeworx-io/istat-it	live status →
mcp-registry/io.github.pipeworx-io/polygon-io/subscribe	io.github.pipeworx-io/polygon-io	live status →
mcp-registry/io.github.pipeworx-io/plos/subscribe	io.github.pipeworx-io/plos	live status →
mcp-registry/io.github.pipeworx-io/pkg-go-dev/subscribe	io.github.pipeworx-io/pkg-go-dev	live status →
mcp-registry/io.github.pipeworx-io/met-no/subscribe	io.github.pipeworx-io/met-no	live status →
mcp-registry/io.github.pipeworx-io/mastodon/subscribe	io.github.pipeworx-io/mastodon	live status →
mcp-registry/io.github.pipeworx-io/arcgis-marioncountyor/subscribe	io.github.pipeworx-io/arcgis-marioncountyor	live status →
mcp-registry/io.github.pipeworx-io/gtex/subscribe	io.github.pipeworx-io/gtex	live status →
mcp-registry/io.github.pipeworx-io/github_private/subscribe	io.github.pipeworx-io/github_private	live status →

FAQ

What is the best alternative to mcp-registry/ai.trydock/dock/upgrade_plan?

mcp-registry/io.github.pipeworx-io/elexon/subscribe is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/librivox/subscribe, mcp-registry/io.github.pipeworx-io/jikan/subscribe, mcp-registry/io.github.pipeworx-io/istat-it/subscribe, mcp-registry/io.github.pipeworx-io/polygon-io/subscribe. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/ai.trydock/dock/upgrade_plan down right now?

mcp-registry/ai.trydock/dock/upgrade_plan's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fai.trydock%2Fdock%2Fupgrade_plan.

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.trydock%2Fdock%2Fupgrade_plan or MCP find_alternatives. Check mcp-registry/ai.trydock/dock/upgrade_plan's live status: https://glimind.com/tool/mcp-registry/ai.trydock/dock/upgrade_plan.