mcp-registry/io.github.wnsod/oneqaz-trading-mcp/get_backtest_tuning_state / alternatives

Live alternatives to mcp-registry/io.github.wnsod/oneqaz-trading-mcp/get_backtest_tuning_state

The best live alternatives to mcp-registry/io.github.wnsod/oneqaz-trading-mcp/get_backtest_tuning_state right now are mcp-registry/io.github.midasflowai-lab/midasflow-mcp-quickstart/backtest, mcp-registry/io.github.raviolelabs/predmcp/get_signal_backtest, mcp-registry/io.github.timwal78/mcp-x402/backtest_run, mcp-registry/io.github.midasflowai-lab/midasflow-mcp-quickstart/get_accuracy, mcp-registry/vc.doomscore/doom/record_outcome — capability-matched and ranked by current reliability. mcp-registry/io.github.wnsod/oneqaz-trading-mcp/get_backtest_tuning_state itself is currently "healthy".

alternative	server
mcp-registry/io.github.midasflowai-lab/midasflow-mcp-quickstart/backtest	io.github.midasflowai-lab/midasflow-mcp-quickstart	live status →
mcp-registry/io.github.raviolelabs/predmcp/get_signal_backtest	io.github.RavioleLabs/predmcp	live status →
mcp-registry/io.github.timwal78/mcp-x402/backtest_run	io.github.Timwal78/mcp-x402	live status →
mcp-registry/io.github.midasflowai-lab/midasflow-mcp-quickstart/get_accuracy	io.github.midasflowai-lab/midasflow-mcp-quickstart	live status →
mcp-registry/vc.doomscore/doom/record_outcome	vc.doomscore/doom	live status →
mcp-registry/finance.shibui/data/load_backtesting_workflow	finance.shibui/data	live status →
mcp-registry/com.claribi/mcp-server/get_forecast_trust	com.claribi/mcp-server	live status →
mcp-registry/io.github.raviolelabs/predmcp/get_signal_performance	io.github.RavioleLabs/predmcp	live status →
mcp-registry/io.github.timwal78/mcp-x402/backtest_validate	io.github.Timwal78/mcp-x402	live status →
mcp-registry/dev.xpansion/xfms/benchmark	dev.xpansion/xfms	live status →
mcp-registry/io.github.jaideepdhanoa/vocab-voyage/get_session_trends	io.github.jaideepdhanoa/vocab-voyage	live status →
mcp-registry/io.tooloracle/ampel/score_trend	io.tooloracle/ampel	live status →

FAQ

What is the best alternative to mcp-registry/io.github.wnsod/oneqaz-trading-mcp/get_backtest_tuning_state?

mcp-registry/io.github.midasflowai-lab/midasflow-mcp-quickstart/backtest is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.raviolelabs/predmcp/get_signal_backtest, mcp-registry/io.github.timwal78/mcp-x402/backtest_run, mcp-registry/io.github.midasflowai-lab/midasflow-mcp-quickstart/get_accuracy, mcp-registry/vc.doomscore/doom/record_outcome. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.wnsod/oneqaz-trading-mcp/get_backtest_tuning_state down right now?

mcp-registry/io.github.wnsod/oneqaz-trading-mcp/get_backtest_tuning_state's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.wnsod%2Foneqaz-trading-mcp%2Fget_backtest_tuning_state.

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.wnsod%2Foneqaz-trading-mcp%2Fget_backtest_tuning_state or MCP find_alternatives. Check mcp-registry/io.github.wnsod/oneqaz-trading-mcp/get_backtest_tuning_state's live status: https://glimind.com/tool/mcp-registry/io.github.wnsod/oneqaz-trading-mcp/get_backtest_tuning_state.