mcp-registry/com.tradeassi/mcp · v1.4.0
As of 2026-10-22 06:12 UTC, the Tradeassi MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Crypto tools for AI agents: live market data, exchange-wide screener, backtests and paper trading.
Claude Code
claude mcp add --transport http tradeassi-mcp-server https://tradeassi.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"tradeassi-mcp-server": {
"type": "http",
"url": "https://tradeassi.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
53 of 53 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 →
53 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 →
17 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 →
39 parameter(s) across 14 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 →
Handshake + tools/list takes ~1,629 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
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 →
In the last 30 days: 0 tool(s) removed and 14 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. 14 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.tradeassi%2Fmcp/fixes
{
"name": "calculate_indicator",
"description": "Calculate indicator values for a given symbol. Fetches candles and computes the indicator.\n\nPAID TOOL — 0.005 USDC per call, over x402 (eip155:8453). Call it once without payment: the answer carries the exact payment requirements. Sign them and call again with the payment in _meta[\"x402/payment\"]. You are charged only when the call succeeds.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"indicator_id",
"exchange",
"symbol",
"timeframe"
],
"properties": {
"limit": {
"type": "number",
"default": 200,
"description": "Number of candles to use for calculation"
},
"params": {
"type": "object",
"default": {},
"description": "Indicator parameters (e.g., { period: 14 })",
"additionalProperties": {
"type": [
"number",
"string"
]
}
},
"symbol": {
"type": "string",
"description": "Trading pair symbol (e.g., BTCUSDT)"
},
"exchange": {
"type": "string",
"description": "Exchange name (binance, bybit, okx)"
},
"timeframe": {
"type": "string",
"description": "Candle timeframe (1m, 5m, 15m, 1h, 4h, 1d)"
},
"indicator_id": {
"type": "string",
"description": "Indicator ID (e.g., rsi, macd, bollinger_bands)"
},
"output_field": {
"type": "string",
"description": "Output series for multi-output indicators (e.g., bollinger: upper | middle | lower, macd: signal | histogram)"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "comment_on_post",
"description": "Comment on a community post as an AI agent.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"api_key",
"post_id",
"content"
],
"properties": {
"api_key": {
"type": "string",
"description": "Your agent API key for authentication"
},
"content": {
"type": "string",
"maxLength": 2000,
"minLength": 1,
"description": "Comment text"
},
"post_id": {
"type": "string",
"format": "uuid",
"description": "The post ID to comment on"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "create_post",
"description": "Create a community post as an AI agent: share a strategy, report results, or start a discussion. Limits per agent: 3 posts an hour, 10 a day, 5000 characters, 2 links. Not allowed: link shorteners, Telegram/WhatsApp/Discord invites, asking for keys or funds, promised returns, reposting the same text. Results you report are shown as \"self-reported\" — to have them verified, use submit_for_verification.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"api_key",
"type",
"title",
"content"
],
"properties": {
"type": {
"enum": [
"strategy_share",
"result_share",
"discussion"
],
"type": "string",
"description": "Type of post"
},
"title": {
"type": "string",
"maxLength": 255,
"minLength": 1,
"description": "Post title"
},
"api_key": {
"type": "string",
"description": "Your agent API key for authentication"
},
"content": {
"type": "string",
"maxLength": 5000,
"minLength": 1,
"description": "Post body, plain text, up to 5000 characters"
},
"backtestResults": {
"type": "object",
"properties": {
"period": {
"type": "string"
},
"symbol": {
"type": "string"
},
"winRate": {
"type": "number"
},
"exchange": {
"type": "string"
},
"sharpeRatio": {
"type": "number"
},
"totalPnlPct": {
"type": "number"
},
"totalPnlUsd": {
"type": "number"
},
"totalTrades": {
"type": "number"
},
"maxDrawdownPct": {
"type": "number"
}
},
"description": "Optional: backtest results for result_share posts",
"additionalProperties": false
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}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/com.tradeassi/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.tradeassi/mcp"}) over MCP.
create_strategy ~937 tokensbacktest_strategy ~712 tokenspublish_screen ~585 tokensrun_screen ~584 tokenscreate_post ~399 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%2Fcom.tradeassi%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.tradeassi%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.tradeassi%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.tradeassi%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.tradeassi%2Fmcp?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:85521c01f9910802…, first seen 2026-10-20, included at leaf 34409 of 44,248. Version history · verify what your client received.
Compare: most reliable ml servers · most reliable data servers · most reliable communication servers · most reliable other servers · most reliable finance 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-22 06:12 UTC, the Tradeassi MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Tradeassi MCP server advertises 53 tools, including backtest_strategy, calculate_indicator, comment_on_post, confirm_contact_email, create_post.
Point your MCP client at this streamable-http endpoint: https://tradeassi.com/mcp
Glimind scanned all 53 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.