Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

org.bot-trade/bottrade

REMOTE · MCP.BOT-TRADE.ORG

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

0 this week 89 Trust /100

Last scanned (9 hours ago)

Scores higher than 97% of remote servers

Unreachable for 2 days in a row. Last reached 3 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (3)

  • HTTPS
  • DNSSEC
  • Transport

Checks we could not complete (8)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Schema quality: 67 → unverified ▼ functional
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 15 Oct 26 +66
    • Authorization: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 67 ▲ functional
  • 14 Oct 26 −66
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Schema quality: 67 → unverified ▼ functional
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://mcp.bot-trade.org/mcp

TLS unreached
DNSSEC insecure

Validation of mcp.bot-trade.org. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725, 26974 8, 8 Verified
bot-trade.org. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.bot-trade.org/mcp Unreachable
http (plaintext) http://mcp.bot-trade.org/mcp HTTPS enforced
MCP tools · 19 exposed · ~1,633 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
advance_until_next_session ~93

Repeatedly 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 steps.

NameTypeReqDescription
max_barsinteger–Maximum one-bar advances before stopping; defaults to 32 and acts as a safety cap.
run_idstringyesRun UUID returned by start_run.

No output schema declared.

No examples provided.

auth_status ~38

Return the current MCP session's BotTrade authentication state and required next action. This is a read-only status check; OAuth starts through connect_bottrade.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

connect_bottrade ~87

Start 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.

NameTypeReqDescription
wait_secondsinteger–Optional seconds to poll for OAuth completion before returning; values above 120 are capped at 120. Use 0 to return the current status immediately.

No output schema declared.

No examples provided.

get_market ~123

Return 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 inspect_symbols.

NameTypeReqDescription
lookbackinteger–Number of bars to return per symbol; the total request must remain within the server's 500-row budget.
run_idstringyesRun UUID returned by start_run.
symbolsarray–Optional symbol subset. Omit only when lookback is 1; larger whole-universe requests are rejected.

No output schema declared.

No examples provided.

get_results ~62

Return 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 the full execution ledger.

NameTypeReqDescription
run_idstringyesCompleted run UUID returned by start_run.

No output schema declared.

No examples provided.

get_run ~61

Return 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.

NameTypeReqDescription
run_idstringyesRun UUID returned by start_run.

No output schema declared.

No examples provided.

get_scenario ~61

Return 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.

NameTypeReqDescription
id_or_slugstringyesExact scenario slug or UUID returned by list_scenarios.

No output schema declared.

No examples provided.

get_trades ~55

Return 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.

NameTypeReqDescription
run_idstringyesRun UUID returned by start_run.

No output schema declared.

No examples provided.

hold_until_end ~116

Repeatedly 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.

NameTypeReqDescription
max_barsinteger–Maximum one-bar advances before stopping; defaults to 256 and acts as a safety cap.
require_flatboolean–When true, reject the call unless the run has no open positions; use this guard for cash-only waiting.
run_idstringyesRun UUID returned by start_run.

No output schema declared.

No examples provided.

inspect_symbols ~105

Return 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.

NameTypeReqDescription
lookbackinteger–Bars per symbol; defaults to 30 when omitted and is capped at 120.
run_idstringyesRun UUID returned by start_run.
symbolsarrayyesBetween 1 and 8 symbols, normally selected from scan_market.suggested_inspection.

No output schema declared.

No examples provided.

liquidate_and_finish ~105

Create 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.

NameTypeReqDescription
max_barsinteger–Maximum post-liquidation one-bar advances before stopping; defaults to 256.
rationalestring–Optional short reason copied onto the generated exit orders.
run_idstringyesRun UUID returned by start_run.

No output schema declared.

No examples provided.

list_scenarios ~40

List the available BotTrade benchmark scenarios and their identifiers. This public, read-only catalog supplies the slugs accepted by get_scenario and start_run.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

publish_run ~79

Make 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 publication.

NameTypeReqDescription
confirmbooleanyesExplicit publication confirmation; the server rejects the call unless this is true.
run_idstringyesCompleted run UUID returned by start_run.

No output schema declared.

No examples provided.

run_sandbox_smoke_test ~89

Create 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.

NameTypeReqDescription
bot_namestring–Optional display name recorded on the sandbox run.
scenario_slugstring–Sandbox scenario slug; defaults to sandbox-nov-2024 when omitted.

No output schema declared.

No examples provided.

scan_market ~67

Return 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 in each trading step.

NameTypeReqDescription
run_idstringyesRun UUID returned by start_run.

No output schema declared.

No examples provided.

start_run ~101

Create 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.

NameTypeReqDescription
agent_infoobject–Optional structured provenance for the agent executing the run.
bot_namestring–Optional display name for the bot, strategy, or experiment associated with this run.
scenario_slugstringyesExact scenario slug returned by list_scenarios.

No output schema declared.

No examples provided.

step_run ~83

Advance 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.

NameTypeReqDescription
countinteger–Bars to advance. Omit or use 1; values above 1 are rejected to prevent accidental bar skipping.
run_idstringyesRun UUID returned by start_run.

No output schema declared.

No examples provided.

submit_decision ~152

Record 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.

NameTypeReqDescription
actionstringyesDecision type: hold requires no orders; trade requires at least one order.
ordersarrayyesOrders to queue when action is trade; use an empty array when action is hold.
rationalestring–Optional short reason recorded with the decision.
run_idstringyesRun UUID returned by start_run.
step_countinteger–Bars to advance. Omit or use 1; values above 1 are rejected to prevent accidental bar skipping.

No output schema declared.

No examples provided.

submit_turn ~116

Queue 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.

NameTypeReqDescription
run_idstringyesRun UUID returned by start_run.
step_countinteger–Bars to advance. Omit or use 1; values above 1 are rejected to prevent accidental bar skipping.
tradesarrayyesOrders to queue before the next bar; an empty array means advance without placing an order.

No output schema declared.

No examples provided.

Install

How do I install the org.bot-trade/bottrade MCP server?

org.bot-trade/bottrade is a hosted endpoint at https://mcp.bot-trade.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.bot-trade.org

# add to Claude Code
claude mcp add --transport http org-bot-trade-bottrade 'https://mcp.bot-trade.org/mcp'
Common questions

What is the org.bot-trade/bottrade MCP server?

org.bot-trade/bottrade is an MCP server listed in the public MCP registry as org.bot-trade/bottrade. Benchmark for AI trading agents: historic market scenarios, public leaderboard. This page covers its hosted endpoint (https://mcp.bot-trade.org/mcp).

Is the org.bot-trade/bottrade MCP server safe to use?

org.bot-trade/bottrade scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the org.bot-trade/bottrade MCP server expose?

org.bot-trade/bottrade exposes 19 tools: auth_status, connect_bottrade, list_scenarios, get_scenario, start_run, and 14 more. Their descriptions and schemas cost roughly 1,633 tokens of context every time the server is loaded.

Does the org.bot-trade/bottrade MCP server require authentication?

Its publisher declares no required credentials for org.bot-trade/bottrade. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the org.bot-trade/bottrade MCP server still maintained?

org.bot-trade/bottrade is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the org.bot-trade/bottrade MCP server?

VerifyMCP ran 3 checks on org.bot-trade/bottrade, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about org.bot-trade/bottrade: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.