app.traderspyPublished by traderspy.appOfficial publisherv3.0.2Updated Oct 24, 2026
AI crypto signals, whale positions, 19 technical indicators, derivatives, screener and backtests
TraderSpy gives an assistant read-only access to crypto futures market data: AI signals, whale positions, prices, indicators, derivatives, screening and…
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/app.traderspy%2Ftraderspy/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"traderspy": {
"type": "http",
"url": "https://mcp.traderspy.app/mcp"
}
}
}Crypto smart money & AI signals, wired straight into your AI assistant.
[TraderSpy MCP connector on Glama] [MCP status] [License: MIT] [Tools] [Transport]
17 read-only tools · 4 exchanges · 19 technical indicators · 3 interactive views One URL. No install, no daemon, no broker, no API keys of your own.
Connect Claude, Claude Code, ChatGPT, Grok, Cursor, Cline or any MCP client to TraderSpy's live crypto futures data: AI-generated signals with real targets, whale positioning across four exchanges, prices, candles, indicators, derivatives, a condition screener and an event-study backtester.
Every tool is read-only. This connector cannot place, close or modify an order, it has no withdrawal or transfer tool, and it cannot see anyone's account. It answers questions with public market data. See Security.
Quick start · What it answers · Tool catalogue · Interactive views · Skills · Authentication · Security · Data sources · Architecture · Prompts to try · Changelog
Everything below points at the same endpoint: https://mcp.traderspy.app/mcp.
Claude, Claude Code, ChatGPT, Grok and Gemini sign in with your TraderSpy account (OAuth), so
there is no key to copy. A free account is enough. Clients that cannot open a sign-in window
(Cursor, Cline, Windsurf, Grok Build, n8n, scripts) use a personal key instead: get it from the
Other clients tab at traderspy.app/mcp. It starts with mcp_,
the page can show it again, and it is revocable at any time.
Settings → Connectors → Add custom connector, paste https://mcp.traderspy.app/mcp, then click
Connect and sign in with your TraderSpy account. No key to paste.
As a plugin — also installs the six skills:
Then type /mcp, pick traderspy and choose Authenticate. Your browser opens the TraderSpy
sign-in once; click Allow access and Claude Code keeps the token. Coming from 1.7.0 or earlier,
which asked for a key at install? That key is no longer used: authenticate once the same way.
The Claude plugin lives in plugins/traderspy, with its own README. No
browser on that machine (a server, CI)? The plugin's server signs in through a browser, so add the
server with your personal URL instead of the plugin. Since 1.12.0 the plugin no longer reads
TRADERSPY_MCP_URL.
Or as a plain MCP server, then authenticate the same way from /mcp:
TraderSpy is in the ChatGPT plugin directory:
Prefer your own connector? Turn on Developer mode in Settings → Security and login, then
click + on the Plugins page, paste https://mcp.traderspy.app/mcp and choose OAuth.
grok.com/connectors → New Connector → Custom, then paste
https://mcp.traderspy.app/mcp. Grok opens the TraderSpy sign-in: sign in and click
Allow access, and leave any client ID and secret fields empty.
No sign-in appeared, or the tools don't answer? Paste your personal URL instead. The key is embedded, so the host's authentication can stay on "None":
Grok Build cannot open a sign-in window, so from the terminal it always takes the personal URL:
As a Grok Build plugin (the server plus the six skills), the repo carries .grok-plugin/plugin.json
and .grok-plugin/mcp.json; the xAI plugin marketplace listing is in review. Grok Build has no
install-time prompt for secrets, so the plugin reads your key from TRADERSPY_API_KEY in the
environment that launches grok.
The personal URL also works as a remote MCP tool in the xAI API. Grok speaks Streamable HTTP and SSE — so does this server.
As a plugin — also installs the six skills. This repo is a Cursor plugin
(.cursor-plugin/plugin.json + mcp.json): install TraderSpy from the Cursor Marketplace
(listing in review), or clone the repo into ~/.cursor/plugins/local/traderspy and run
Developer: Reload Window. Cursor asks for your key as TRADERSPY_API_KEY at install (change it
later under Plugins → Configure) and sends it as a bearer token; it never lands in your repo.
Or as a plain MCP server — .cursor/mcp.json:
cline_mcp_settings.json:
type must be exactly streamableHttp. streamable-http, or leaving type out, falls back to SSE
and the server answers 405. Full walkthrough: llms-install.md.
The extension (gemini-extension.json) adds the server and the six skills. It signs in with
OAuth rather than a key: run /mcp auth traderspy once inside Gemini CLI.
In the Gemini app (gemini.google.com or mobile): Settings → Connected apps, add a custom app,
paste https://mcp.traderspy.app/mcp and sign in. Google offers custom apps only in the US, in
English, on a personal Google account with Keep Activity on.
As a plugin — also installs the six skills. In Kimi Code:
The repo carries .kimi-plugin/plugin.json, and Kimi Code installs the latest release. The first
TraderSpy tool call asks you to sign in: run the /mcp-config login … command Kimi Code prints,
sign in with your TraderSpy account in the browser and click Allow access, then /reload.
Or as a plain MCP server — ~/.kimi-code/mcp.json, then sign in the same way:
No browser on that machine? Keep the key out of the file: export it and point Kimi Code at the
variable with bearerTokenEnvVar.
Add the server to opencode.json (project) or ~/.config/opencode/opencode.json (global):
Then run opencode mcp auth traderspy. Your browser opens the TraderSpy sign-in once. Click
Allow access and OpenCode stores the token.
No browser on that machine? Turn off OAuth detection and send your personal key from the environment:
OpenCode also loads skills from .agents/skills/ and .claude/skills/, so the six skills installed
with the skills CLI work in OpenCode too.
As a plugin, which also installs the six skills:
The plugin manifest is .github/plugin/plugin.json. It points Copilot CLI at
https://mcp.traderspy.app/mcp with no key: Copilot CLI signs in with your TraderSpy account (OAuth)
in the browser, and /mcp auth traderspy opens the sign-in again. Copilot CLI passes a plugin's
remote server settings through literally, so a key cannot come from an environment variable here.
No browser on that machine? Skip the plugin and add the server with your personal key under its own name:
Desktop: Add TraderSpy to goose opens goose and adds the extension. Start a new chat. On the first tool call goose opens the TraderSpy sign-in in your browser; click Allow access. There is no key to paste.
CLI: run goose configure, choose Add Extension → Remote Extension (Streamable HTTP), name it traderspy
and enter https://mcp.traderspy.app/mcp. Add no headers. For one session only:
Every tool is read-only: there is no order, transfer or withdrawal tool. Market data and analysis, not financial advice.
The personal URL works in any client that takes an MCP server URL:
A client that implements MCP authorization can take the bare URL instead: the server answers an
unauthenticated tool call with 401 and a WWW-Authenticate header, which starts its sign-in. That
works when the client's OAuth callback is a loopback address (http://localhost:<port>,
http://127.0.0.1:<port>) or one of the hosts above. Custom-scheme callbacks (cursor://,
vscode://) and other web callbacks are refused at registration, so those clients use the personal
URL.
The server publishes this routing to the model itself, so you rarely have to name a tool:
Batch, don't loop. Calls are metered per day, and the tools are built so one call replaces many:
several symbols in a single get_price, three timeframes and three coins in a single
get_technical_indicators (one quota unit, and you get the confluence across the timeframes), and
screen_symbols instead of running indicators symbol by symbol.
17 tools, every one read-only, every one annotated readOnlyHint: true.
In hosts that support MCP Apps, three tools render a real interface instead of a wall of text. Every view is a single self-contained HTML bundle with a deny-all CSP — it makes no network call of its own, because the data arrives inside the tool result.
Verified on claude.ai web with the deployed connector. Hosts without MCP Apps get the same data as text and structured content — nothing degrades.
The plugin ships six skills: playbooks that tell the assistant which tools answer which question,
how to read the fields, and how to present the result without turning market data into advice. They
live in skills/<name>/SKILL.md (Agent Skills format) and load automatically in Claude Code,
Cursor, Grok Build, Gemini CLI, Kimi Code, GitHub Copilot CLI and Codex. The Claude plugin carries a
copy in plugins/traderspy/skills: edit skills/, then run scripts/sync-claude-plugin.sh
(--check fails when the copy is out of date). For the ChatGPT plugin portal, run
scripts/package-skills.sh and upload the ZIPs from dist/skills/.
Any other Agent Skills client can install them with the skills CLI. The skills need the MCP server connected, as shown in Quick start:
Every skill carries the same conduct rules: report what the data shows and leave the decision to the user, never present a hit rate or a backtest as a forecast, and say plainly that the connector cannot place, close or move anything.
Two ways to connect, both tied to your TraderSpy account:
mcp.read). There is
nothing to copy, and the host renews its own token.Authorization: Bearer mcp_…,
or embed it in the URL (https://mcp.traderspy.app/mcp?token=mcp_...) for hosts whose
authentication can only be "None".Treat a personal URL like a password: anyone holding it can spend your daily quota. If it leaks, regenerate it on the same page and the old URL stops working at once. Disconnect all apps on the same page signs every connected assistant out, sign-ins and the personal key alike. Both take effect on the very next call.
A three-coin, three-timeframe get_technical_indicators and a 100-symbol screen_symbols each cost one call,
deliberately — the cheap way to use the connector is also the fast one.
Don't have an account? Sign up free.
This connector's security model is mostly a list of things that do not exist.
What no credential can do here:
Two reasons, and the second is the load-bearing one. First, the Anthropic Software Directory Policy
excludes software that executes financial transactions on a user's behalf — and hiding such tools at
call time is not enough, they must not appear in tools/list. Second, an MCP credential is a
long-lived bearer token handed to a third-party host: everything it can reach is reachable by whoever
holds it. So it reaches reads only.
Acting on what it finds stays with you, on your own exchange account, with you present.
Coverage is the Binance USDⓈ-M perpetual universe, plus perpetuals that trade on Hyperliquid but not
on Binance. get_tracked_symbols is the authoritative list.
Morning brief
"Give me a crypto morning brief: what moved, where funding is stretched, and what the AI signals fired overnight."
Find a setup
"Run the screener: RSI under 30 and ADX above 25 on the 4h, top 100 by volume. For anything it finds, show me the multi-timeframe read."
Check a thesis before acting
"Historically, what happened on SOLUSDT 4h after RSI crossed above 30? Compare it against the baseline over the same tape."
Follow the whales
"Who are the most profitable traders on Hyperliquid right now, and what are they positioned in? Then show me the position history of the top one."
Judge a signal
"Is the latest BTC signal still valid? Show me where price is against its entry, targets and stop."
Check a position you hold elsewhere
"I'm long ETH from 2,400 at 10x. How far is liquidation, and what do the 1h/4h/1d indicators say about it?"
Compare coins
"Compare BTC, ETH and SOL on the 4h: trend, momentum, funding and open interest."
TraderSpy provides market data and analysis, not financial advice. Signal statistics and backtests describe what already happened; they are not a forecast and not a guarantee. Trading crypto futures carries substantial risk. You are responsible for your own decisions.
MIT © TraderSpy
Source: README.md at commit b0adc85
Get AI Signals
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.
coinskiplimitstrategyimportanceGet Signal Details
Use this when the user needs full details for one AI signal by ID, including review and resolution data.
signalIdrequiredGet Signal Statistics
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.
periodstrategyGet Top Traders
Use this when the user wants ranked smart-money traders across supported exchanges with sorting and filtering.
limitordersortBysourcetimeRangerankingTypeGet Elite Leaderboard
Use this when the user specifically asks for the elite leaderboard by SmartScore across exchanges.
Takes no parameters.
Get Trader Profile
Use this when the user needs one trader profile, including metrics and latest positions.
sourcetraderIdrequiredtimeRangerankingTypeGet Trader Position History
Use this when the user asks for closed trade history of a specific trader.
pagelimitsourcetraderIdrequiredGet Smart Money Positions
Use this when the user asks for current or historical smart-money positions, optionally filtered by status, source, or symbol.
limitoffsetsourcestatussymbolGet Market Statistics
Use this when the user asks for aggregate market stats (positions, PNL, win rate), optionally scoped by source and period.
periodsourceGet Tracked Exchanges
Use this when the user asks which exchanges are currently available in TraderSpy smart-money tracking.
Takes no parameters.
Get Live Price
Get real-time price data for one or more crypto futures symbols. Returns current price, 24h high/low, volume, and 24h price change percentage.
symbolsrequiredGet Candles (OHLCV)
Get OHLCV (Open, High, Low, Close, Volume) candle data for a crypto futures symbol. Useful for charting, price history, and technical analysis.
limitsymbolrequiredintervalGet Tracked Symbols
List all crypto futures symbols currently tracked by TraderSpy with real-time candle data available.
Takes no parameters.
Get Technical Indicators
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`.
symbolhistoryperiodssymbolsintervalintervalsindicatorsGet Funding & Open Interest
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.
symbolsrequiredScreen Symbols
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.
limitsortBysymbolsintervaluniversesortOrderconditionsBacktest a Condition
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.
symbolrequiredhorizonsintervalconditionsrequired100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
You ask: It calls: It reads:
"Which coins are oversold?" → screen_symbols() → top 100 by 24h volume, one pass"Is BTC still trending?" → get_technical_indicators() → 1h + 4h + 1d in a single call"What are the whales doing?" → get_positions() → Binance · Hyperliquid · Bybit · OKX"Is this signal still valid?" → get_signal_details() → live price against entry / TP / SL"What happens after this setup?" → backtest_condition() → up to 1000 stored candles/plugin marketplace add target1m/traderspy-mcp/plugin install traderspy@traderspy-mcpclaude mcp add --transport http traderspy "https://mcp.traderspy.app/mcp?token=mcp_YOUR_KEY"claude mcp add --transport http traderspy https://mcp.traderspy.app/mcphttps://mcp.traderspy.app/mcp?token=mcp_YOUR_KEYgrok mcp add --transport http traderspy "https://mcp.traderspy.app/mcp?token=mcp_YOUR_KEY"{ "mcpServers": { "traderspy": { "url": "https://mcp.traderspy.app/mcp", "headers": { "Authorization": "Bearer mcp_YOUR_KEY" } } }}{ "mcpServers": { "traderspy": { "type": "streamableHttp", "url": "https://mcp.traderspy.app/mcp", "headers": { "Authorization": "Bearer mcp_YOUR_KEY" }, "disabled": false, "autoApprove": [] } }}gemini extensions install https://github.com/target1m/traderspy-mcp/plugins install https://github.com/target1m/traderspy-mcp/reload{ "mcpServers": { "traderspy": { "url": "https://mcp.traderspy.app/mcp" } }}{ "mcpServers": { "traderspy": { "url": "https://mcp.traderspy.app/mcp", "bearerTokenEnvVar": "TRADERSPY_API_KEY" } }}{ "$schema": "https://opencode.ai/config.json", "mcp": { "traderspy": { "type": "remote", "url": "https://mcp.traderspy.app/mcp" } }}{ "$schema": "https://opencode.ai/config.json", "mcp": { "traderspy": { "type": "remote", "url": "https://mcp.traderspy.app/mcp", "oauth": false, "headers": { "Authorization": "Bearer {env:TRADERSPY_API_KEY}" } } }}copilot plugin install target1m/traderspy-mcpcopilot mcp add --transport http --header "Authorization: Bearer mcp_YOUR_KEY" \ traderspy-key https://mcp.traderspy.app/mcpgoose session --with-streamable-http-extension "https://mcp.traderspy.app/mcp"{ "traderspy": { "type": "http", "url": "https://mcp.traderspy.app/mcp?token=mcp_YOUR_KEY" }}npx skills add target1m/traderspy-mcp # all sixnpx skills add target1m/traderspy-mcp --skill market-briefing # just oneYour AI client Claude · Claude Code · ChatGPT · Grok · Cursor · Cline · Windsurf │ │ MCP over Streamable HTTP (+ SSE) ▼mcp.traderspy.app/mcp ├── 17 read-only tools no order · no withdrawal · no account ├── 3 MCP Apps views cards and charts where the host supports them ├── per-user daily quota 300 free · 3,500–15,000 on paid plans └── OAuth sign-in · personal key (header or URL) │ ▼TraderSpy platform ├── AI signal engine entry · TP1–TP3 · stop · validation · outcome ├── Smart-money trackers Binance · Hyperliquid · Bybit · OKX ├── Candle store Binance USDⓈ-M + Hyperliquid-only perpetuals └── Binance Futures API funding · open interest · long/short · taker flow