Trading Signals is an MCP server that provides live AI crypto trading signals to Claude and other MCP-compatible clients. It exposes read tools for signal retrieval, signal detail lookup, history, and performance statistics. Sign in from your agent, or use an API key from your dashboard.
Add the URL below. Your client opens a browser page where you sign in or create a free account — 14 days of Pro, no card — and click Allow. No key to copy.
claude mcp add --transport http trading-signals https://signals.x70.ai/mcp/connect
Then start Claude Code, run /mcp, choose trading-signals and Authenticate. Added trading-signals before? Run claude mcp remove trading-signals first.
Customize → Connectors → “+” → Add custom connector, name it “Trading Signals”, URL:
https://signals.x70.ai/mcp/connect
{"mcpServers":{"trading-signals":{"url":"https://signals.x70.ai/mcp/connect"}}}
Any other client that supports MCP sign-in: the same URL. Then ask your agent: "show me the latest crypto trading signals".
Use https://signals.x70.ai/mcp instead — for example claude mcp add --transport http trading-signals https://signals.x70.ai/mcp. You get 3 live signals plus our verified hit rate with no account and no card. When you ask for more, your client offers to sign in.
For scripts, Codex and clients that can’t sign in. A free account gives you a key: up to 100 signals with full reasoning and verified outcomes. Pro adds entry / SL / TP / leverage and 30-day history.
Custom connectors have no header field, so the key goes in the connector URL (treat it like a password):
https://signals.x70.ai/mcp?apiKey=YOUR_KEY
claude mcp add --transport http trading-signals https://signals.x70.ai/mcp --header "X-Api-Key: YOUR_KEY"
{"mcpServers":{"trading-signals":{"url":"https://signals.x70.ai/mcp","headers":{"X-Api-Key":"YOUR_KEY"}}}}
[mcp_servers.trading-signals] url = "https://signals.x70.ai/mcp" bearer_token_env_var = "SIGNALS_API_KEY"
smithery mcp add roman-rr/trading-signals
| Tool | Type | Description |
|---|---|---|
| get_signals | Read | Fetch live signals. Pro: entry, SL, TP, leverage. Free: coin + direction. |
| get_signal | Read | Fetch single signal by ID. Check verification status. |
| get_signal_history | Read | Historical (verified) signals with cursor pagination. |
| get_stats | Read | Hit rate, cumulative ROI, avg leverage, by-direction breakdown. |
1. Add https://signals.x70.ai/mcp/connect to your agent and sign in when the browser opens
2. Or use an API key from the API Key page — as the X-Api-Key header, Authorization: Bearer, or ?apiKey= in the URL for clients without headers; the page has copy-paste setup for each client
3. Ask Claude: "Show me the latest crypto trading signals"
4. Ask Claude: "What's the 30-day hit rate?"
| Field | Type | Description |
|---|---|---|
| coin | string | Ticker (BTC, ETH, SOL...) |
| direction | string | bullish or bearish |
| confidence | 0-100 | AI conviction level |
| entryPrice | number | Suggested entry (Pro) |
| stopLoss | number | Stop-loss level (Pro) |
| takeProfit | number | Take-profit target (Pro) |
| leverage | 1-10 | Suggested leverage (Pro) |
| riskRewardRatio | number | R/R ratio (Pro) |
| verification.status | string | unverified, pending, success, failed |
| Tier | Limit |
|---|---|
| Anonymous (no key) | 30 / hr / IP |
| Free key | 300 / hr / key |
| Pro key | 10,000 / hr / key |
Rate limit is anti-abuse, not the product — the sell is data depth. Signing in raises your ceiling; Pro removes it.
/mcp, choose trading-signals and Authenticate; in other clients look for a Sign in / Connect button next to the server. If your client can’t sign in, use an API key (above).X-Api-Key headerhttps://signals.x70.ai/mcp/connect (sign-in) or https://signals.x70.ai/mcp (API key or no account)