mcp-registry/io.github.pipeworx-io/stratz/player_heroes / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/stratz/player_heroes

The best live alternatives to mcp-registry/io.github.pipeworx-io/stratz/player_heroes right now are mcp-registry/io.github.olijboyd/tomevault/get_vault_item, mcp-registry/io.github.pipeworx-io/carbon/recall, mcp-registry/io.github.pipeworx-io/openweather/recall, mcp-registry/io.github.pipeworx-io/jpl-ssd/recall, mcp-registry/io.github.pipeworx-io/owid/recall — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/stratz/player_heroes itself is currently "healthy".

alternative	server
mcp-registry/io.github.olijboyd/tomevault/get_vault_item	io.github.olijboyd/tomevault	live status →
mcp-registry/io.github.pipeworx-io/carbon/recall	io.github.pipeworx-io/carbon	live status →
mcp-registry/io.github.pipeworx-io/openweather/recall	io.github.pipeworx-io/openweather	live status →
mcp-registry/io.github.pipeworx-io/jpl-ssd/recall	io.github.pipeworx-io/jpl-ssd	live status →
mcp-registry/io.github.pipeworx-io/owid/recall	io.github.pipeworx-io/owid	live status →
mcp-registry/io.github.pipeworx-io/business-feeds/recall	io.github.pipeworx-io/business-feeds	live status →
mcp-registry/io.github.pipeworx-io/osv/recall	io.github.pipeworx-io/osv	live status →
mcp-registry/io.github.pipeworx-io/arcgis-eagan/recall	io.github.pipeworx-io/arcgis-eagan	live status →
mcp-registry/io.github.pipeworx-io/arcgis-princewilliam/recall	io.github.pipeworx-io/arcgis-princewilliam	live status →
mcp-registry/io.github.pipeworx-io/idigbio/recall	io.github.pipeworx-io/idigbio	live status →
mcp-registry/io.github.pipeworx-io/ietf-datatracker/recall	io.github.pipeworx-io/ietf-datatracker	live status →
mcp-registry/io.github.pipeworx-io/hud/recall	io.github.pipeworx-io/hud	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/stratz/player_heroes?

mcp-registry/io.github.olijboyd/tomevault/get_vault_item is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/carbon/recall, mcp-registry/io.github.pipeworx-io/openweather/recall, mcp-registry/io.github.pipeworx-io/jpl-ssd/recall, mcp-registry/io.github.pipeworx-io/owid/recall. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/stratz/player_heroes down right now?

mcp-registry/io.github.pipeworx-io/stratz/player_heroes's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fstratz%2Fplayer_heroes.

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%2Fstratz%2Fplayer_heroes or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/stratz/player_heroes's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/stratz/player_heroes.