Build & backtest Hyperliquid strategies
Keel turns your ideas into systematic strategies for Hyperliquid crypto perpetual futures (perps). Connect it to your AI, describe a strategy, and your AI builds it from Keel's strategy components, backtests it on real Hyperliquid history with fees and slippage, and explains the results. More
MCP connector Server URL https://mcp.usekeel.io/mcpCopy Login OAuth Tools Reads data21 account_ statusapp_ linkbacktest_ comparebacktest_ positionsbacktest_ summarizebacktest_ watchcomponents_ getcomponents_ get_ manycomponents_ searchconnection_ checkhelp library_ getlibrary_ listlive_ monitorplan_ usagestrategy_ diffstrategy_ getstrategy_ historystrategy_ notes_ readstrategy_ readinessstrategy_ search
Changes data6 backtest_ runlibrary_ forkstrategy_ composestrategy_ forkstrategy_ notes_ addstrategy_ restore
Deletes or can't be undone2 feedback share_ create
Skills 7 in the ChatGPT listing
Backtest and analyze Run a backtest on an existing strategy and read it: confirm the strategy, run on the strategy's default window unless the user named one, watch to terminal, present the run's view, and interpret the mechanism behind the result. Component discovery Find the Keel component(s) that implement a concept the user names: search by concept, batch the candidates' schemas, show what precedes and follows the best one. Overfit check Probe whether a backtest result is robust or curve-fit: re-run the strategy on disjoint windows and regimes the user agrees to, optionally perturb the sensitive parameters, compare the runs once, and give one verdict (ROBUST / MIXED / OVERFIT). Portfolio review Summarise the strategies running on the user's account, read-only: positions, recent fills, drawdown against backtest expectations, and anything errored or stale. Recover from error Triage repeated keel_* tool failures: capture the errors, read keel_account_status and keel_connection_check, classify by the error's code (auth, scope, quota, sync, validation rule, handoff), and propose one specific next step. Strategy creation Author a new Keel strategy from a natural-language thesis: fix path, universe and polarity; search every concept; batch-verify component types; draft the declarations and one Pipeline; dry-run until clean; save; and, when the user wants one, backtest and read the result. Strategy fork and iterate Change an existing strategy with one focused edit: the user's own strategy takes the change as its next version (earlier versions and their backtests stay in its history); a shared link or a Keel Library entry is forked first.