Skip to content

VS Code trading signals mcp backtest_opening_range_breakout

How to: VS Code trading signals mcp backtest_opening_range_breakout

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

Add trading signals mcp to VS Code

  1. 01

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

{
  "servers": {
    "trading-signals-mcp": {
      "type": "http",
      "url": "https://signals.incomefather.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that trading signals mcp'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

trading signals mcp will not start until these are set, so backtest_opening_range_breakout never becomes available.

  • X402_PRIVATE_KEY
  • MAX_USD_PER_CALL
  • TRADING_SIGNALS_BASE_URL

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 11 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.