mcp-registry/com.wingmanprotocol.agent/gateway/browse_back / alternatives
mcp-registry/com.wingmanprotocol.agent/gateway/browse_backThe best live alternatives to mcp-registry/com.wingmanprotocol.agent/gateway/browse_back right now are mcp-registry/io.github.pipeworx-io/nass/recall, mcp-registry/io.github.pipeworx-io/jina-reader/recall, mcp-registry/io.github.pipeworx-io/noaa-spc/recall, mcp-registry/io.github.pipeworx-io/brreg-no/recall, mcp-registry/io.github.pipeworx-io/jargon-translator/recall — capability-matched and ranked by current reliability. mcp-registry/com.wingmanprotocol.agent/gateway/browse_back itself is currently "healthy".
mcp-registry/io.github.pipeworx-io/nass/recall is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/jina-reader/recall, mcp-registry/io.github.pipeworx-io/noaa-spc/recall, mcp-registry/io.github.pipeworx-io/brreg-no/recall, mcp-registry/io.github.pipeworx-io/jargon-translator/recall. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/com.wingmanprotocol.agent/gateway/browse_back's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.wingmanprotocol.agent%2Fgateway%2Fbrowse_back.
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.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fcom.wingmanprotocol.agent%2Fgateway%2Fbrowse_back
or MCP find_alternatives. Check mcp-registry/com.wingmanprotocol.agent/gateway/browse_back's live status: https://glimind.com/tool/mcp-registry/com.wingmanprotocol.agent/gateway/browse_back.