TraderSpy MCP

Crypto smart money & AI signals, wired straight into your AI assistant.

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.

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

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.

Contents

Quick start · What it answers · Tool catalogue · Interactive views · Skills · Authentication · Security · Data sources · Architecture · Prompts to try · Changelog

Related MCP server: Simsar MCP

Quick start

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.

Claude (web, desktop and mobile)

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.

Claude Code

As a plugin — also installs the six skills:

/plugin marketplace add target1m/traderspy-mcp
/plugin install traderspy@traderspy-mcp

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.

No browser on that machine (a server, CI)? Export your personal URL before starting Claude Code and the plugin connects with it instead:

export TRADERSPY_MCP_URL="https://mcp.traderspy.app/mcp?token=mcp_YOUR_KEY"

Or as a plain MCP server, then authenticate the same way from /mcp:

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

ChatGPT

TraderSpy is in the ChatGPT plugin directory:

1. Open chatgpt.com/plugins (or Settings → Plugins), search for TraderSpy and click Connect

2. Sign in with your TraderSpy account and click Allow access

3. Pick TraderSpy in a chat with @ or from the + menu

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 (xAI)

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":

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

Grok Build cannot open a sign-in window, so from the terminal it always takes the personal URL:

grok mcp add --transport http traderspy "https://mcp.traderspy.app/mcp?token=mcp_YOUR_KEY"

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.

Cursor

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:

{
  "mcpServers": {
    "traderspy": {
      "url": "https://mcp.traderspy.app/mcp",
      "headers": {
        "Authorization": "Bearer mcp_YOUR_KEY"
      }
    }
  }
}

Cline

cline_mcp_settings.json:

{
  "mcpServers": {
    "traderspy": {
      "type": "streamableHttp",
      "url": "https://mcp.traderspy.app/mcp",
      "headers": {
        "Authorization": "Bearer mcp_YOUR_KEY"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

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.

Gemini CLI

gemini extensions install https://github.com/target1m/traderspy-mcp

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.

Kimi Code

As a plugin — also installs the six skills. In Kimi Code:

/plugins install https://github.com/target1m/traderspy-mcp
/reload

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:

{
  "mcpServers": {
    "traderspy": {
      "url": "https://mcp.traderspy.app/mcp"
    }
  }
}

No browser on that machine? Keep the key out of the file: export it and point Kimi Code at the variable with bearerTokenEnvVar.

{
  "mcpServers": {
    "traderspy": {
      "url": "https://mcp.traderspy.app/mcp",
      "bearerTokenEnvVar": "TRADERSPY_API_KEY"
    }
  }
}

OpenCode

Add the server to opencode.json (project) or ~/.config/opencode/opencode.json (global):

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

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:

{
  "$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}"
      }
    }
  }
}

OpenCode also loads skills from .agents/skills/ and .claude/skills/, so the six skills installed with the skills CLI work in OpenCode too.

GitHub Copilot CLI

As a plugin, which also installs the six skills:

copilot plugin install target1m/traderspy-mcp

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:

copilot mcp add --transport http --header "Authorization: Bearer mcp_YOUR_KEY" \
  traderspy-key https://mcp.traderspy.app/mcp

goose

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:

goose session --with-streamable-http-extension "https://mcp.traderspy.app/mcp"

Every tool is read-only: there is no order, transfer or withdrawal tool. Market data and analysis, not financial advice.

Windsurf and other MCP clients

The personal URL works in any client that takes an MCP server URL:

{
  "traderspy": {
    "type": "http",
    "url": "https://mcp.traderspy.app/mcp?token=mcp_YOUR_KEY"
  }
}

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.

What it answers

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.

Tool catalogue

17 tools, every one read-only, every one annotated readOnlyHint: true.

Signals — 3 tools

Smart money — 7 tools

Market data & research — 7 tools

Interactive views

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.

Skills

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

npx skills add target1m/traderspy-mcp                          # all six
npx skills add target1m/traderspy-mcp --skill market-briefing  # just one

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.

Authentication and limits

Two ways to connect, both tied to your TraderSpy account:

• Sign in (OAuth 2.1, recommended) — Claude, Claude Code, ChatGPT, Grok and Gemini take the bare URL and open the TraderSpy sign-in (dynamic client registration, PKCE, scope mcp.read). There is nothing to copy, and the host renews its own token.

• Personal key — for clients that cannot open a sign-in window. Get it from the Other clients tab at traderspy.app/mcp and send it as 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.

Security

This connector's security model is mostly a list of things that do not exist.

What no credential can do here:

• No order tool. Placing, closing or modifying an order does not exist. The order tools were not hidden or feature-flagged; they were deleted.

• No withdrawal, transfer or deposit tool.

• No account tool. Nothing reads a balance or a position, and the connector has no client toward the trading service at all, so no code path can reach an account even by mistake.

• No standing rules. It cannot create alerts, subscriptions or automations on your account.

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.

Trading belongs in the TraderSpy web app or mobile app, where you are present for it.

Data sources

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.

Architecture

Your 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 · 5,000 premium
       └── 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

Prompts to try

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

Changelog

Links

• TraderSpy — the platform

• traderspy.app/mcp — connect your assistant, get a personal key for other clients, read the tutorial

• Glama listing — independent inspection and tool grading

• mcpi listing — uptime, auth matrix and a classified contract changelog, probed every six hours

• llms-install.md — install walkthrough for AI agents

• Smithery — alternative install path

• Privacy policy · Support

Disclaimer

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.

License

MIT © TraderSpy