BotSpot: AI Trading, Backtests and Bots
AI agents backtest, paper trade and live trade via your broker. Free to connect; OAuth
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: automate CI/CD pipelines.Similar tools
Listed for the same task: automate CI/CD pipelinesReviews
No review yet. Used BotSpot: AI Trading, Backtests and Bots? Be the first to help others choose.What it does
BotSpot: AI Trading, Backtests and Bots is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: devops automation. That makes it a candidate for tasks such as automate CI/CD pipelines or monitor production incidents.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://mcp.botspot.trade/mcpstreamable-http
In Claude Code: claude mcp add --transport http botspot-ai-trading-bots-backtesting https://mcp.botspot.trade/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"botspot-ai-trading-bots-backtesting": {
"url": "https://mcp.botspot.trade/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 1d agoONLINE BotSpot: AI Trading, Backtests and Bots answered an MCP connection on 16 Nov 2026 and introduced itself as botspot-mcp 0.0.0 (MCP protocol 2025-06-18).
115 tools offered to AI assistants
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 retrieves evidence. Before calling it, independently read the exact rules.json anlist_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, strategyId, and aiStrategyId. The server resolves the exact strategy from the scoget_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 the discovered deploymentId and runId. A deploymentId or deployment runId is notget_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_logs for those runtime logs and list_deployment_artifacts/query_deployment_artifactstart_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 immutable strategy parameter set per variant and starts the runs in parallel withstart_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 artifact tools expose the current state for that id. Backtests are asynchronous andstop_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: - `percent`, `eta`, `elapsed`, `simulationDate`, `portfolioValue`, `totalReturnPct`, `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_backtest_artifact; never pass a strategy id, aiStrategyId, revisionId, browser URrun_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. It can place live trades. Preserves the saved revision, broker, variables, recustart_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 RISK: the deployment may place real-money trades. Call for an authorized start rstop_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 call this tool after the user has explicitly confirmed the stop action, broker m
Show 88 more
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 website approval request. Restart argument example: {"deploymentId":"RETURNED_DEPLOYplace_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 least 200 characters explaining the decision, supporting evidence and material riskget_deployment_action_status· Returns the status of a pending or completed deployment authorization request created by start_deployment, stop_deployment, update_deployment_revision, run_deployment_once, or place_trade. Includes the active, expired or revoked trading winget_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(action="manage") or broker_orders(action=manage), or the deterministic singleTralist_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 live deployments; an unavailable live return stays unknown. Do not use this toolget_deployment_logs· Returns CloudWatch logs from a live deployment's container. Supports time-range filtering (startTimeIso/endTimeIso), CloudWatch filter patterns (query), local multi-query diagnostics (queries), diagnosticPreset, noise suppression, and paginlist_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 deploymentId so run IDs remain paired with the deployment that owns them. Use this when tlist_deployment_artifacts· Returns the manifest for the latest or specified deployment run, including artifact kinds, keys, sizes, row counts, timestamps, symbols, queryability, visibility, and upload status. Use this to find the canonical agent_detail and memory artget_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_deployment_artifact for agent_detail, memory, indicators, stats, or other tabular artifquery_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 {deploymentId, runId} targets; they are owner-checked, queried concurrently, and returget_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 exactly one active saved broker connection. Ask once: put up to 20 symbols of oneget_broker_positions· Read-only: fetches current positions directly from saved broker credentials, not from deployment telemetry or snapshot automation. For current performance of a named bot or a follow-up about its holdings, use show_bot_activity first; it perget_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 follow-up about its account, use show_bot_activity first; it performs its own exget_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 hoursAgo parameter controls the lookback window (default 168 = 1 week, max 720 = 30 dget_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 deployment. The live evidence requirements below apply only when investigating oget_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 whole linked account, not strategy-attributed or cash-flow-adjusted investment perfoget_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 deployment. The live evidence requirements below apply only when investigating ocreate_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 strategy logic or fake validation trades. After creation, use the returned files manifeset_strategy_revision· Updates the active conversation to use a specific revision of the already-active strategy. Pass revisionId, or pass version with the user-facing version number (for example version=641) when the user asks to restore or pull up an exact histset_runtime_secret_requirements· Sets or clears structured runtime secret requirements for an owned strategy revision. Use this when the strategy code needs non-broker API keys or settings, such as AP_API_KEY. This metadata is checked before starting or updating a bot so mset_strategy_requirements· Explicitly overrides the automatically analyzed assetClasses and dataRequirements metadata for this owned strategy revision only. Optionally correct aiEnabled after inspecting that exact revision; omitted classification is preserved. Use thswitch_active_strategy· Changes this conversation's active strategy workspace to another strategy owned by the user. Use only when the user explicitly asks to work with, compare against, copy from, or move to a different strategy. If the user explicitly names or ilist_revisions· Returns a bounded page of available revisions for a strategy with full revisionIds and version numbers. The default returns the newest 20 revisions and is capped at 50 per call so revision history never overwhelms the model context. When thgenerate_other_code· ⚠️ IMPORTANT: This tool is RARELY needed. Normal trading strategy requests should use create_strategy plus file tools for LumiBot Python strategies. WHY LUMIBOT IS BETTER: - Python is more powerful and easier to maintain - Works with multiplist_strategies· Returns all strategies owned by the current user. Each item includes both strategyId and aiStrategyId so you can use either with other tools (delete_strategy, list_revisions, start_backtest, etc.). Optionally filter by name. The name filterget_strategy· Returns full details for a single strategy including name, type, revision count, latest revision info, and deployment status. Accepts either strategyId or aiStrategyId.delete_strategy· Soft-deletes a strategy so it no longer appears in lists or can be used for backtests. Data is preserved in the database for compliance. Two-phase operation: call without confirm (or confirm=false) to preview what will be affected. Call witupdate_strategy· Updates a strategy's name. Accepts either strategyId or aiStrategyId. Use publish_to_marketplace or unpublish_from_marketplace for public marketplace visibility.create_checkout_link· Creates a checkout session URL (subscription or one-time) tied to the authenticated MCP account.create_billing_portal_link· Creates a billing portal URL for the authenticated MCP user so subscriptions and payment methods can be managed.get_strategy_visuals· Returns strategy visual assets for a revision: Mermaid diagram code/image and infographic image URL. Use generateInfographicIfMissing=true to trigger infographic generation when missing.get_backtest_visuals· Returns signed URLs for visual backtest artifacts (tearsheet, trades, indicators, stats) plus summary metrics and strategy IDs.get_backtest_chart_series· Builds chart-ready time series data for equity/portfolio/drawdown/returns from stats artifacts and returns points + Vega-Lite spec.show_account_overview· Answers "How is my account doing?" with account value, cash, unrealized P&L and position count for each connected broker account, an account value history chart from saved daily snapshots, and an allocation donut when holdings are complete.show_holdings· Answers "What do I hold?" and "Which positions are winning?" with a holdings table per account (value, unrealized P&L in dollars and percent, weight) and an allocation donut when the total is complete. Fetches the holdings itself; use thisshow_position· Answers "How is my TSLA position doing?" and "How much TSLA exposure do I have?" for a stock symbol or an options underlying: value, unrealized P&L, shares and average cost, exposure in share-equivalents (option delta only when the broker rshow_backtest_dashboard· Answers "How did my backtest do?" with total return, CAGR, max drawdown, Sharpe and the equity curve for one saved backtest. Use a backtestId from list_backtests or backtest_status. Results are simulated. Never starts or changes a backtest.show_backtest_comparison· Answers "Which of my backtests did better?" for 2 to 10 saved backtests: equity lines started at 100 on the same chart plus a metric table (total return, CAGR, max drawdown, Sharpe, trades). Runs of one strategy with different parameter valshow_bot_activity· For a general activity or trading-today summary, call this before separate order telemetry, run history or logs. Inspect its returned dated account, holdings and orders first, then fetch only missing decision details. Daily price attributioshow_option_payoff· Draws ONE option position at expiration from the legs described (call or put, long or short, strike, premium, contracts): one call or put, debit or credit spread, straddle, strangle, butterfly, iron condor; covered call with stock (shares,show_trading_cards· This panel uses supplied inputs; rendering does not independently verify their prices, timestamps or account marks. For portfolio attribution, use run_data_analysis to calculate and publish every holding’s daily change/contribution and quanget_tool_call_metrics· Returns per-tool call duration metrics for a conversation with an explicit latency boundary. Includes individual call records and aggregates, or exact Agent-vs-Node paired comparisons with transport/Agent overhead. Use this to identify slowsave_marketplace_publication· Creates or updates a draft for exactly one explicit subject. Can set Marketplace presentation and default-deny capabilities, then optionally publish. To save your default positions, filled-trade and open-order sharing for first-time strategpublish_to_marketplace· Publishes a strategy to the public marketplace where users can discover it. Marketplace listing status is the public contract; bot deployments remain private. Tags can be set for categorization (holdingPeriod, riskLevel, plan tier). Free anunpublish_from_marketplace· Removes a strategy from the public marketplace. The strategy becomes private and is no longer discoverable by other users. Existing private share links (if any) are NOT affected. Uses soft-delete (sets isActive=false). Accepts the marketplaclone_strategy· Creates a private dormant copy for the authenticated user. To copy a Marketplace listing, pass its listingId from marketplace_strategies; the publisher must have allowed copying. This copies published code, not a first-build workspace: contcommunity· BotSpot's trader Community: what other traders and their bots are doing right now. Read it often, before building or changing a strategy, to see what is working for real people: action feed reads the newest posts (kind=trades for shared andcompetitions· Browse public trading competitions, their rules, prizes and account leaderboards. list finds competitions; get reads one; leaderboard follows entered accounts; my_entry reads your own entry. enter registers your explicitly selected brokeragsearch_memory· Retrieve relevant prior memories about this user. CALL search_memory at the START of any conversation where the user: - References past context ("like we discussed", "remember when", "last time") - Asks for advice that should reflect theirdelete_memory· Permanently delete a memory about the user. CALL delete_memory when the user explicitly asks to forget something, OR when they correct a fact you retrieved ("no, I switched to IBKR last month" — delete the old "user trades on Tradier" memorget_education_offers· Live facts about the AI Trading Bootcamp and the free live challenge show, read from the database. Use when the user asks about the Bootcamp, its price, payment plans, curriculum or dates, or about the free live challenge or show (the nextskills· BotSpot's free strategy-building skills: expert guides for writing LumiBot trading strategies (stocks, ETFs, options), making them fast, and using the BotSpot tools well. Before you write, edit or debug a strategy, call action=list, then acsearch_conversation_history· Search the user's full conversation history via Postgres full-text search. CALL search_conversation_history when the user refers to specific past messages, errors, decisions, or details that you do not already see in the live context windowlist_broker_credentials· Lists saved broker credential metadata for the authenticated user. Raw credential values are never returned. Use an item's id as start_deployment.brokerCredentialId only when the user explicitly named that exact saved broker connection/accoget_broker_token_refresh_status· Read-only token refresh status for one saved broker credential owned by the authenticated user. Use this after Schwab or Tradier OAuth snapshot runs to verify whether Node persisted rotated token material. In a reconnection conclusion, stattest_schwab_broker_connection· One-stop MCP smoke test for an authenticated user's saved Schwab broker connection. If brokerCredentialId is omitted and exactly one active Schwab credential exists, this selects it automatically. The tool checks sanitized token-refresh reaupdate_broker_credential· Updates broker credential metadata and optionally replaces Vault material for the authenticated owner. This replaces the saved credential values when credentialValues is provided; it never returns raw values. For a broker or exchange API kedelete_broker_credential· Deletes broker credential material from Vault and marks the authenticated user's metadata row deleted. Existing running deployments may fail if they still depend on this credential; create a new credential and redeploy instead of deleting alist_files· Lists files in any saved strategy revision owned by the authenticated user. Folders are represented by slash-separated file paths. For the current attached/open strategy, omit strategyId and revisionId so the server uses the latest active rget_file· Returns one file from any saved strategy revision owned by the authenticated user, including an opaque editHandle for safe edits. Call list_files before reading optional files such as rules.json or helpers whose presence is unknown; read oncreate_file· Creates a file in a new immutable revision for any strategy owned by the authenticated user. For the current attached workspace, omit strategyId and revisionId. When create_strategy attaches the workspace through conversationUpdate, these dreplace_file· Replaces the full contents of an existing strategy file in a new immutable revision for any strategy owned by the authenticated user. Requires editHandle from get_file/list_files. Use this for first-build main.py replacement after create_stcreate_dashboard_file· Creates a template-first dashboard file at dashboards/<name>.dashboard.js in a new immutable strategy revision. Use this when the user asks to create a dashboard, then use get_file and patch_file to customize the dashboard from the templatedelete_file· Deletes a file in a new immutable revision for any strategy owned by the authenticated user. Requires editHandle from get_file/list_files to prevent stale edits. main.py cannot be deleted. For the current attached/open strategy, omit stratepatch_file· Applies exact text or guarded line-range edits to one file in any strategy owned by the authenticated user and creates a new immutable strategy revision. Requires editHandle from get_file/list_files. For insert_before and insert_after operaget_active_plan· Returns the active read-only user-visible plan for the current conversation. Plan tools update plan state only; they never hide, block, route, or enable other tools.create_plan· Creates a persisted, user-visible plan for substantial work in the current conversation. Use this for strategy builds, strategy edits, research, deployment setup, backtest analysis, broker investigation, and other multi-step tasks. Do not uadd_plan_item· Adds a user-visible item to the active plan when new work is discovered. When working in the current conversation, omit planId unless you already have the actual plan id; never pass a plan item id as planId. All new-item fields belong insidupdate_plan_item· Updates one user-visible plan item. The target is required and must be `{type:"id", itemId}` or `{type:"position", position}`; ambiguous itemId/position top-level shapes are intentionally not accepted. Use this before or after each major acupdate_plan_items· Applies multiple user-visible plan item updates atomically in the listed order. Use this for handoffs between existing rows and multi-row reconciliation: first resolve the current item, then start the next existing item in the same orderedreplace_plan_items· Codex-style whole-plan update. Replaces the complete visible item list for the active plan in one call while preserving item ids when supplied. Use this when the visible checklist needs simple list/status synchronization or reorder cleanup.record_external_wait_in_plan· Generic factual plan helper for the moment after a domain tool starts asynchronous work and returns a real externalWaitId. Identity and revision come from that stored hook wait; pass externalWaitId instead of copying externalKind, externalIremove_plan_item· Marks one plan item as removed. The target is required and must be `{type:"id", itemId}` or `{type:"position", position}`. Users cannot manually edit plan items; redirect changes through chat.complete_plan· Marks the active plan completed, blocked, or cancelled. When working in the current conversation, omit conversationId; never pass placeholders such as `current`, `this`, or `active`. If you include conversationId, it must be the real UUID.search_data_catalog· Find BotSpot-provided public research datasets the agent can query. Pass datasetId alone to inspect a selected dataset contract, schemas, units, coverage and historical guarantees. Catalog metadata is not observations or a permission grant.query_data· Query a registered research dataset by datasetId. Use for versioned symbol-membership universes, SEC company facts, SEC financial statements, SEC current filings, SEC full-text search, SEC filing exhibits, SEC insider transactions, SEC 13Fsearch_documents· Search public research documents, initially SEC EDGAR filings. Use this to find 10-K, 10-Q, 8-K, S-1, DEF 14A, Form 4, and 13F-HR documents before calling get_document. Use datasetId sec.full_text_search with query when searching across EDGget_document· Retrieve a public document by id, initially SEC filing documents from EDGAR. For SEC filings, pass documentId as CIK:accessionNumber[:filename]. Optional section aliases include risk_factors, business, mda, and controls. Use ids returned byrun_data_analysis· Execute a previously validated Python analysis. Before the first execution, call validate_analysis_program with the full intended request, then pass its exact returned validatedProgram. If code or settings change, validate the new request binspect_analysis_artifact· Read the durable datasets, stable semantic element IDs, and view bindings from one completed analysis run in the current conversation. Use this before resolving any chart-derived value or condition. The response exposes schemas, stable IDs,resolve_analysis_reference· Deterministically resolve one stable semantic element or one structured expression against the full durable dataset from a completed analysis run. Every result is persisted with its source run, expression, value or condition state, timestamset_data_provider· Updates the active conversation to use the specified backtesting data provider. AVAILABILITY AND SETUP: Read these constraints before selecting a provider. Do not probe a provider already declared OFF by calling this tool. Explain its knownbroker_orders· Read current orders through a saved broker connection, or request cancellation/modification of one exact owned order. Management always requires a fresh website approval and never places a replacement trade. Read the returned broker state abroker_markets· Read native instruments through a saved broker connection. Use search for prediction-market contracts/details/rules and options for a bounded option chain. Preserve native IDs and the saved account mode for subsequent quotes and trades. Setaccount· Read account billing, provider-aware current and historical subscriptions with billing states and management actions, and usage with status, or read the current database AI model catalog with models. Models includes supported effort and spebroker_connections· Connect an existing broker using its supported credentials, prepare a deferred paper account request, create an internal simulated trading account, add/remove/set its virtual cash, delete it, or read operation progress. Creation is a write;api_keys· Make, list, replace or revoke BotSpot API keys right in the chat, and approve a `lumibot connect botspot` login code. For a requested LumiBot project setup, action="create" returns connection.environment: choose a recognizable name, save thindicators· Save, version, read, list and delete your own custom Python indicators (LumiBot Indicator classes). Before writing custom chart source, load the custom-chart-indicators reference. Use from lumibot.indicators import Indicator, InputSpec, Out
The first 100 are shown.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 1.1.2 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Hosted endpoint | https://mcp.botspot.trade/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/Lumiwealth/botspot-mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
- VERSION24 Oct 20261.1.1 → 1.1.2
- VERSION11 Oct 20261.1.0 → 1.1.1
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is BotSpot: AI Trading, Backtests and Bots still online?
Free alerts · no account▲ 0Do you run BotSpot: AI Trading, Backtests and Bots? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about BotSpot: AI Trading, Backtests and Bots
How do I connect BotSpot: AI Trading, Backtests and Bots?
Use the hosted endpoint https://mcp.botspot.trade/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does BotSpot: AI Trading, Backtests and Bots offer?
When Electra Index connected on 16 Nov 2026, it listed 115 tools: commit_backtest_rules_review, list_backtests, get_backtest_artifact, get_backtest_logs, start_parameter_experiment, start_backtest, stop_backtest, backtest_status and more. The full list is in "Live check" above.
Is BotSpot: AI Trading, Backtests and Bots online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.
What can I use BotSpot: AI Trading, Backtests and Bots for?
Based on its description, it is most relevant to: automate CI/CD pipelines, monitor production incidents.