backtest_rule — Sardine: Kalshi crypto settlement history MCP Tool
backtest_rule
(backtest rule) is one of 9 tools on the
Sardine: Kalshi crypto settlement history
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call backtest_rule from your client
- Claude Code Sardine: Kalshi crypto settlement history backtest_rule run in your project directory
- Claude Desktop Sardine: Kalshi crypto settlement history backtest_rule ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Sardine: Kalshi crypto settlement history backtest_rule ~/.cursor/mcp.json
- VS Code Sardine: Kalshi crypto settlement history backtest_rule .vscode/mcp.json
- Zed Sardine: Kalshi crypto settlement history backtest_rule ~/.config/zed/settings.json
- Windsurf Sardine: Kalshi crypto settlement history backtest_rule ~/.codeium/windsurf/mcp_config.json
- Cline Sardine: Kalshi crypto settlement history backtest_rule ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Sardine: Kalshi crypto settlement history backtest_rule ~/.gemini/settings.json
- Grok Sardine: Kalshi crypto settlement history backtest_rule .mcp.json (in your project root)
- ChatGPT Sardine: Kalshi crypto settlement history backtest_rule Settings → Connectors → Advanced → Developer mode
- Claude.ai Sardine: Kalshi crypto settlement history backtest_rule Settings → Connectors → Add custom connector
- LangChain Sardine: Kalshi crypto settlement history backtest_rule pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http sardine https://sardine.info/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.