mcp-registry/io.github.pipeworx-io/riot-games/match_timeline / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/riot-games/match_timeline

The best live alternatives to mcp-registry/io.github.pipeworx-io/riot-games/match_timeline right now are mcp-registry/io.github.pipeworx-io/stratz/match, mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/tos_watch_timeline, mcp-registry/io.github.pipeworx-io/thesportsdb/team_events_last, mcp-registry/io.github.cuecrux/vaultcrux-memory-core/build_timeline, mcp-registry/io.github.pipeworx-io/opendota/pro_matches — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/riot-games/match_timeline itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/stratz/match	io.github.pipeworx-io/stratz	live status →
mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/tos_watch_timeline	com.mcp-revenue-empire/japan-public-ledgers	live status →
mcp-registry/io.github.pipeworx-io/thesportsdb/team_events_last	io.github.pipeworx-io/thesportsdb	live status →
mcp-registry/io.github.cuecrux/vaultcrux-memory-core/build_timeline	io.github.CueCrux/vaultcrux-memory-core	live status →
mcp-registry/io.github.pipeworx-io/opendota/pro_matches	io.github.pipeworx-io/opendota	live status →
mcp-registry/io.github.pipeworx-io/stratz/live_matches	io.github.pipeworx-io/stratz	live status →
mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/recall_watch_timeline	com.mcp-revenue-empire/japan-public-ledgers	live status →
mcp-registry/io.github.getgapup/mcp-knowledge/realtime_data_streams	io.github.getgapup/mcp-knowledge	live status →
mcp-registry/io.github.getgapup/gapup-mcp/realtime_data_streams	io.github.getgapup/gapup-mcp	live status →
mcp-registry/io.github.pipeworx-io/stratz/tournament	io.github.pipeworx-io/stratz	live status →
mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/tos_watch_get	com.mcp-revenue-empire/japan-public-ledgers	live status →
mcp-registry/io.github.fxmacrodata/fxmacrodata/event_impact_replay_task	io.github.fxmacrodata/fxmacrodata	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/riot-games/match_timeline?

mcp-registry/io.github.pipeworx-io/stratz/match is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/tos_watch_timeline, mcp-registry/io.github.pipeworx-io/thesportsdb/team_events_last, mcp-registry/io.github.cuecrux/vaultcrux-memory-core/build_timeline, mcp-registry/io.github.pipeworx-io/opendota/pro_matches. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/riot-games/match_timeline down right now?

mcp-registry/io.github.pipeworx-io/riot-games/match_timeline's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Friot-games%2Fmatch_timeline.

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%2Friot-games%2Fmatch_timeline or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/riot-games/match_timeline's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/riot-games/match_timeline.