Model Context Protocol

Use StratProof from inside Claude

StratProof exposes its core tools via the Model Context Protocol. Add us as a custom connector in Claude Desktop (or any MCP client) and you can call our tools directly from a conversation. No signup, no auth.

One-click install

Install via Smithery

Listed in the Smithery MCP directory. Their gateway handles Claude Desktop config and adds usage observability. Fastest option if you already have a Smithery account.

Open on Smithery →

Prefer to paste the URL directly into Claude Desktop, Cursor, or Claude Code? Use the manual instructions below.

Available tools

  • prove_strategy : honest backtest of any strategy description against 3 years of real Binance data
  • get_live_proof : current v1 vs v2 live paper-trading stats
  • get_research_findings : aggregated output from 7,000+ tested candidates
  • get_regime_insights : regime classifier validation (Welch t-test, nightly)
  • get_shootout_results : 20 popular strategies tested with honest fees
  • get_stats : site-wide meta stats

Claude Desktop

  1. Settings → Connectors, then Add custom connector.
  2. Name: StratProof
  3. URL: https://stratproof.com/api/mcp
  4. Leave OAuth fields blank. Our MCP tools are public.
  5. Quit and restart Claude Desktop fully (tray icon, Quit, not just close the window).

Once restarted, ask Claude: “Test this strategy through StratProof: Buy ETH when RSI drops below 30, sell above 70.” Claude will call prove_strategy, get a verdict, and explain it.

Cursor

Settings → MCP → Add new global MCP server:

{
  "stratproof": {
    "url": "https://stratproof.com/api/mcp"
  }
}

Claude Code CLI

claude mcp add --transport http stratproof https://stratproof.com/api/mcp

Troubleshooting

  • Tools did not appear after adding the connector. Most likely you did not fully quit Claude Desktop. Right-click the system tray / dock icon, Quit, then reopen.
  • Tool calls time out. prove_strategy can take 8-20 seconds because it runs an actual backtest. Server-side timeout is 60s. If it is timing out consistently, try get_stats first to confirm the service is live.
  • HTTP 401 / 403. Our MCP endpoint is public and does not use OAuth. Remove any OAuth config for this connector.

What is not exposed

User account endpoints (saved strategies, history) and owner-only dashboards are intentionally not in the MCP server. If you think a tool belongs here that is not listed, email [email protected].