mcp-registry/ai.sugra/api-mcp/fetch_data / alternatives

Live alternatives to mcp-registry/ai.sugra/api-mcp/fetch_data

The best live alternatives to mcp-registry/ai.sugra/api-mcp/fetch_data right now are mcp-registry/io.github.branch-docs/ai/search-endpoints, mcp-registry/io.github.vybenetwork/vybe-solana-api/search-endpoints, mcp-registry/com.claidex/failure-intelligence/fetch, mcp-registry/io.github.branch-docs/ai/fetch, mcp-registry/io.github.pipeworx-io/nvd/search_within — capability-matched and ranked by current reliability. mcp-registry/ai.sugra/api-mcp/fetch_data itself is currently "healthy".

alternativeserver
mcp-registry/io.github.branch-docs/ai/search-endpointsio.github.branch-docs/ailive status →
mcp-registry/io.github.vybenetwork/vybe-solana-api/search-endpointsio.github.vybenetwork/vybe-solana-apilive status →
mcp-registry/com.claidex/failure-intelligence/fetchcom.claidex/failure-intelligencelive status →
mcp-registry/io.github.branch-docs/ai/fetchio.github.branch-docs/ailive status →
mcp-registry/io.github.pipeworx-io/nvd/search_withinio.github.pipeworx-io/nvdlive status →
mcp-registry/io.github.pipeworx-io/medlineplus/search_withinio.github.pipeworx-io/medlinepluslive status →
mcp-registry/io.github.pipeworx-io/jsdelivr/search_withinio.github.pipeworx-io/jsdelivrlive status →
mcp-registry/io.github.pipeworx-io/itunes-search/search_withinio.github.pipeworx-io/itunes-searchlive status →
mcp-registry/io.github.pipeworx-io/itis/search_withinio.github.pipeworx-io/itislive status →
mcp-registry/io.github.pipeworx-io/ine-pt/search_withinio.github.pipeworx-io/ine-ptlive status →
mcp-registry/io.github.pipeworx-io/n2yo/search_withinio.github.pipeworx-io/n2yolive status →
mcp-registry/io.github.pipeworx-io/arcgis-mobile/search_withinio.github.pipeworx-io/arcgis-mobilelive status →

FAQ

What is the best alternative to mcp-registry/ai.sugra/api-mcp/fetch_data?

mcp-registry/io.github.branch-docs/ai/search-endpoints is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.vybenetwork/vybe-solana-api/search-endpoints, mcp-registry/com.claidex/failure-intelligence/fetch, mcp-registry/io.github.branch-docs/ai/fetch, mcp-registry/io.github.pipeworx-io/nvd/search_within. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/ai.sugra/api-mcp/fetch_data down right now?

mcp-registry/ai.sugra/api-mcp/fetch_data's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fai.sugra%2Fapi-mcp%2Ffetch_data.

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.sugra%2Fapi-mcp%2Ffetch_data or MCP find_alternatives. Check mcp-registry/ai.sugra/api-mcp/fetch_data's live status: https://glimind.com/tool/mcp-registry/ai.sugra/api-mcp/fetch_data.