TraderSpy

REMOTE · MCP.TRADERSPY.APP · SCANNED AUG 15

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

Available components

74 74 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security83

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
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. See how to fix → View diagnostics → Fail
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
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 Usability78

AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 989 tokens (~65/item across 15 items; 15 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management0

Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Supports UI / widget rendering.Pass

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

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.traderspy.app

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.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 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.

15 Aug 26 74

First indexed and scored.

Diagnostics

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 15 Aug 2026 · Probed https://mcp.traderspy.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=traderspy.app	CN=WE1,O=Google Trust Services,C=US	22 Jul 2026	20 Oct 2026	ECDSA 256	ECDSA-SHA256	a671d9cb34df8ac10e0fbebbfbc463bc
SANs: traderspy.app, *.traderspy.app
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC insecure

Validation of mcp.traderspy.app. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
app.	present	23684	8	Verified
traderspy.app.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result	Challenged, unverified
Enforced	On tool calls
HTTP status	200

Protected resource metadata

Retrieved	No
Problem	no_resource_metadata

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.traderspy.app/mcp	Verified	200
http (plaintext)	http://mcp.traderspy.app/mcp	HTTPS enforced	301	https://mcp.traderspy.app/mcp

MCP tools · 15 exposed · ~989 tokens

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.

Tool Tokens

get_candles ~85

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

Input Output Examples

Name	Type	Req	Description
interval	string	–	Candle interval/timeframe
limit	number	–	Number of candles to return
symbol	string	yes	Trading pair symbol, e.g. BTCUSDT

No output schema declared.

No examples provided.

get_elite_leaderboard ~29

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_exchanges ~27

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_market_stats ~57

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

Input Output Examples

Name	Type	Req	Description
period	string	–	Time period for closed position stats
source	string	–	Exchange filter

No output schema declared.

No examples provided.

get_my_account ~61

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_positions ~93

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

Input Output Examples

Name	Type	Req	Description
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

No output schema declared.

No examples provided.

get_price ~69

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 Output Examples

Name	Type	Req	Description
symbols	array	yes	List of symbols to get prices for, e.g. ["BTCUSDT", "ETHUSDT"]

No output schema declared.

No examples provided.

get_signal_details ~45

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

Input Output Examples

Name	Type	Req	Description
signalId	string	yes	The ID of the signal to retrieve

No output schema declared.

No examples provided.

get_signal_stats ~37

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

Input Output Examples

Name	Type	Req	Description
period	string	–	Time period for statistics

No output schema declared.

No examples provided.

get_signals ~125

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 Output Examples

Name	Type	Req	Description
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

No output schema declared.

No examples provided.

get_technical_indicators ~102

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 Output Examples

Name	Type	Req	Description
indicators	array	–	Technical indicators to compute
interval	string	–	Candle interval/timeframe
symbol	string	yes	Trading pair symbol, e.g. BTCUSDT

No output schema declared.

No examples provided.

get_top_traders ~97

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

Input Output Examples

Name	Type	Req	Description
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

No output schema declared.

No examples provided.

get_tracked_symbols ~27

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_trader_position_history ~64

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

Input Output Examples

Name	Type	Req	Description
limit	number	–	Results per page
page	number	–	Page number
source	string	–	Exchange
traderId	string	yes	The trader ID

No output schema declared.

No examples provided.

get_trader_profile ~71

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

Input Output Examples

Name	Type	Req	Description
rankingType	string	–	Ranking snapshot type
source	string	–	Exchange the trader is on
timeRange	string	–	Performance time range
traderId	string	yes	The trader ID

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

15 Aug 15 Aug