TradingAgentStack
NPM · TRADINGAGENTSTACK-MCP · 2 COMPONENTS
Check bots, exchanges and wallets before you connect; Agent Risk Scores, incidents, sources.
Available components
Last scanned (3 minutes ago)
Scores higher than 35% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1553 tokens (~155/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 Management4
- Stability check failed: the tool surface changed between 0.1.0 and 0.6.0: 2 tool removals, 1 breaking changes, 8 additions. See how to fix → Fail
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.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- Schema quality: pass → fail ▼ functional
- Package version: 0.5.0 → 0.6.0 functional
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 25 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Schema quality: 78 → 95 ▼ functional
- Package version: 0.4.0 → 0.5.0 functional
- 24 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Schema quality: 64 → 78 ▼ functional
- Tool coverage: 75% → 83% ▲ functional
- Schema quality: fair → good functional
- Package version: 0.3.2 → 0.4.0 functional
- 22 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.3.1 → 0.3.2 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 5 Nov 2026 · Analysed npm/tradingagentstack-mcp@0.6.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~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 ~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 ~164
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 Agent Risk Score or 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 ~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 ~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 ~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 ~170
Check a tool before your agent connects to it: how much money could the agent lose if it is wrong, hacked or prompt-injected? Returns the Agent Risk Score (custody, limits enforced outside the model, human approval, withdrawal scope, preview, open source, incident record), each input with its official source; missing inputs are listed, not guessed. Omit tool to rank every scored tool in a category (agent_wallet, agent_payments, ai_trading_agent, agent_token, bot_exchange, defi_agent).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Rank a category instead: agent_wallet, agent_payments, ai_trading_agent, agent_token, bot_exchange or defi_agent |
| tool | string | – | Tool slug or name, e.g. 'safe-smart-account', 'Hyperliquid' |
No output schema declared.
No examples provided.
get_tool ~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 ~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 ~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 runs locally as an npm package, launched with npx -y tradingagentstack-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tradingagentstack-mcp
claude mcp add intoapex-tradingagentstack -- npx -y tradingagentstack-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 npm package (tradingagentstack-mcp).
Is the TradingAgentStack MCP server safe to use?
TradingAgentStack scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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,255 tokens of context every time the server is loaded.
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.
What licence is the TradingAgentStack MCP server under?
TradingAgentStack declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.