# TraderSpy (remote · mcp.traderspy.app)

AI crypto signals, smart money whale positions, live futures prices and indicators

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-15

## Components

- remote · `mcp.traderspy.app`: 74/100 (this document), [markdown](https://verifymcp.io/servers/app-traderspy-traderspy/mcp.md), [page](https://verifymcp.io/servers/app-traderspy-traderspy/mcp)

## Channel facts

- Endpoint: `https://mcp.traderspy.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.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-08-15.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 989 tokens (~65/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http app-traderspy-traderspy https://mcp.traderspy.app/mcp
```

### Codex

```toml
[mcp_servers.app-traderspy-traderspy]
url = "https://mcp.traderspy.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-traderspy-traderspy": {
      "type": "remote",
      "url": "https://mcp.traderspy.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-traderspy-traderspy --url https://mcp.traderspy.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-traderspy-traderspy:
    url: "https://mcp.traderspy.app/mcp"
```

### Other

```json
{
  "mcpServers": {
    "app-traderspy-traderspy": {
      "type": "http",
      "url": "https://mcp.traderspy.app/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-08-15 (score 74)

First indexed and scored.

## MCP tools (15)

### `get_signals` (~125 tokens)

Use this when the user asks for recent public AI crypto trading signals, optionally filtered by coin, importance, or pagination. When the user names a count ("last 5 signals"), pass it as `limit` — the card view renders exactly what was fetched, so over-fetching shows more cards than the user asked for.

Input parameters:

- `coin` (string): Filter by coin symbol, e.g. BTC, ETH
- `importance` (string): Filter by signal importance
- `limit` (number): Number of signals to return
- `skip` (number): Offset for pagination

### `get_signal_details` (~45 tokens)

Use this when the user needs full details for one AI signal by ID, including review and resolution data.

Input parameters:

- `signalId` (string, required): The ID of the signal to retrieve

### `get_signal_stats` (~37 tokens)

Use this when the user asks for aggregate AI signal performance statistics over a specific period.

Input parameters:

- `period` (string): Time period for statistics

### `get_top_traders` (~97 tokens)

Use this when the user wants ranked smart-money traders across supported exchanges with sorting and filtering.

Input parameters:

- `limit` (number): Number of traders to return
- `order` (string): Sort direction
- `rankingType` (string): Ranking snapshot type
- `sortBy` (string): Sort metric (defaults to ranking type)
- `source` (string): Exchange to filter by
- `timeRange` (string): Performance time range

### `get_elite_leaderboard` (~29 tokens)

Use this when the user specifically asks for the elite leaderboard by SmartScore across exchanges.

### `get_trader_profile` (~71 tokens)

Use this when the user needs one trader profile, including metrics and latest positions.

Input parameters:

- `rankingType` (string): Ranking snapshot type
- `source` (string): Exchange the trader is on
- `timeRange` (string): Performance time range
- `traderId` (string, required): The trader ID

### `get_trader_position_history` (~64 tokens)

Use this when the user asks for closed trade history of a specific trader.

Input parameters:

- `limit` (number): Results per page
- `page` (number): Page number
- `source` (string): Exchange
- `traderId` (string, required): The trader ID

### `get_positions` (~93 tokens)

Use this when the user asks for current or historical smart-money positions, optionally filtered by status, source, or symbol.

Input parameters:

- `limit` (number): Number of positions to return
- `offset` (number): Offset for pagination
- `source` (string): Exchange filter
- `status` (string): Position status filter
- `symbol` (string): Filter by trading pair, e.g. BTC, ETHUSDT

### `get_market_stats` (~57 tokens)

Use this when the user asks for aggregate market stats (positions, PNL, win rate), optionally scoped by source and period.

Input parameters:

- `period` (string): Time period for closed position stats
- `source` (string): Exchange filter

### `get_exchanges` (~27 tokens)

Use this when the user asks which exchanges are currently available in TraderSpy smart-money tracking.

### `get_price` (~69 tokens)

Get real-time price data for one or more crypto futures symbols. Returns current price, 24h high/low, volume, and 24h price change percentage.

Input parameters:

- `symbols` (array, required): List of symbols to get prices for, e.g. ["BTCUSDT", "ETHUSDT"]

### `get_candles` (~85 tokens)

Get OHLCV (Open, High, Low, Close, Volume) candle data for a crypto futures symbol. Useful for charting, price history, and technical analysis.

Input parameters:

- `interval` (string): Candle interval/timeframe
- `limit` (number): Number of candles to return
- `symbol` (string, required): Trading pair symbol, e.g. BTCUSDT

### `get_tracked_symbols` (~27 tokens)

List all crypto futures symbols currently tracked by TraderSpy with real-time candle data available.

### `get_technical_indicators` (~102 tokens)

Compute technical indicators (RSI, MACD, EMA, SMA, Bollinger Bands, ATR, ADX, Stochastic, OBV, VWAP, CCI, MFI, Williams %R) for a crypto futures symbol at a specific timeframe.

Input parameters:

- `indicators` (array): Technical indicators to compute
- `interval` (string): Candle interval/timeframe
- `symbol` (string, required): Trading pair symbol, e.g. BTCUSDT

### `get_my_account` (~61 tokens)

Use this when the user asks about THEIR OWN TraderSpy account: Hyperliquid balance, open positions, unrealized PnL, paper-trading account, or whether agent trading is enabled. Requires a personal MCP connection (key from traderspy.app Settings).

## Diagnostics

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

## Score history

- 2026-08-15: 74

## Links

- Remote endpoint: https://mcp.traderspy.app/mcp
- Authorisation metadata: https://mcp.traderspy.app/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/target1m/traderspy-mcp
- Website: https://traderspy.app/mcp
- Changelog RSS feed: https://verifymcp.io/servers/app-traderspy-traderspy/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-traderspy-traderspy/mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-traderspy-traderspy/mcp