mcp-registry/io.github.pipeworx-io/opendota/search_players / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/opendota/search_players

The best live alternatives to mcp-registry/io.github.pipeworx-io/opendota/search_players right now are mcp-registry/io.github.pipeworx-io/stratz/player, mcp-registry/io.github.pipeworx-io/stratz/player_matches, mcp-registry/io.github.pipeworx-io/cricket/search_players, mcp-registry/io.github.pipeworx-io/thesportsdb/search_players, mcp-registry/io.github.pipeworx-io/steam/player_summaries — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/opendota/search_players itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/stratz/player	io.github.pipeworx-io/stratz	live status →
mcp-registry/io.github.pipeworx-io/stratz/player_matches	io.github.pipeworx-io/stratz	live status →
mcp-registry/io.github.pipeworx-io/cricket/search_players	io.github.pipeworx-io/cricket	live status →
mcp-registry/io.github.pipeworx-io/thesportsdb/search_players	io.github.pipeworx-io/thesportsdb	live status →
mcp-registry/io.github.pipeworx-io/steam/player_summaries	io.github.pipeworx-io/steam	live status →
mcp-registry/io.github.pipeworx-io/steam/player_summary	io.github.pipeworx-io/steam	live status →
mcp-registry/io.github.pipeworx-io/stratz/match	io.github.pipeworx-io/stratz	live status →
mcp-registry/io.github.pipeworx-io/bungie/search_destiny_player	io.github.pipeworx-io/bungie	live status →
mcp-registry/app.flaim/mcp/get_players	app.flaim/mcp	live status →
mcp-registry/io.github.pipeworx-io/nba/get_player	io.github.pipeworx-io/nba	live status →
mcp-registry/io.github.pipeworx-io/lichess/user	io.github.pipeworx-io/lichess	live status →
mcp-registry/io.github.pipeworx-io/riot-games/account_by_puuid	io.github.pipeworx-io/riot-games	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/opendota/search_players?

mcp-registry/io.github.pipeworx-io/stratz/player is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/stratz/player_matches, mcp-registry/io.github.pipeworx-io/cricket/search_players, mcp-registry/io.github.pipeworx-io/thesportsdb/search_players, mcp-registry/io.github.pipeworx-io/steam/player_summaries. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/opendota/search_players down right now?

mcp-registry/io.github.pipeworx-io/opendota/search_players's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fopendota%2Fsearch_players.

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.pipeworx-io%2Fopendota%2Fsearch_players or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/opendota/search_players's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/opendota/search_players.