io.github.grzesir/botspot-trading

up checked 2026-11-11T04:39:21.630Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

BotSpot: AI Trading, Backtests and Bots

Publisher-provided description

AI agents backtest, paper trade and live trade via your broker. Free to connect; OAuth.

Summary by lookupd

Lets agents run backtests, paper and live trading bots, and view positions, quotes, logs and performance via a connected broker account.

Install

Claude Code, remote (streamable-http)

claude mcp add --transport http botspot-trading https://mcp.botspot.trade/mcp

Codex, remote (streamable-http)

codex mcp add botspot-trading --url https://mcp.botspot.trade/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

{
  "mcpServers": {
    "botspot-trading": {
      "url": "https://mcp.botspot.trade/mcp"
    }
  }
}

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (showing 30 of 115)

Publisher-provided text

• commit_backtest_rules_review Commit the conversational Agent's already-completed, per-Rule evidence review for one exact terminal backtest and revision. This tool never analyzes a Rule or r
• list_backtests Summarize recent backtests for the user, optionally scoped to a strategy or conversation. For the current attached strategy, use scope='strategy' and omit id, s
• get_backtest_artifact For a live or scheduled deployment, use get_deployment_logs for runtime logs and list_deployment_artifacts/query_deployment_artifact for decisions, preserving t
• get_backtest_logs Fetch runtime logs for an identified historical backtest simulation. This tool does not read live/paper bot or scheduled-deployment logs. Use get_deployment_log
• start_parameter_experiment Start 2-10 parameter variants against the same saved revision, same date window, and same current BotSpot Auto routing policy. BotSpot creates or resolves one i
• start_backtest Start a new backtest for a revision with the provided date range. ASYNC: This starts a job and returns immediately with a backtest id. `backtest_status` and art
• stop_backtest Force-stop an in-progress backtest by ID.
• backtest_status Fetch the latest status/stage for a backtest by id. Response includes `stage` plus a rich `structuredContent.progress` snapshot of the current heartbeat: - `p
• query_csv Execute a SQL query on a backtest artifact using DuckDB. backtestId must be the actual backtest run id already discovered from list_backtests or used with get_b
• run_deployment_once HIGH RISK: request owner approval for one immediate iteration of an existing scheduled bot. Use this for run once, an extra run, or retrying a missed iteration.
• start_deployment Prepares owner review for a new BotSpot deployment; this call does not start a bot or place trades before approval. After explicit owner approval, this is HIGH
• stop_deployment HIGH RISK: stops an existing BotSpot live deployment and changes a running trading system. Stopping the wrong bot can leave real-money exposure unmanaged. Only
• update_deployment_revision HIGH RISK: updates one named BotSpot live deployment to a target saved strategy revision after owner authorization. Without an active window it creates one webs
• place_trade HIGH RISK: creates a BotSpot website approval request for a single trade that may place real-money orders after approval. Provide reason before approval: at lea
• get_deployment_action_status Returns the status of a pending or completed deployment authorization request created by start_deployment, stop_deployment, update_deployment_revision, run_depl
• get_single_trade_status Read-only approval and execution status for a direct trade or an existing-order cancel/modify request. Pass the actionId returned by place_trade, broker_orders(
• list_deployments Returns the user's deployments with each row's own paper/live mode, linked broker and performance data. Never transfer performance between same-named paper and
• get_deployment_logs Returns CloudWatch logs from a live deployment's container. Supports time-range filtering (startTimeIso/endTimeIso), CloudWatch filter patterns (query), local m
• list_deployment_runs Lists owner-scoped artifact runs for one live/scheduled deployment, or for up to 10 related deployments via deploymentIds. Every returned row includes deploymen
• list_deployment_artifacts Returns the manifest for the latest or specified deployment run, including artifact kinds, keys, sizes, row counts, timestamps, symbols, queryability, visibilit
• get_deployment_artifact Returns a short-lived signed URL for one manifest-listed deployment artifact. Owner-scoped and manifest-only: never pass arbitrary S3 keys. Prefer query_deploym
• query_deployment_artifact Runs a read-only DuckDB SELECT against queryable deployment artifacts listed in the run manifest. For replacement-deployment history, pass up to 10 exact {deplo
• get_broker_quotes Read-only: fetches current quote/last-price data from the signed-in user's saved broker connection. Pass brokerCredentialId, or omit it only when the user has e
• get_broker_positions Read-only: fetches current positions directly from saved broker credentials, not from deployment telemetry or snapshot automation. For current performance of a
• get_broker_account_snapshot Read-only: fetches current cash, buying power, and account value from the signed-in user's saved broker connection. For current performance of a named bot or a
• get_bot_performance Returns recorded performance snapshots for a live deployment's bot, including total return, max drawdown, Sharpe ratio, and portfolio value over time. The hours
• get_deployment_position_telemetry A saved-code-only edit does not require live orders or positions. Implement confirmed-fill handling in the strategy runtime without inventing a current fill or
• get_portfolio_series Returns the owned linked-account history plus a fresh direct broker balance through the same canonical source used by Python internal_data.get. This is the whol
• get_deployment_order_telemetry A saved-code-only edit does not require live orders or positions. Implement confirmed-fill handling in the strategy runtime without inventing a current fill or
• create_strategy Creates a new strategy workspace with main.py and requirements.txt. The starter files are neutral boilerplate only; they do not encode customer-specific strateg

Details

• Version: 1.1.2
• Transports: streamable-http
• Uptime (7 days): 100%
• Median latency: 221 ms
• First indexed: 2026-11-01T09:32:08.877Z
• Last seen in registry: 2026-11-01T09:32:08.913Z
• Repository: https://github.com/Lumiwealth/botspot-mcp

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/io.github.grzesir/botspot-trading.svg)](https://lookupd.com/servers/io.github.grzesir/botspot-trading)

• 62092 servers
• Last crawl: 2026-11-11T17:17:22.074Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp