mcp-registry/io.github.grzesir/botspot-trading · v0.0.0
As of 2026-10-27 06:16 UTC, the Grzesir Botspot Trading MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
AI trading bots: generate strategies, backtest, deploy live to 10+ brokers. No coding required.
Point your MCP client at this streamable-http endpoint: https://mcp.botspot.trade/mcp
Loading this server's tool list costs an agent ~56,422 tokens before any work — more than 99% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
10 tool definition(s) exceed ~1,200 tokens each (largest: show_trading_cards, ~5,236).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~14,413 tokens every session. How to fix →
111 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
287 parameter(s) across 72 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
2 tools share an identical description with another tool on this server.
Make each description say how the tool differs from its siblings, or the model will pick between them at random. How to fix →
2 of 111 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 72 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.grzesir%2Fbotspot-trading/fixes
{
"name": "run_deployment_once",
"description": "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, recurring schedule, history and state. Current balance and holdings reports are not prerequisites; use the exact saved deployment and broker connection status. Preparation reads the saved connection status and mode and refuses an approval unless that status is con",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"deploymentId"
],
"properties": {
"deploymentId": {
"type": "string",
"format": "uuid"
},
"idempotencyKey": {
"type": "string",
"maxLength": 120,
"minLength": 1
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Run an existing scheduled bot once"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.grzesir/botspot-trading"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.grzesir/botspot-trading"}) over MCP.
show_trading_cards ~5,236 tokensplace_trade ~3,051 tokenssend_feedback ~2,346 tokensmanage_schedule ~2,024 tokensrecord_external_wait_in_plan ~1,402 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.grzesir%2Fbotspot-trading?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.grzesir%2Fbotspot-trading?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.grzesir%2Fbotspot-trading.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.grzesir%2Fbotspot-trading.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.grzesir%2Fbotspot-trading?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7c5a2d2a6653bf9f…, first seen 2026-10-27, included at leaf 76405 of 77,796. Version history · verify what your client received.
Compare: most reliable productivity servers · most reliable data servers · most reliable other servers · most reliable communication servers · most reliable payments servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 06:16 UTC, the Grzesir Botspot Trading MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Grzesir Botspot Trading MCP server advertises 111 tools, including add_plan_item, backtest_status, broker_snapshots, clone_strategy, commit_backtest_rules_review.
Point your MCP client at this streamable-http endpoint: https://mcp.botspot.trade/mcp
Glimind scanned all 111 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.