mcp-registry/io.github.foomworks/fresh-feeds/get_mcp_registry_snapshot / alternatives

Live alternatives to mcp-registry/io.github.foomworks/fresh-feeds/get_mcp_registry_snapshot

The best live alternatives to mcp-registry/io.github.foomworks/fresh-feeds/get_mcp_registry_snapshot right now are mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_mcp_asset_inventory_risk_register, mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_mcp_entitlement_receipt_gateway, mcp-registry/com.ontarioprotocol/ontario-protocol/mcp_endpoint_owner_next_step, mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_mcp_tool_revenue_share_ledger, mcp-registry/io.github.spacemandomains/mcp-registry-search/get_mcp_server_details — capability-matched and ranked by current reliability. mcp-registry/io.github.foomworks/fresh-feeds/get_mcp_registry_snapshot itself is currently "healthy".

alternative	server
mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_mcp_asset_inventory_risk_register	xyz.558686.gpt55/token-gateway	live status →
mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_mcp_entitlement_receipt_gateway	xyz.558686.gpt55/token-gateway	live status →
mcp-registry/com.ontarioprotocol/ontario-protocol/mcp_endpoint_owner_next_step	com.ontarioprotocol/ontario-protocol	live status →
mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_mcp_tool_revenue_share_ledger	xyz.558686.gpt55/token-gateway	live status →
mcp-registry/io.github.spacemandomains/mcp-registry-search/get_mcp_server_details	io.github.Spacemandomains/mcp-registry-search	live status →
mcp-registry/io.github.virgen101/xportalx/mcp_pricing	io.github.virgen101/xportalx	live status →
mcp-registry/online.sasame/research/readiness_report	online.sasame/research	live status →
mcp-registry/io.github.spacemandomains/library-mcp/inspect	io.github.Spacemandomains/library-mcp	live status →
mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_seller_intelligence_bundle	xyz.558686.gpt55/token-gateway	live status →
mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_seller_intelligence_bundle_get	xyz.558686.gpt55/token-gateway	live status →
mcp-registry/io.github.jsonbored/heyclaude/registry.info	io.github.JSONbored/heyclaude	live status →
mcp-registry/io.github.bobjonesgood/x402nano/get_market_pricing	io.github.Bobjonesgood/x402nano	live status →

FAQ

What is the best alternative to mcp-registry/io.github.foomworks/fresh-feeds/get_mcp_registry_snapshot?

mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_mcp_asset_inventory_risk_register is the top capability-matched alternative that's live right now. Other options: mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_mcp_entitlement_receipt_gateway, mcp-registry/com.ontarioprotocol/ontario-protocol/mcp_endpoint_owner_next_step, mcp-registry/xyz.558686.gpt55/token-gateway/gpt55_x402_mcp_tool_revenue_share_ledger, mcp-registry/io.github.spacemandomains/mcp-registry-search/get_mcp_server_details. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.foomworks/fresh-feeds/get_mcp_registry_snapshot down right now?

mcp-registry/io.github.foomworks/fresh-feeds/get_mcp_registry_snapshot's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.foomworks%2Ffresh-feeds%2Fget_mcp_registry_snapshot.

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.foomworks%2Ffresh-feeds%2Fget_mcp_registry_snapshot or MCP find_alternatives. Check mcp-registry/io.github.foomworks/fresh-feeds/get_mcp_registry_snapshot's live status: https://glimind.com/tool/mcp-registry/io.github.foomworks/fresh-feeds/get_mcp_registry_snapshot.