app.traderspy/traderspy

Est-ce que app.traderspy/traderspy est sûr ?

Au dernier audit MCP Hub, le serveur MCP « app.traderspy/traderspy » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 17 outils

• backtest_condition≈ 1697 tokens

  What happened AFTER a condition in the past, on one symbol and timeframe — "how did BTC do after RSI dropped below 30 on 4h", "is a golden cross on ETH daily actually bullish", "what usually follows a −5% day on SOL". Runs an event study over the whole stored tape (up to 1000 candles: ~41 days on 1h, ~166 days on 4h, ~3 years on 1d): occurrences, average / median forward return, win rate, average best and worst excursion per horizon, the unconditional baseline over the same tape and the EDGE the condition adds over it, the last five episodes, and whether the condition is active on the latest bar. Same condition vocabulary as screen_symbols. Quote the edge and the sample size together — a 3-sample stat is an anecdote.

  Paramètres, retour & exemple (4)

  Paramètres

  • symbol · string · requis
    Trading pair, e.g. BTCUSDT (a bare "BTC" is read as its USDT perpetual)
  • horizons · array · optionnel
    Bars ahead to measure returns over (≤ 4). Default per interval ≈ 4h / 1d / 3d: 1h → [4, 24, 72], 4h → [6, 18, 42], 1d → [1, 3, 7].
  • interval · string · optionnel · 1m | 5m | 15m | 1h | 4h | 1d
    Candle timeframe
  • conditions · array · requis
    Up to 3 conditions, AND-ed. Examples: RSI oversold = {"metric":"rsi","op":"lt","value":30}; above the 200 EMA = {"metric":"priceVsEma","op":"gt","value":0,"period":200}; golden cross = {"metric":"emaSpread","op":"crossAbove","value":0,"period":50,"period2":200}; MACD bullish cross = {"metric":"macdHistogram","op":"crossAbove","value":0}; dumped 5% in a day = {"metric":"changePct","op":"lt","value":-5,"period":24}.

  Exemple d'appel

  {"name": "backtest_condition", "arguments": {"symbol": "texte", "conditions": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"to": "texte", "tip": "texte", "url": "texte", "bars": 1, "from": "texte", "recent": "texte", "symbol": "texte", "horizons": "texte", "interval": "texte", "warnings": "texte", "activeNow": true, "conditions": "texte"}}

• get_candles≈ 398 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · number · optionnel
    Number of candles to return
  • symbol · string · requis
    Trading pair symbol, e.g. BTCUSDT
  • interval · string · optionnel · 1m | 5m | 15m | 1h | 4h | 1d
    Candle interval/timeframe

  Exemple d'appel

  {"name": "get_candles", "arguments": {"symbol": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"symbol": "texte", "candles": "texte", "interval": "texte"}}

• get_derivatives≈ 490 tokens

  Funding rate, open interest and positioning for Binance USDⓈ-M perpetual futures — the derivatives questions candles cannot answer: is funding high (who is paying whom, annualized), is open interest building or unwinding (24h/4h change, and the OI×price regime: new longs, short covering, new shorts, long liquidation), and which way accounts lean (top-trader long/short by position, all-account ratio, taker buy/sell flow). Each symbol carries plain-language notes — quote those. Up to 5 symbols per call; data is 60s fresh.

  Paramètres, retour & exemple (1)

  Paramètres

  • symbols · array · requis
    Up to 5 Binance USDⓈ-M futures symbols, e.g. ["BTCUSDT", "ETHUSDT"]. A bare base asset ("BTC") is read as its USDT perpetual.

  Exemple d'appel

  {"name": "get_derivatives", "arguments": {"symbols": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": "texte", "count": 1}}

• get_elite_leaderboard≈ 392 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_elite_leaderboard", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"key": "texte", "title": "texte", "source": "texte", "leaders": "texte", "summary": "texte", "lastRunAt": "texte", "updatedAt": "texte", "algorithmDetails": "texte", "algorithmVersion": "texte"}}

• get_exchanges≈ 193 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_exchanges", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": "texte"}}

• get_market_stats≈ 360 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • period · string · optionnel · 4h | 8h | 24h | 7d
    Time period for closed position stats
  • source · string · optionnel · all | binance | hyperliquid | bybit | okx
    Exchange filter

  Exemple d'appel

  {"name": "get_market_stats", "arguments": {"period": "4h", "source": "all"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"avgRoi": 1, "period": "texte", "winRate": 1, "byExchange": "texte", "realizedPnl": 1, "openPositions": 1, "closedInPeriod": 1, "totalPositions": 1}}

• get_positions≈ 720 tokens

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

  Paramètres, retour & exemple (5)

  Paramètres

  • limit · number · optionnel
    Number of positions to return
  • offset · number · optionnel
    Offset for pagination
  • source · string · optionnel · all | binance | hyperliquid | bybit | okx
    Exchange filter
  • status · string · optionnel · all | open | closed
    Position status filter
  • symbol · string · optionnel
    Filter by trading pair, e.g. BTC, ETHUSDT

  Exemple d'appel

  {"name": "get_positions", "arguments": {"limit": 1, "offset": 1, "source": "all", "status": "all", "symbol": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "data": "texte", "pagination": "texte"}}

