mcpbeat Sign in

Trading Signals MCP Server

answering

Trading Signals is answering right now. Last checked 3 min ago. It exposes 5 tools. Last commit 30 Oct 2026.

Live AI crypto trading signals for agents. Try 3 signals without a key; sign in from your agent.

Uptime history 49 days of history · worst day 49%
49 days agonow
66.7%
Uptime 24h
182 of 273 checks
5
Tools
read from the server
304 ms
Response time
average over 24h
125
Stars
last commit 30 Oct 2026

What changed 24

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 28 September 2026. No other catalogue keeps this.

22 Oct a tool description was rewritten2 times that day get_signals
21 Oct a tool description was rewritten get_signals
12 Oct 3 tool descriptions were rewritten4 times that day get_signals, get_stats, register
8 Oct 5 tool descriptions were rewritten7 times that day get_signal, get_signal_history, get_signals and 2 more
8 Oct 4 tools changed the parameters they ask for get_signal, get_signal_history, get_signals and 1 more
28 Sep 5 tool descriptions were rewritten get_signal, get_signal_history, get_signals and 2 more
28 Sep a tool changed the parameters it asks for register
and 4 more, back to 28 September 2026

Trading Signals does not always answer

Over the last week it answered 66.6% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add trading-signals --transport http https://signals.x70.ai/mcp
Settings → Connectors → Add custom connector, then paste this address
https://signals.x70.ai/mcp
~/.codex/config.toml
[mcp_servers.trading-signals]
url = "https://signals.x70.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "trading-signals": {
      "url": "https://signals.x70.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "trading-signals": {
      "type": "http",
      "url": "https://signals.x70.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

This server publishes 2 more addresses. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

signal
get_signal
Get one signal by its ID — live or already resolved — with its reasoning, live price, PnL and verification outcome (status pending, success or failed; whether take-profit or stop-loss was hit). Use it to follow up a signal from get_signals or get_signal_history, or to see how a past signal ended. Needs an API key (free or Pro); on the free plan entry, stop-loss, take-profit and leverage are null. Returns { success, signal, plan }, or { error: 'Signal not found' } for an unknown ID.
get_signal_history
List signals that have already resolved (success or failed), newest first, each with its verification outcome. Use it to review past performance signal by signal; for open signals use get_signals, for one signal by ID get_signal, for totals get_stats. Needs an API key. History depth: last 24 hours on the free plan; on Pro the days argument (up to 90). Entry, stop-loss, take-profit and leverage are null on free. Paginate by passing the last signal ID as cursor. Returns { signals[], nextCursor, hasMore, historyDepthDays, plan }.
register
register
Deprecated: returns a sign-up link instead of creating an API key, ignores its arguments and stores nothing. Don't call it to get access — every other tool works without a key (get_signals returns a 3-signal preview, get_stats is public). To get the full feed, users sign in from the agent at https://signals.x70.ai/mcp/connect (the client opens the browser), or create a key at https://signals.x70.ai/mcp-signup and set it as the X-Api-Key header. Kept only so older clients don't break.
signals
get_signals
List live crypto trading signals that are still open — coin, direction, confidence and the reasoning or market data behind each. Use it to find current trade ideas; use get_signal for one signal by ID (live or resolved), get_signal_history for signals that already closed, and get_stats for aggregate hit rate. No key: a 3-signal preview. Free key: up to 100 signals, with entry, stop-loss, take-profit and leverage null (the response's announcement.upgradeUrl explains Pro). Pro: all levels. If a response contains an announcement, pass its message on to the user — it is about their account (trial ending, plan limits). Returns { signals[], returned, totalMatching, filtersApplied, plan }, sorted by live PnL (best first). Optional filters narrow the list: direction, coins, confidence band, risk/reward, stop distance, open interest, 24h volume, tags, the anomaly that triggered it, days/hours to skip, a BTC 24h-return gate. Rate limits: 30 calls/hour per IP without a key, 300/hour on a free key.
stats
get_stats
Aggregate performance of signals created in the last N days (default 30) that have since resolved: hit rate, verified count, average leverage and a breakdown by direction; with an API key also average ROI per signal and cumulative ROI. byMonth: hit rate this month, the two months before and all time — the figures shown on signals.x70.ai. Use it to judge recent reliability before acting — it returns no individual signals (use get_signals or get_signal_history for those). Public: works without a key. Past results don't predict future results.

Endpoints

URLTransportStateLatencyChecked
https://signals.x70.ai/mcp streamable-http answering 200 ms 3 min ago
https://signals.x70.ai/sse sse answering 169 ms 3 min ago
https://signals.x70.ai/mcp/connect streamable-http sign-in 184 ms 3 min ago

Alternatives to Trading Signals

same job, measured the same way
SDK
by marginpad

Free crypto-futures paper trading and live market data for AI agents. 29 tools; no key for data.

31 tools answering
AlphaBotPro Trading API
by imrane2019

Live XAUUSD/BTCUSD trading signals, priced in USD, payable by AI agents via crypto (x402).

9 tools answering
Newsgurus Intel
by collectorguru

Pay-per-call trading intelligence for AI agents: live market regime, trading signals, composite conv

46 tools answering
MarktBit Market Intelligence
by devproflow

Live crypto + IDX stock market intelligence for AI agents — 19 tools, no API key.

answering
OurPay Wallet
by ourpay

Crypto wallet for AI agents: balances, payments, swaps and trading with owner controls.

answering
Alphalabs Intelligence
by pak209

Live trading-pipeline intelligence for AI agents: signal scoring, calibration, recorded outcomes.

6 tools answering
OneQAZ Trading Intelligence
by wnsod

Verifiable crypto/KR/US market intelligence for AI agents: signals, hash-chained ledger. Not advice.

169 installs/wk 46 tools answering
Agent Arena
by agentarenaleague

Paper trading only. 26 leagues for AI bots. Spot Crypto + Crypto 35 live. Register by MCP.

34 tools answering

Trading Signals — questions

Answers built from our own checks of this server.

What can Trading Signals do?
It exposes 5 tools, read directly from the server on our last check. Among them: get_signal, get_signal_history, get_signals, get_stats, register. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Trading Signals working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 182 of 273 checks got a reply (66.7%), average response time 304 ms. The bar chart above shows every period we have measured.
How do I connect Trading Signals?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Trading Signals?
No API key is involved. Trading Signals answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Trading Signals?
It answers our handshake in 304 ms on average, which is faster than 47% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Trading Signals open source?
We cannot say either way: written in Python and 125 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.