BotSpot: AI Trading, Backtests and Bots
REMOTE · MCP.BOTSPOT.TRADE
AI agents backtest, paper trade and live trade via your broker. Free to connect; OAuth.
Available components
Last scanned (15 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security86
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability33
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 67317 tokens (~570/item across 118 items; 115 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management89
- Stability check failed: schema churn in the 29 days we've observed: 8 tool removals, 0 breaking changes, 0 auth/transport breaks, 13 additions. See how to fix → Fail
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 61% of tool parameters carry a description.Partial
Tool Safety48
- Injection-marker check failed: the description of tool "complete_plan" contains an instruction to conceal the call from the user, the text "Do not tell the user", at byte 750 of that field. See how to fix → Fail
- 9 of 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "query_csv" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 117 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Checks we could not complete (1)
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.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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 →
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.
- 21 Nov 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Nov 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Nov 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Nov 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 21 Nov 2026 · Probed https://mcp.botspot.trade/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.botspot.trade | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 13 Oct 2026 | 28 Apr 2027 | RSA 2048 | SHA256-RSA | 1bb2abe58a6fbfeceffd9ac6900c5b0 |
| SANs: *.botspot.trade | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.botspot.trade. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| trade. | DS published | 64969 | 8 | Verified |
| botspot.trade. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="botspot-mcp", error="invalid_token", error_description="Sign in to BotSpot to use this tool. Connecting BotSpot creates a free account if the person does not have one. Agents that cannot connect can use the public signup endpoint /signup-mcp (tool create_botspot_account).", resource_metadata="https://mcp.botspot.trade/.well-known/oauth-protected-resource"
Bearer realm="botspot-mcp", error="invalid_token", error_description="Sign in to BotSpot to use this tool. Connecting BotSpot creates a free account if the person does not have one. Agents that cannot connect can use the public signup endpoint /signup-mcp (tool create_botspot_account).", resource_metadata="https://mcp.botspot.trade/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Protected resource metadata
| Document | https://mcp.botspot.trade/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.botspot.trade/mcp |
| Authorisation server | https://mcp.botspot.trade |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.botspot.trade/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.botspot.trade/mcp | Inconclusive | 405 |
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 →
skills ~152
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| name | string | – | – |
| reference | string | – | – |
No output schema declared.
No examples provided.
start_backtest ~1,512
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | – | – |
| budgetConversion | object | – | – |
| cache | string | – | – |
| dataConnectionId | string | – | – |
| dataProvider | string | – | – |
| endDate | string | yes | – |
| envVarSetIds | array | – | – |
| parameters | object | – | – |
| profile | boolean | – | – |
| revisionId | string | – | – |
| startDate | string | yes | – |
| strategyParameterSetId | string | – | – |
No output schema declared.
No examples provided.
start_deployment ~2,041
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptances | object | – | – |
| aiStrategyRevisionId | string | yes | – |
| brokerCredentialId | – | – | – |
| deploymentMode | string | – | – |
| envVarSetIds | array | – | – |
| idempotencyKey | string | – | – |
| memoryGb | number | – | – |
| runImmediately | boolean | – | – |
| scheduleMetadata | object | – | – |
| schedulePolicyId | – | – | – |
| strategyParameterSetId | – | – | – |
No output schema declared.
No examples provided.
start_parameter_experiment ~612
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | – | – |
| budgetConversion | object | – | – |
| endDate | string | yes | – |
| envVarSetIds | array | – | – |
| revisionId | string | – | – |
| startDate | string | yes | – |
| variants | array | yes | – |
No output schema declared.
No examples provided.
stop_backtest ~44
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| backtestId | string | – | – |
| botId | string | – | – |
| revisionId | string | – | – |
No output schema declared.
No examples provided.
stop_deployment ~210
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| deploymentId | string | yes | – |
| idempotencyKey | string | – | – |
No output schema declared.
No examples provided.
strategy_share_link ~528
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | – | – |
| action | string | yes | – |
| aiStrategyId | string | – | – |
| allowClone | boolean | – | – |
| allowCodeView | boolean | – | – |
| allowPerformanceView | boolean | – | – |
| forceRegenerate | boolean | – | – |
| strategyId | string | – | – |
No output schema declared.
No examples provided.
switch_active_strategy ~214
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| aiStrategyId | string | – | – |
| revisionId | string | – | – |
| strategyId | string | – | – |
No output schema declared.
No examples provided.
test_schwab_broker_connection ~165
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| brokerCredentialId | string | – | – |
| includeDiagnostics | boolean | – | – |
| includeLogs | boolean | – | – |
| logLimit | integer | – | – |
| runSnapshot | boolean | – | – |
No output schema declared.
No examples provided.
unpublish_from_marketplace ~120
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| aiStrategyId | string | – | – |
| listingId | string | – | – |
| strategyId | string | – | – |
No output schema declared.
No examples provided.
update_broker_credential ~1,152
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| broker | string | – | – |
| credentialValues | object | – | – |
| displayName | string | – | – |
| id | string | yes | – |
| paperOrLive | string | – | – |
No output schema declared.
No examples provided.
update_deployment_revision ~1,530
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| aiStrategyRevisionId | string | yes | – |
| brokerCredentialId | – | – | – |
| deploymentId | string | yes | – |
| deploymentMode | string | – | – |
| envVarSetIds | array | – | – |
| idempotencyKey | string | – | – |
| runImmediately | boolean | – | – |
| scheduleMetadata | object | – | – |
| schedulePolicyId | – | – | – |
| strategyParameterSetId | – | – | – |
No output schema declared.
No examples provided.
update_plan_item ~605
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationId | string | – | – |
| patch | object | yes | – |
| planId | – | – | – |
| target | – | yes | – |
No output schema declared.
No examples provided.
update_plan_items ~451
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationId | string | – | – |
| planId | – | – | – |
| updates | array | yes | – |
No output schema declared.
No examples provided.
update_strategy ~78
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| aiStrategyId | string | – | – |
| name | string | – | – |
| strategyId | string | – | – |
No output schema declared.
No examples provided.
How do I install the BotSpot: AI Trading, Backtests and Bots MCP server?
BotSpot: AI Trading, Backtests and Bots is a hosted endpoint at https://mcp.botspot.trade/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.botspot.trade
claude mcp add --transport http grzesir-botspot-trading 'https://mcp.botspot.trade/mcp'
What is the BotSpot: AI Trading, Backtests and Bots MCP server?
BotSpot: AI Trading, Backtests and Bots is an MCP server listed in the public MCP registry as io.github.grzesir/botspot-trading. AI agents backtest, paper trade and live trade via your broker. Free to connect; OAuth. This page covers its hosted endpoint (https://mcp.botspot.trade/mcp).
Is the BotSpot: AI Trading, Backtests and Bots MCP server safe to use?
BotSpot: AI Trading, Backtests and Bots scores 77 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.
Does the BotSpot: AI Trading, Backtests and Bots MCP server require authentication?
Yes. BotSpot: AI Trading, Backtests and Bots asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the BotSpot: AI Trading, Backtests and Bots MCP server still maintained?
BotSpot: AI Trading, Backtests and Bots is still listed as active in the MCP registry. We last reached this channel on 21 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 BotSpot: AI Trading, Backtests and Bots MCP server?
VerifyMCP ran 13 checks on BotSpot: AI Trading, Backtests and Bots, covering TLS certificate, Authorization, HSTS header, DNSSEC and 9 more. One item could not be completed, a gap on our side rather than a finding about BotSpot: AI Trading, Backtests and Bots: HTTPS. 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.