TraderSpy

What TraderSpy MCP server does

TraderSpy MCP server gives MCP-compatible assistants access to TraderSpy’s crypto futures data. Its read-only tools cover four main areas: AI-generated trading signals, smart-money and trader activity, market data and technical analysis, and historical condition testing.

Signal tools return recent setups, full signal context, current applicability, and performance statistics. Trader and position tools expose ranked traders, SmartScore leaders, individual profiles, closed-trade history, and live or historical positions. Market tools provide prices, OHLCV candles, derivatives data, and tracked venue or symbol coverage.

The server is intended for analysis and research. It does not place, close, or modify orders, handle transfers, or expose a user’s private trading account.

How it works

The service is hosted at https://mcp.traderspy.app/mcp and uses Streamable HTTP. An MCP client sends tool requests to that endpoint, and TraderSpy returns public crypto market data. The tools are read-only, so an assistant can inspect conditions and produce analysis but cannot execute a trade through this connection.

Authentication depends on the client. Clients that support the server’s authorization flow can sign in with a TraderSpy account. Clients without a usable sign-in window can use a personal URL containing an MCP key or send the key as a bearer token. A free TraderSpy account is described as sufficient for OAuth access.

Setup and configuration

Add the hosted endpoint to an MCP client that supports Streamable HTTP. Claude, Claude Code, ChatGPT, Grok, and Gemini use the account authorization flow described in the repository. Cursor, Cline, Windsurf, scripts, and similar clients can use a personal key from the TraderSpy MCP page.

For a URL-based configuration, use the hosted endpoint with a token parameter:

https://mcp.traderspy.app/mcp?token=mcp_YOUR_KEY

A client that accepts HTTP headers can instead send the key as a bearer token. Claude Code can connect with its MCP command or the repository plugin. Cursor, Cline, and Gemini CLI also have repository-specific setup paths documented by the project.

Tools and capabilities

TraderSpy MCP server exposes tools for:

• Filtering signals by symbol, side, entry, targets, stop, strength, and validation score.
• Reviewing a signal’s conditions, absolute price levels, outcome, and current price.
• Measuring signal win rate, profit factor, and resolution results over a period.
• Ranking traders by exchange and inspecting profiles, open positions, and closed trades.
• Comparing smart-money long and short exposure across tracked exchanges.
• Reading prices, 24-hour statistics, candles, and a broad set of technical indicators.
• Inspecting funding, open interest, long/short ratios, and taker flow for Binance perpetuals.
• Screening symbols with up to three combined conditions across supported metrics.
• Studying historical occurrences of a condition, including forward returns, excursions, baseline comparison, and current status.

Technical indicators include RSI, MACD, moving averages, Bollinger Bands, ATR, ADX, stochastic, OBV, VWAP, CCI, MFI, Williams %R, ROC, SuperTrend, Ichimoku, Keltner Channels, pivots, and swing support or resistance. Multi-timeframe indicator requests can include up to three intervals.

Limitations and notes

The data is public market information rather than private account data. Coverage depends on the exchanges and symbols tracked by TraderSpy; the repository identifies Binance, Hyperliquid, Bybit, and OKX for smart-money positions. Derivatives requests support up to five Binance perpetuals, symbol screening covers up to 100 pairs, and backtests use no more than 1,000 stored candles.

Every capability is read-only. The connector cannot submit orders, manage positions, withdraw funds, or transfer assets. Clients that do not support the required authentication flow must use a personal MCP key, and Cline configurations must specify the exact streamableHttp transport type rather than falling back to SSE.