mcp-registry/io.github.jorgeperez0825/v12-dfs/slate_health / alternatives

Live alternatives to mcp-registry/io.github.jorgeperez0825/v12-dfs/slate_health

The best live alternatives to mcp-registry/io.github.jorgeperez0825/v12-dfs/slate_health right now are mcp-registry/dev.infersports/infersports/scan_slate, mcp-registry/com.olympus-bets/olympus-bets-analytics/get_game_recommendation, mcp-registry/com.olympus-bets/olympus-bets-analytics/get_league_schedule, mcp-registry/com.voxodds/voxodds/get_world_cup_matchday, mcp-registry/io.github.rotwang9000/seneschal-data/seneschal_health — capability-matched and ranked by current reliability. mcp-registry/io.github.jorgeperez0825/v12-dfs/slate_health itself is currently "healthy".

alternative	server
mcp-registry/dev.infersports/infersports/scan_slate	dev.infersports/infersports	live status →
mcp-registry/com.olympus-bets/olympus-bets-analytics/get_game_recommendation	com.olympus-bets/olympus-bets-analytics	live status →
mcp-registry/com.olympus-bets/olympus-bets-analytics/get_league_schedule	com.olympus-bets/olympus-bets-analytics	live status →
mcp-registry/com.voxodds/voxodds/get_world_cup_matchday	com.voxodds/voxodds	live status →
mcp-registry/io.github.rotwang9000/seneschal-data/seneschal_health	io.github.Rotwang9000/seneschal-data	live status →
mcp-registry/com.olympus-bets/olympus-bets-analytics/get_performance_summary	com.olympus-bets/olympus-bets-analytics	live status →
mcp-registry/com.bonissystems/trustai-verify/get_health	com.bonissystems/trustai-verify	live status →
mcp-registry/com.olympus-bets/olympus-bets-analytics/get_todays_projections	com.olympus-bets/olympus-bets-analytics	live status →
mcp-registry/ai.intuitek.the-stall/the-stall/sports-prediction	ai.intuitek.the-stall/the-stall	live status →
mcp-registry/io.github.nhoverte/biocosm/get_staleness_report	io.github.nhoverte/biocosm	live status →
mcp-registry/dev.depscope/mcp/get_health_score	dev.depscope/mcp	live status →
mcp-registry/cn.whylingxi/insurance/get_schema	cn.whylingxi/insurance	live status →

FAQ

What is the best alternative to mcp-registry/io.github.jorgeperez0825/v12-dfs/slate_health?

mcp-registry/dev.infersports/infersports/scan_slate is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.olympus-bets/olympus-bets-analytics/get_game_recommendation, mcp-registry/com.olympus-bets/olympus-bets-analytics/get_league_schedule, mcp-registry/com.voxodds/voxodds/get_world_cup_matchday, mcp-registry/io.github.rotwang9000/seneschal-data/seneschal_health. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.jorgeperez0825/v12-dfs/slate_health down right now?

mcp-registry/io.github.jorgeperez0825/v12-dfs/slate_health's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.jorgeperez0825%2Fv12-dfs%2Fslate_health.

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.jorgeperez0825%2Fv12-dfs%2Fslate_health or MCP find_alternatives. Check mcp-registry/io.github.jorgeperez0825/v12-dfs/slate_health's live status: https://glimind.com/tool/mcp-registry/io.github.jorgeperez0825/v12-dfs/slate_health.