vike-cli runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 15 Sep 2026.
Backtest, validate and execute trading strategies behind a mandatory two-call preview gate.
What the code does
We read the source, 19 h ago · rules 3dff92dd89df
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
`rm -r sma_cross/` removes the whole thing, and two strategies' presets can never be confused.
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
let url = format!("https://api.telegram.org/bot{token}/sendMessage");
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found things in this code
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch vike-cli and you get told the day something new turns up.
Alternatives to vike-cli
same job, measured the same wayBuild, backtest, and deploy crypto trading strategies via MCP with 7-stage validation.
AI-powered crypto trading tools. Strategies, backtests, bots, and portfolio management.
Search 5,000+ trading papers with verified backtests, strategies, datasets, and courses.
Mine, validate and paper-trade quantitative trading strategies. The engine runs on your machine.
Automate trading on your own Alpaca account - build, backtest and run strategies via your AI.
Market regime, execution-cost, bar-QC and backtest-audit tools for agents. Pay per call via x402.
Backtest trading ideas and inspect strategies, trades and results. OAuth; invite-only beta.
Build, backtest, and deploy quantitative trading strategies from your AI agent.
vike-cli — questions
Answers built from our own checks of this server.