# TradingAgentStack (remote · tradingagentstack.com)

Check bots, exchanges and wallets before you connect; Agent Risk Scores, incidents, sources.

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `tradingagentstack.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/intoapex-tradingagentstack/api-mcp.md), [page](https://verifymcp.io/servers/intoapex-tradingagentstack/api-mcp)
- npm · `tradingagentstack-mcp`: 68/100, [markdown](https://verifymcp.io/servers/intoapex-tradingagentstack/tradingagentstack-mcp.md), [page](https://verifymcp.io/servers/intoapex-tradingagentstack/tradingagentstack-mcp)

## Channel facts

- Endpoint: `https://tradingagentstack.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.6.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http intoapex-tradingagentstack 'https://tradingagentstack.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "intoapex-tradingagentstack": {
      "url": "https://tradingagentstack.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "intoapex-tradingagentstack": {
      "type": "http",
      "url": "https://tradingagentstack.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.intoapex-tradingagentstack]
url = "https://tradingagentstack.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "intoapex-tradingagentstack": {
      "type": "remote",
      "url": "https://tradingagentstack.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add intoapex-tradingagentstack --url 'https://tradingagentstack.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  intoapex-tradingagentstack:
    url: "https://tradingagentstack.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "intoapex-tradingagentstack": {
      "Transport": "http",
      "Url": "https://tradingagentstack.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add intoapex-tradingagentstack -t streamable-http -u 'https://tradingagentstack.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "intoapex-tradingagentstack": {
      "type": "http",
      "url": "https://tradingagentstack.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 80, +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.

### 2026-11-03 (score 79, +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.

### 2026-11-02 (score 78, 0)

- [security] 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
- [functional] Server version: 0.6.0 → 0.7.0
- [cosmetic] “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

### 2026-11-01 (score 78, +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.

### 2026-10-30 (score 77, +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.

### 2026-10-29 (score 76, −1)

- [security] 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
- [functional regression] Schema quality: 114 → 155
- [functional] Server version: 0.5.0 → 0.6.0
- [functional] New tool “check_setup”
- [functional] New tool “get_leaderboard”
- [cosmetic] “search_tools” added an optional parameter “limit”
- [cosmetic] “get_incidents” reworded the description of “tool”

### 2026-10-28 (score 77, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: pass → fail

### 2026-10-26 (score 76, +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.

## MCP tools (10)

### `search_tools` (~144 tokens)

Search AI trading tools

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.

Input parameters:

- `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, required): Words to match, e.g. 'options paper alpaca'

### `get_tool` (~50 tokens)

Get tool facts and sources

Full facts for one tool: pricing, live vs paper, order approval, rate limits, safety score inputs and every source URL.

Input parameters:

- `slug` (string, required): Tool slug (from search_tools) or name

### `list_category` (~43 tokens)

List tools in a category

List every tool in a category. Call with an unknown category to get the list of categories.

Input parameters:

- `category` (string, required): Category slug, e.g. broker_mcp

### `compare_tools` (~38 tokens)

Compare two tools

Compare two tools side by side, field by field, with sources.

Input parameters:

- `slug_a` (string, required)
- `slug_b` (string, required)

### `broker_order_gating` (~39 tokens)

Broker MCP order approval overview

Who places the order for every official broker MCP server: AI trades directly, you confirm each order, approval optional, or you place the order.

### `get_risk` (~178 tokens)

Safety score for a tool

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).

Input parameters:

- `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'

### `get_incidents` (~111 tokens)

Agent security incidents

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.

Input parameters:

- `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'

### `check` (~206 tokens)

Check a bot, exchange or wallet before connecting

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.

Input parameters:

- `query` (string, required): e.g. 't.me/solana_trojanbot', 'bananagun.io', '@krakenfx', 'github.com/cake-tech/cake_wallet', 'Kraken'

### `check_setup` (~160 tokens)

Check my whole setup

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.

Input parameters:

- `items` (array, required): e.g. ['Phantom', 'Trojan', 'Binance', 'Alpaca MCP server']

### `get_leaderboard` (~290 tokens)

Verified AI trading leaderboard

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.

Input parameters:

- `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)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/intoapex-tradingagentstack/api-mcp#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 76
- 2026-10-28: 77
- 2026-10-27: 76
- 2026-10-26: 76
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 74
- 2026-10-22: 72
- 2026-10-21: 72
- 2026-10-20: 72
- 2026-10-19: 71
- 2026-10-18: 71

## Common questions

### 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.

## Links

- Remote endpoint: https://tradingagentstack.com/api/mcp
- Repository: https://github.com/intoApex/ai-trading-tools
- Website: https://tradingagentstack.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/intoapex-tradingagentstack/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/intoapex-tradingagentstack/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/intoapex-tradingagentstack/api-mcp