TradingAgentStack
REMOTE · TRADINGAGENTSTACK.COM · 2 COMPONENTS
Check bots, exchanges and wallets before you connect; Agent Risk Scores, incidents, sources.
Available components
Last scanned (29 minutes ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1565 tokens (~156/item across 10 items; 10 tools + 0 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 Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_setup” rewrote its description, which is the text the model reads security
- Tool “get_risk” rewrote its description, which is the text the model reads security
- Server version: 0.6.0 → 0.7.0 functional
- “get_risk” reworded the description of “category” cosmetic
- Tool “get_risk” changed its title: Agent Risk Score for a tool → Safety score for a tool cosmetic
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check” rewrote its description, which is the text the model reads security
- Tool “get_incidents” rewrote its description, which is the text the model reads security
- Schema quality: 114 → 155 ▼ functional
- Server version: 0.5.0 → 0.6.0 functional
- New tool “check_setup” functional
- New tool “get_leaderboard” functional
- “search_tools” added an optional parameter “limit” cosmetic
- “get_incidents” reworded the description of “tool” cosmetic
- 28 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://tradingagentstack.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.tradingagentstack.com | CN=YR1,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | RSA 2048 | SHA256-RSA | 5a8aa20d0a9683213de01a41de761b5ab68 |
| SANs: *.tradingagentstack.com, tradingagentstack.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tradingagentstack.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tradingagentstack.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tradingagentstack.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://tradingagentstack.com/api/mcp | HTTPS enforced | 308 | https://tradingagentstack.com/api/mcp |
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 →
broker_order_gating Broker MCP order approval overview ~39
Who places the order for every official broker MCP server: AI trades directly, you confirm each order, approval optional, or you place the order.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check Check a bot, exchange or wallet before connecting ~206
Check before connecting (TAS Check): give a name, link, Telegram or X @handle, GitHub repo or app-store link of a Telegram trading bot, web trading terminal, exchange, swap service or wallet (incl. Zcash/Monero wallets). Returns whether the link is on that service's official list (confirmed from two independent places), a known fake, or a lookalike that uses its name, plus the worst case for your money, who holds the keys, freeze/hold policy, what a leaked API key can do, Monero/Zcash support, what the service collects about you and any data breaches, incidents, deadlines and a 3-step safe setup, each with sources. Unknown links are reported as unknown, never as safe.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | e.g. 't.me/solana_trojanbot', 'bananagun.io', '@krakenfx', 'github.com/cake-tech/cake_wallet', 'Kraken' |
No output schema declared.
No examples provided.
check_setup Check my whole setup ~160
Check a whole setup at once: up to 8 bots, exchanges, wallets, swap services or AI trading connectors someone uses (names, links, @handles or slugs). For each: who holds the keys, the worst case, who places orders, the Safety score, incidents in the last 12 months and the first fix, each from the dataset. Also returns the single biggest risk by a fixed rule, items we don't track (reported as unknown, never as safe), and a report_url that opens the same report on tradingagentstack.com. Links that use a tracked name but aren't official are flagged.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | e.g. ['Phantom', 'Trojan', 'Binance', 'Alpaca MCP server'] |
No output schema declared.
No examples provided.
compare_tools Compare two tools ~38
Compare two tools side by side, field by field, with sources.
| Name | Type | Req | Description |
|---|---|---|---|
| slug_a | string | yes | – |
| slug_b | string | yes | – |
No output schema declared.
No examples provided.
get_incidents Agent security incidents ~111
Security incidents involving AI agents, trading tools and the infrastructure they run on (breaches, exploits, security releases), each from an official disclosure. Filter by date, or by a listed tool or a bot, exchange or wallet tracked by check.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | Only incidents on or after this date, YYYY-MM-DD |
| tool | string | – | Only incidents for this tool or service (slug or name), e.g. 'alpaca-mcp-server', 'Keystone', 'Bloom' |
No output schema declared.
No examples provided.
get_leaderboard Verified AI trading leaderboard ~290
Verified performance leaderboard for AI trading agents, bots and vaults: return, BTC over the same dates, max drawdown and Sortino ratio, computed by TradingAgentStack from the venue's public API (never screenshots, self-reported PnL or backtests), with security rated separately as a gate. Sections: ai_vaults (Hyperliquid vaults whose leader says they are AI-run, with the quoted claim), vaults (biggest Hyperliquid vaults of any strategy), agents (AI agents with an officially published trading account or on-chain registration), apps (AI trading apps on Hyperliquid: users, volume and users' realized PnL from public builder fills), models (which AI model forecasts and trades best: ForecastBench, Prophet Arena, Alpha Arena, FutureEval), signals (grade B: MQL5 robot signals on real accounts, venue-reported, not ranked), usage (fees users pay Telegram bots, trading apps and AI agent protocols, and open-source repo health). Ranked vaults passed a 30% drawdown gate and are sorted by Sortino; the rest are listed as high_drawdown. Not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max entries per list (default 10) |
| section | string | – | Which list to return (default all: the verified lists plus apps; models, signals and usage only when asked) |
No output schema declared.
No examples provided.
get_risk Safety score for a tool ~178
Check a tool before your agent connects to it: how much money could be lost if the tool, or the agent using it, is wrong, hacked or prompt-injected? Returns the Safety score (human approval, guardrails outside the agent, test mode, sending funds out, who holds the keys, open source or audited, incident record), each input with its reason and source; missing inputs are listed, not guessed. Omit tool to rank every tool in a category (e.g. agent_wallet, bot_exchange, broker_mcp).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Rank a category instead, e.g. agent_wallet, agent_payments, ai_trading_agent, bot_exchange, defi_agent or broker_mcp |
| tool | string | – | Tool slug or name, e.g. 'safe-smart-account', 'Hyperliquid' |
No output schema declared.
No examples provided.
get_tool Get tool facts and sources ~50
Full facts for one tool: pricing, live vs paper, order approval, rate limits, safety score inputs and every source URL.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Tool slug (from search_tools) or name |
No output schema declared.
No examples provided.
list_category List tools in a category ~43
List every tool in a category. Call with an unknown category to get the list of categories.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Category slug, e.g. broker_mcp |
No output schema declared.
No examples provided.
search_tools Search AI trading tools ~144
Search the TradingAgentStack directory of AI trading tools (broker MCP servers, trading and data APIs, bots, frameworks) by name, market or feature. Optional filters: category slug, can_trade_live, has_paper.
| Name | Type | Req | Description |
|---|---|---|---|
| can_trade_live | boolean | – | Only tools that can place real-money orders |
| category | string | – | Category slug, e.g. broker_mcp, data_api, ai_bot_platform |
| has_paper | boolean | – | Only tools with a documented paper/demo/testnet mode |
| limit | integer | – | Max results (default 10) |
| query | string | yes | Words to match, e.g. 'options paper alpaca' |
No output schema declared.
No examples provided.
How do I install the TradingAgentStack MCP server?
TradingAgentStack is a hosted endpoint at https://tradingagentstack.com/api/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 · tradingagentstack.com
claude mcp add --transport http intoapex-tradingagentstack 'https://tradingagentstack.com/api/mcp'
What is the TradingAgentStack MCP server?
TradingAgentStack is an MCP server listed in the public MCP registry as io.github.intoApex/tradingagentstack. Check bots, exchanges and wallets before you connect; Agent Risk Scores, incidents, sources. This page covers its hosted endpoint (https://tradingagentstack.com/api/mcp).
Is the TradingAgentStack MCP server safe to use?
TradingAgentStack scores 80 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.
What tools does the TradingAgentStack MCP server expose?
TradingAgentStack exposes 10 tools: search_tools, get_tool, list_category, compare_tools, broker_order_gating, and 5 more. Their descriptions and schemas cost roughly 1,259 tokens of context every time the server is loaded.
Does the TradingAgentStack MCP server require authentication?
No. We connected to TradingAgentStack without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TradingAgentStack MCP server still maintained?
TradingAgentStack is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.