Trading Signals

io.github.roman-rrPublished by GitHub account roman-rrv1.1.0Updated Nov 2, 2026

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

The publisher's own server: SIGNALS Loyalty Agent Platform

VerifiedStreamable HTTPWeb executableFinanceAI & ML

Overview

AI-generated overview

Remote MCP server that gives an assistant live AI-generated crypto trading signals with reasoning, verification outcomes and aggregate performance stats.

What you can do
  • List open crypto trading signals with coin, direction, confidence and the reasoning behind each
  • Fetch a single signal by ID, live or resolved, with price, PnL and whether take-profit or stop-loss was hit
  • Review resolved signal history, newest first, with each verification outcome
  • Read aggregate stats such as hit rate, verified count, average leverage and direction breakdown, plus ROI figures with a key
  • Call a deprecated register tool that only returns a sign-up link
When to use it
Useful when you want an assistant to surface current crypto trade ideas, explain the reasoning behind them, or review how past signals performed. It suits research and paper-trading workflows rather than automated order execution.
Requirements
A remote HTTP endpoint; no local runtime or package. The public URL works without an account and returns a 3-signal preview. Full signals, history and ROI stats need sign-in through the client or an API key supplied by header X-Api-Key, query parameter apiKey, or the SIGNALS_API_KEY environment variable for Codex.
Before you install
Signals are third-party trading suggestions, not advice, and the README's example rows are explicitly not live data. Pro features (entry, stop-loss, take-profit, leverage, position size) cost $35/month or $300/year after a 14-day trial; nothing is charged unless you subscribe. An API key in a URL query string can leak through logs. The register tool is deprecated and stores nothing.

Installation

In SourceWeft

  1. Open Trading Signals in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

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/io.github.roman-rr%2Ftrading-signals/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "trading-signals": {
      "type": "http",
      "url": "https://signals.x70.ai/mcp"
    }
  }
}

README

Trading Signals

[Trading Signals for AI Agents]

17 triggers. 44 algorithms. 3 AI experts. Every signal backed by causal reasoning and verified against real prices.

Live crypto trading signals for Claude Code, OpenAI Codex, Cursor, Windsurf & 30+ AI agents. Every signal comes with its reasoning — a transmission chain showing exactly which data points led to the trade — and is verified against real prices. Pro adds the trade levels: entry, stop-loss, take-profit, leverage and position size. See Pricing.

Updates, new features and how-tos: follow @x70signals on X.

Install

Claude Code Plugin (recommended)

bash
/plugin install roman-rr/trading-skills

npx (Claude Code, Codex, Cursor, Windsurf, etc.)

bash
npx skills add roman-rr/trading-skills

MCP Server (Claude, Cursor, VS Code, Codex)

Sign in from your agent (recommended). Add the URL below and 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 Code

bash
claude mcp add --transport http trading-signals https://signals.x70.ai/mcp/connect# then in Claude Code: /mcp → trading-signals → Authenticate

Claude app (Desktop & claude.ai) — Customize → Connectors → Add custom connector, URL https://signals.x70.ai/mcp/connect.

Cursor (~/.cursor/mcp.json)

json
{  "mcpServers": {    "trading-signals": { "url": "https://signals.x70.ai/mcp/connect" }  }}

Try it without an account: use https://signals.x70.ai/mcp instead — 3 live signals plus the verified hit rate. When you ask for more, your client offers to sign in.

