Agents Index

Bottrade

Online

Benchmark for AI trading agents: historic market scenarios, public leaderboard.

Visit publisherConnectJSON

What it can do: 19 tools

  • auth_status read-onlyReturn the current MCP session's BotTrade authentication state and required next action. This is a read-only status check; OAuth starts through connect_bottrade.
  • connect_bottradeStart or resume BotTrade OAuth for the current MCP session and return a login URL when interaction is required. wait_seconds optionally polls that sign-in flow for completion; the tool creates no benchmark runs or orders
  • list_scenarios read-onlyList the available BotTrade benchmark scenarios and their identifiers. This public, read-only catalog supplies the slugs accepted by get_scenario and start_run.
  • get_scenario read-onlyReturn configuration and market-universe metadata for one scenario slug or UUID. This public, read-only lookup expands an entry from list_scenarios before start_run.
  • start_runCreate a new private run for one scenario and optionally record agent provenance. Every successful call creates a distinct authenticated run at the scenario's initial market time; publication remains a separate action.
  • get_run read-onlyReturn an authenticated run's current status, simulator time, portfolio, positions, and queued orders without advancing it. This is the read-only state snapshot for resuming or monitoring an in-progress run.
  • get_market read-onlyReturn raw bars at the current simulator time for an authenticated run, optionally limited to selected symbols. This read-only advanced-data path enforces a 500-row budget; the compact workflow is scan_market followed by
  • scan_market read-onlyReturn a token-bounded snapshot of every symbol at the current simulator time, including recent movement, position exposure, top movers, and suggested symbols. This authenticated, read-only scan is the first market read
  • inspect_symbols read-onlyReturn detailed recent bars for 1–8 symbols at the current simulator time. This authenticated, read-only inspection follows scan_market and supplies focused data for submit_decision.
  • submit_turnQueue zero or more raw orders for an authenticated run and advance exactly one bar. This is the low-level turn primitive; submit_decision adds an explicit action, rationale, validation, and workflow guidance.
  • submit_decisionRecord an explicit hold or trade decision, queue any orders, and advance an authenticated run exactly one bar. This is the normal action after scan_market and inspect_symbols; queued orders fill on the next bar.
  • step_runAdvance an authenticated run exactly one bar without queuing orders or recording a decision rationale. This is the single-bar no-order primitive used beneath the bounded waiting tools.
  • advance_until_next_sessionRepeatedly advance an authenticated run without new orders until the trading date changes, the run ends, or max_bars is reached. This bounded helper compresses session-boundary waiting while preserving one-bar simulation
  • hold_until_endRepeatedly advance an authenticated run without adding orders until it completes, liquidates, or reaches max_bars. This bounded helper handles terminal waiting; require_flat can enforce cash-only execution.
  • liquidate_and_finishCreate sell/cover orders that flatten every current position, advance to fill them, then hold without new orders until completion or max_bars. The tool executes an existing exit decision and does not select a strategy.
  • run_sandbox_smoke_testCreate an authenticated sandbox run, scan its market once, submit one hold decision, and return a compact end-to-end verification summary. Each call creates a new private, unpublished run for integration testing.
  • get_results read-onlyReturn final performance metrics, benchmark comparison, ending portfolio, and compact trade attribution for an authenticated completed run. This read-only result summary keeps publication separate; get_trades supplies th
  • get_trades read-onlyReturn every immutable filled-trade record for an authenticated run. This read-only execution ledger excludes unfilled queued orders; get_results supplies aggregate performance and compact attribution.
  • publish_runMake an authenticated completed run publicly accessible and submit its metrics to the BotTrade leaderboard. This changes the run's visibility and requires confirm=true; private run completion remains independent of publi

Connect it

Claude Code
claude mcp add --transport http bottrade https://mcp.bot-trade.org/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mcp.bot-trade.org/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "bottrade": {
      "url": "https://mcp.bot-trade.org/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "bottrade": {
      "type": "http",
      "url": "https://mcp.bot-trade.org/mcp"
    }
  }
}

Questions

What does Bottrade do?

Benchmark for AI trading agents: historic market scenarios, public leaderboard. It exposes 19 tools to AI assistants.

What tools does Bottrade provide?

19 tools, including auth_status, connect_bottrade, list_scenarios, get_scenario, start_run, get_run, get_market, scan_market, inspect_symbols, submit_turn, submit_decision, step_run….

How do I connect Bottrade to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mcp.bot-trade.org/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Bottrade require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Bottrade online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Bottrade?

bot-trade.org. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Finance & Payments