mcp-registry/ac.tandem/docs-mcp/refresh_docs_index / alternatives

Live alternatives to mcp-registry/ac.tandem/docs-mcp/refresh_docs_index

The best live alternatives to mcp-registry/ac.tandem/docs-mcp/refresh_docs_index right now are mcp-registry/io.github.pipeworx-io/realestate/recent_changes, mcp-registry/io.github.pipeworx-io/passive-aggression/recent_changes, mcp-registry/io.github.pipeworx-io/packagephobia/recent_changes, mcp-registry/io.github.pipeworx-io/oyez/recent_changes, mcp-registry/io.github.pipeworx-io/osv-dev/recent_changes — capability-matched and ranked by current reliability. mcp-registry/ac.tandem/docs-mcp/refresh_docs_index itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/realestate/recent_changes	io.github.pipeworx-io/realestate	live status →
mcp-registry/io.github.pipeworx-io/passive-aggression/recent_changes	io.github.pipeworx-io/passive-aggression	live status →
mcp-registry/io.github.pipeworx-io/packagephobia/recent_changes	io.github.pipeworx-io/packagephobia	live status →
mcp-registry/io.github.pipeworx-io/oyez/recent_changes	io.github.pipeworx-io/oyez	live status →
mcp-registry/io.github.pipeworx-io/osv-dev/recent_changes	io.github.pipeworx-io/osv-dev	live status →
mcp-registry/io.github.pipeworx-io/opentopodata/recent_changes	io.github.pipeworx-io/opentopodata	live status →
mcp-registry/io.github.pipeworx-io/openverse/recent_changes	io.github.pipeworx-io/openverse	live status →
mcp-registry/io.github.pipeworx-io/openweather/recent_changes	io.github.pipeworx-io/openweather	live status →
mcp-registry/io.github.pipeworx-io/osv/recent_changes	io.github.pipeworx-io/osv	live status →
mcp-registry/io.github.pipeworx-io/opentopography/recent_changes	io.github.pipeworx-io/opentopography	live status →
mcp-registry/io.github.pipeworx-io/zippopotam/recent_changes	io.github.pipeworx-io/zippopotam	live status →
mcp-registry/io.github.pipeworx-io/yc-rejection/recent_changes	io.github.pipeworx-io/yc-rejection	live status →

FAQ

What is the best alternative to mcp-registry/ac.tandem/docs-mcp/refresh_docs_index?

mcp-registry/io.github.pipeworx-io/realestate/recent_changes is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/passive-aggression/recent_changes, mcp-registry/io.github.pipeworx-io/packagephobia/recent_changes, mcp-registry/io.github.pipeworx-io/oyez/recent_changes, mcp-registry/io.github.pipeworx-io/osv-dev/recent_changes. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/ac.tandem/docs-mcp/refresh_docs_index down right now?

mcp-registry/ac.tandem/docs-mcp/refresh_docs_index's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fac.tandem%2Fdocs-mcp%2Frefresh_docs_index.

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%2Fac.tandem%2Fdocs-mcp%2Frefresh_docs_index or MCP find_alternatives. Check mcp-registry/ac.tandem/docs-mcp/refresh_docs_index's live status: https://glimind.com/tool/mcp-registry/ac.tandem/docs-mcp/refresh_docs_index.