With an API key (Codex, scripts, clients that can't sign in) — get a free key at https://signals.x70.ai/mcp-signup?utm_content=github-readme; the API Key page has copy-paste setup for every client.

bash
claude mcp add --transport http trading-signals https://signals.x70.ai/mcp --header "X-Api-Key: YOUR_KEY"

Claude app with a key: https://signals.x70.ai/mcp?apiKey=YOUR_KEY (connectors have no header field).

Codex (~/.codex/config.toml, key in env var SIGNALS_API_KEY)

toml
[mcp_servers.trading-signals]url = "https://signals.x70.ai/mcp"bearer_token_env_var = "SIGNALS_API_KEY"

Tools: get_signals, get_signal, get_signal_history, get_stats (register is deprecated — keys come from the dashboard).

OpenAI Codex CLI

See agents/openai.yaml for agent configuration.

Manual

bash
# Claude Codegit clone https://github.com/roman-rr/trading-skills.gitcp -r trading-skills/trading-signals ~/.claude/skills/trading-signals
# OpenAI Codex CLIcp -r trading-skills/trading-signals ~/.codex/skills/trading-signals

Always Watching

17 Triggers. 6 Groups. Every Minute.

The sentinel continuously scans 50+ perpetual markets for anomalies across six orthogonal dimensions -- volume, positioning, price dynamics, cross-asset flows, microstructure, and options-derived signals. A signal fires only when multiple independent dimensions agree, filtering noise from genuine opportunities.

Multi-Expert Consensus

Three specialized AI experts analyze every opportunity independently -- each with a different lens on market structure. Signals require agreement; conflicting views are flagged or filtered. The system continuously learns which analytical approaches perform best per market condition.

Research-Grounded

44 Scientific Methods. 53 Academic Citations.

Every algorithm is grounded in peer-reviewed research from quantitative finance, statistics, and machine learning -- spanning position sizing, anomaly detection, technical analysis, market microstructure, and adaptive risk management.

What You Get

FeatureDescription
Live signalsBullish/bearish with full trade setup -- entry, SL, TP, leverage, position size
Transmission chains2-4 causal reasoning steps per signal with specific data points
50+ coinsDynamically selected from top volume, funding, and OI on Hyperliquid perps
Confidence score0-100 AI conviction level per signal
Auto-verificationEvery signal tracked against real prices -- TP/SL monitoring every minute
Paper trading P&LReal trades on a virtual account with optimal position sizing
Dynamic risk controlConfidence-based leverage caps, volatility-calibrated SL, automatic regime detection
Performance statsHit rate, cumulative ROI, profit factor, breakdown by direction/coin/model

Signal Preview

Example rows — not live data. Entry, SL, TP and leverage are returned on Pro; the free plan returns coin, direction, confidence and the reasoning.

CoinDirConfEntrySLTPLevR/RType
BTCBull87%$68,450$67,200$71,8003x2.7momentum_shift
ETHBear82%$3,840$3,920$3,6802x2.0funding_anomaly
SOLBull79%$142.50$138.00$152.002x2.1volume_spike

API Endpoints

MethodPathAuthDescription
POST/api/skill/registerNoDeprecated — returns signup_required; get keys at /mcp-signup
GET/api/skill/signalsAPI keyList signals (active/verified/all)
GET/api/skill/signals/:idAPI keySingle signal detail
GET/api/skill/statsAPI keyPerformance statistics

Example Prompts

Once installed, ask your AI agent:

  • "Get me the latest crypto trading signals"
  • "Show me today's highest-confidence BTC and ETH signals"
  • "What's the 30-day hit rate for these trading signals?"
  • "Build me a Python script that fetches crypto signals and alerts me on Telegram"
  • "Show me verified signals from the last week -- what hit TP?"

Paper-trade it first

Want to see how the signals do before you trade them? Let your agent run the paper-trading bot on your machine. It takes each new signal as a $100 paper position at the live price, charges fees on both sides, and logs every trade, wins and losses, to a CSV you own. No real orders, no exchange account; one Python file, standard library only.

The API Key page has a ready prompt for Claude Code, Codex or Cursor, with your key filled in. Our own copy has been running since Oct 7: its live record.

Pricing

No keyFree keyPro
Signals3-signal previewevery live signal — coin, direction, confidence, reasoningeverything in Free + entry, stop-loss, take-profit, leverage, position size
History—24 hours30 days
Rate limit30 calls/hour per IP300 calls/houreffectively unlimited
Pricefreefree$35/month or $300/year

New accounts get a 14-day Pro trial — no card. Nothing is charged unless you subscribe. Pricing & sign-up

Contributing

Issues, feature requests, and PRs are welcome. Please open an issue first to discuss changes.

If this is useful, a ⭐ helps other people find it.

License

Proprietary — the source is readable; a paid license is required for commercial redistribution. See LICENSE.txt.

Source: README.md at commit 3424b52

Tools

5

register

Register for Trading Signals API

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.

ParametersnameemailpurposegithubUrl

get_signals

Get Live Trading 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.

ParameterscoindayslimitapiKeyskipDOWcoinOiMaxcoinOiMindirectioncoinVolMincoinExcludecoinIncludeskipHourUtc+10 more

get_signal

Get Signal Detail

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.

ParametersapiKeysignalIdrequired

get_stats

Get Trading Performance 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.

ParametersdaysapiKey

get_signal_history

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

ParameterscoindayslimitapiKeycursorstatus

Version history

2
  1. v1.1.0LatestOct 12, 2026
  2. v1.0.0Sep 16, 2026

Score

90% 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.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Signals integrations