Skip to content

VS Code Sardine: Kalshi crypto settlement history backtest_rule

How to: VS Code Sardine: Kalshi crypto settlement history backtest_rule

client:VS Code transport:streamable-http tool:backtest_rule

Add Sardine: Kalshi crypto settlement history to VS Code

  1. 01

    Open .vscode/mcp.json and merge this in. Keep any servers already there.

{
  "servers": {
    "sardine": {
      "type": "http",
      "url": "https://sardine.info/mcp"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

    Ask for something backtest_rule does. VS Code lists the server's tools on connect and calls backtest_rule itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Sardine: Kalshi crypto settlement history's identifier in your config matches the one above exactly.

Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs

Set these first

Sardine: Kalshi crypto settlement history will not start until these are set, so backtest_rule never becomes available.

  • SARDINE_API_KEY

Same tool, other clients

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.