• get_price≈ 362 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • symbols · array · requis
    List of symbols to get prices for, e.g. ["BTCUSDT", "ETHUSDT"]

  Exemple d'appel

  {"name": "get_price", "arguments": {"symbols": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": "texte"}}

• get_signal_details≈ 958 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • signalId · string · requis
    The ID of the signal to retrieve

  Exemple d'appel

  {"name": "get_signal_details", "arguments": {"signalId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "tip": "texte", "url": "texte", "coin": "texte", "price": 1, "action": "texte", "history": "texte", "targets": "texte", "aiReview": "texte", "createdAt": "texte", "howToRead": "texte", "livePrice": 1}}

• get_signal_stats≈ 701 tokens

  Use this when the user asks for aggregate AI signal performance statistics over a specific period — overall, or for one strategy (preset) by name. The answer also breaks the period down per strategy (byStrategy), which is how to learn the strategy names for get_signals.

  Paramètres, retour & exemple (2)

  Paramètres

  • period · string · optionnel · 4h | 8h | 24h | 7d
    Time period for statistics
  • strategy · string · optionnel
    Only the signals of one AI strategy (preset), matched by part of its name, case-insensitive.

  Exemple d'appel

  {"name": "get_signal_stats", "arguments": {"period": "4h", "strategy": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "total": 1, "pending": 1, "stopped": 1, "warning": "texte", "winRate": 1, "strategy": "texte", "highCount": 1, "howToRead": "texte", "byStrategy": "texte", "targetHits": 1}}

• get_signals≈ 1011 tokens

  Use this when the user asks for recent public AI crypto trading signals, optionally filtered by coin, importance, strategy (the preset that produced them, by name) 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.

  Paramètres, retour & exemple (5)

  Paramètres

  • coin · string · optionnel
    Filter by coin symbol, e.g. BTC, ETH
  • skip · number · optionnel
    Offset for pagination
  • limit · number · optionnel
    Number of signals to return
  • strategy · string · optionnel
    Filter by the AI strategy (preset) that produced the signal — part of its name, words in order, case-insensitive, e.g. "ATR Squeeze" or "Triple Oversold". get_signal_stats (period 7d) lists the strategies that fired recently with their names; a filter that matches nothing answers with the closest names.
  • importance · string · optionnel · high | medium | low | all
    Filter by signal importance

  Exemple d'appel

  {"name": "get_signals", "arguments": {"coin": "texte", "skip": 1, "limit": 1, "strategy": "texte", "importance": "high"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tip": "texte", "data": "texte", "warning": "texte", "pagination": "texte"}}

• get_technical_indicators≈ 2297 tokens

  Technical analysis for a crypto futures symbol. 19 indicators: RSI, MACD, EMA, SMA, Bollinger Bands, ATR, ADX (+DI/−DI), Stochastic, OBV (with price divergence), VWAP, CCI, MFI, Williams %R, ROC, SuperTrend, Ichimoku, Keltner Channels, classic pivot points and swing support/resistance levels. Every indicator returns its current value, the previous bar, a rising/falling/flat direction, a short `series` history and — where it applies — zones and crossovers. EMA/SMA accept several periods at once (default 20/50/200); every period is overridable via `periods`. Pass `intervals` (up to 3) to get 1h/4h/1d in ONE call with a multi-timeframe `confluence` verdict. Each timeframe also carries a `summary` (bias, trend, momentum, volatility, volume, plain-language notes) computed from a fixed indicator set — quote its notes rather than the raw score. For several coins pass `symbols` (up to 3) instead of one call per coin: ONE call and one quota unit, one entry per symbol in `data`.

  Paramètres, retour & exemple (7)

  Paramètres

  • symbol · string · optionnel
    Trading pair symbol, e.g. BTCUSDT. For several pairs pass `symbols` instead.
  • history · integer · optionnel
    Prior values returned per indicator as `series` (oldest → newest, length history + 1). 0 = latest only.
  • periods · object · optionnel
    Optional period overrides, e.g. {"ema":[9,21,55,200],"rsi":7}
  • symbols · array · optionnel
    Up to 3 trading pairs in ONE call (one quota unit), e.g. ["BTCUSDT","ETHUSDT","SOLUSDT"]. The response then carries one entry per symbol in `data`, each shaped like the single-symbol response.
  • interval · string · optionnel · 1m | 5m | 15m | 1h | 4h | 1d
    Candle timeframe. Ignored when `intervals` is given.
  • intervals · array · optionnel
    Up to 3 timeframes in ONE call (one quota unit), e.g. ["1h","4h","1d"]. The response then carries per-timeframe results plus a `confluence` verdict.
  • indicators · array · optionnel
    Indicators to compute. `levels` = swing support/resistance from price structure, `pivots` = classic floor pivots from the previous day.

  Exemple d'appel

  {"name": "get_technical_indicators", "arguments": {"symbol": "texte", "history": 1, "periods": {}, "symbols": [], "interval": "1m", "intervals": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tip": "texte", "url": "texte", "data": "texte", "count": 1, "price": 1, "symbol": "texte", "candles": 1, "summary": "texte", "interval": "texte", "settings": "texte", "warnings": "texte", "confluence": "texte"}}

• get_top_traders≈ 395 tokens

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

  Paramètres, retour & exemple (6)

  Paramètres

  • limit · number · optionnel
    Number of traders to return
  • order · string · optionnel · ASC | DESC
    Sort direction
  • sortBy · string · optionnel · ROI | PNL | SCORE
    Sort metric (defaults to ranking type)
  • source · string · optionnel · all | binance | hyperliquid | bybit | okx
    Exchange to filter by
  • timeRange · string · optionnel · 24h | 3D | 7D | 30D
    Performance time range
  • rankingType · string · optionnel · ROI | PNL
    Ranking snapshot type

  Exemple d'appel

  {"name": "get_top_traders", "arguments": {"limit": 1, "order": "ASC", "sortBy": "ROI", "source": "all", "timeRange": "24h", "rankingType": "ROI"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": "texte"}}

• get_tracked_symbols≈ 153 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_tracked_symbols", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"count": 1, "symbols": "texte"}}

• get_trader_position_history≈ 700 tokens

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

  Paramètres, retour & exemple (4)

  Paramètres

  • page · number · optionnel
    Page number
  • limit · number · optionnel
    Results per page
  • source · string · optionnel · binance | hyperliquid | bybit | okx
    Exchange
  • traderId · string · requis
    The trader ID

  Exemple d'appel

  {"name": "get_trader_position_history", "arguments": {"traderId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tip": "texte", "url": "texte", "data": "texte", "pagination": "texte"}}

• get_trader_profile≈ 787 tokens

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

  Paramètres, retour & exemple (4)

  Paramètres

  • source · string · optionnel · binance | hyperliquid | bybit | okx
    Exchange the trader is on
  • traderId · string · requis
    The trader ID
  • timeRange · string · optionnel · 24h | 3D | 7D | 30D
    Performance time range
  • rankingType · string · optionnel · ROI | PNL
    Ranking snapshot type

  Exemple d'appel

  {"name": "get_trader_profile", "arguments": {"traderId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"aum": 1, "mdd": 1, "pnl": 1, "roi": 1, "tip": "texte", "url": "texte", "rank": 1, "source": "texte", "winRate": 1, "avatarUrl": "texte", "positions": "texte", "timeRange": "texte"}}

• screen_symbols≈ 1588 tokens

  Screen MANY crypto futures symbols at once on one timeframe — "which coins are oversold on 4h", "what is above its 200 EMA with rising volume", "show me squeezes". Give up to 3 AND-ed conditions from a fixed metric list (RSI, stochastic, CCI, MFI, Williams %R, ADX, ROC, MACD histogram, ATR%, volume ratio, Bollinger %B / width, price vs EMA, EMA spread, SuperTrend, change %, price) with lt / gt / crossAbove / crossBelow. Scans the most-traded symbols by 24h volume (default 50, max 100) or an explicit list; every row carries the metric values plus bias, trend, RSI, ADX, ATR% and 24h change. With NO conditions and explicit `symbols` it is a side-by-side comparison table ("compare BTC, ETH, SOL"). ONE quota unit however many symbols — always prefer this over calling get_technical_indicators in a loop.

  Paramètres, retour & exemple (7)

  Paramètres

  • limit · integer · optionnel
    Rows to return
  • sortBy · string · optionnel · volume | change24h | metric
    volume (24h quote volume), change24h, or metric (the first condition's metric). Default: metric when conditions are given, else volume.
  • symbols · array · optionnel
    Explicit symbols to scan (≤ 100, e.g. ["BTC","ETH","SOL"]). Omit to scan the most-traded symbols instead. With no `conditions`, every listed symbol is returned as a comparison table.
  • interval · string · optionnel · 1m | 5m | 15m | 1h | 4h | 1d
    Candle timeframe to evaluate on
  • universe · integer · optionnel
    How many of the most-traded symbols (by 24h volume) to scan when `symbols` is omitted (max 100)
  • sortOrder · string · optionnel · asc | desc
  • conditions · array · optionnel
    Up to 3 conditions, AND-ed. Examples: RSI oversold = {"metric":"rsi","op":"lt","value":30}; above the 200 EMA = {"metric":"priceVsEma","op":"gt","value":0,"period":200}; golden cross = {"metric":"emaSpread","op":"crossAbove","value":0,"period":50,"period2":200}; MACD bullish cross = {"metric":"macdHistogram","op":"crossAbove","value":0}; dumped 5% in a day = {"metric":"changePct","op":"lt","value":-5,"period":24}.

  Exemple d'appel

  {"name": "screen_symbols", "arguments": {"limit": 1, "sortBy": "volume", "symbols": [], "interval": "1m", "universe": 1, "sortOrder": "asc"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tip": "texte", "sortBy": "texte", "matched": 1, "results": "texte", "interval": "texte", "returned": 1, "universe": "texte", "warnings": "texte", "sortOrder": "texte", "conditions": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.traderspy.app/mcp