mcp-registry/ai.boolsai/signals/wayback_backtest / alternatives

Live alternatives to mcp-registry/ai.boolsai/signals/wayback_backtest

The best live alternatives to mcp-registry/ai.boolsai/signals/wayback_backtest right now are mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_timeline, mcp-registry/io.github.pipeworx-io/nyc-parks/polymarket_edge_tracker, mcp-registry/io.github.pipeworx-io/epo-ops/polymarket_edge_tracker, mcp-registry/io.github.pipeworx-io/epa-echo/polymarket_edge_tracker, mcp-registry/io.github.pipeworx-io/dati-it/polymarket_edge_tracker — capability-matched and ranked by current reliability. mcp-registry/ai.boolsai/signals/wayback_backtest itself is currently "healthy".

alternative	server
mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_timeline	com.mcp-revenue-empire/japan-public-ledgers	live status →
mcp-registry/io.github.pipeworx-io/nyc-parks/polymarket_edge_tracker	io.github.pipeworx-io/nyc-parks	live status →
mcp-registry/io.github.pipeworx-io/epo-ops/polymarket_edge_tracker	io.github.pipeworx-io/epo-ops	live status →
mcp-registry/io.github.pipeworx-io/epa-echo/polymarket_edge_tracker	io.github.pipeworx-io/epa-echo	live status →
mcp-registry/io.github.pipeworx-io/dati-it/polymarket_edge_tracker	io.github.pipeworx-io/dati-it	live status →
mcp-registry/io.github.pipeworx-io/futuur/polymarket_edge_tracker	io.github.pipeworx-io/futuur	live status →
mcp-registry/io.github.pipeworx-io/figma/polymarket_edge_tracker	io.github.pipeworx-io/figma	live status →
mcp-registry/io.github.pipeworx-io/whiskyhunter/polymarket_edge_tracker	io.github.pipeworx-io/whiskyhunter	live status →
mcp-registry/io.github.pipeworx-io/meteors/polymarket_edge_tracker	io.github.pipeworx-io/meteors	live status →
mcp-registry/io.github.pipeworx-io/mempool-space/polymarket_edge_tracker	io.github.pipeworx-io/mempool-space	live status →
mcp-registry/io.github.pipeworx-io/makstat-mk/polymarket_edge_tracker	io.github.pipeworx-io/makstat-mk	live status →
mcp-registry/io.github.pipeworx-io/malwarebazaar/polymarket_edge_tracker	io.github.pipeworx-io/malwarebazaar	live status →

FAQ

What is the best alternative to mcp-registry/ai.boolsai/signals/wayback_backtest?

mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_timeline is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/nyc-parks/polymarket_edge_tracker, mcp-registry/io.github.pipeworx-io/epo-ops/polymarket_edge_tracker, mcp-registry/io.github.pipeworx-io/epa-echo/polymarket_edge_tracker, mcp-registry/io.github.pipeworx-io/dati-it/polymarket_edge_tracker. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/ai.boolsai/signals/wayback_backtest down right now?

mcp-registry/ai.boolsai/signals/wayback_backtest's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fai.boolsai%2Fsignals%2Fwayback_backtest.

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%2Fai.boolsai%2Fsignals%2Fwayback_backtest or MCP find_alternatives. Check mcp-registry/ai.boolsai/signals/wayback_backtest's live status: https://glimind.com/tool/mcp-registry/ai.boolsai/signals/wayback_backtest.