Skip to content
Agentmart
Submit a tool

Trading Signals

Live AI crypto trading signals for agents.

Connector by roman-rr · GitHub account verified by the MCP Registry

IndexedLicense unknownRemote (HTTP)Remote (SSE)★ 124
Write a review

Install

Works with Claude Code, VS Code, Cursor, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install connector/roman-rr-trading-signals

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Remote endpoints

  • https://signals.x70.ai/mcp Remote (HTTP)
  • https://signals.x70.ai/mcp/connect Remote (HTTP)
  • https://signals.x70.ai/sse Remote (SSE)

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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

Use cases: finance-accounting

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
5 read · 0 write · 0 deleteRead-only
Secrets
None asked for
Install scripts
Nothing to install (hosted)
Runs as
Hosted (remote endpoint)

Tools by what they do 5

From the running server's own tool list (tools/list) on Oct 25, 2026.

Read 5 · Look things up without changing anything.

  • get_signal
  • get_signal_history
  • get_signals
  • get_stats
  • register

Network hosts it talks to 1

  • signals.x70.ai · found in remote endpoint, install command

Tools (5)

As the server listed them on Oct 25, 2026. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • get_signalGet Signal Detailread-only

    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_historyGet Signal Historyread-only

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

  • get_signalsGet Live Trading Signalsread-only

    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 …

  • get_statsGet Trading Performance Statsread-only

    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.

  • registerRegister for Trading Signals APIread-only

    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.

Compare and alternatives

    Featured in

    Signals

    Stars
    124
    Forks
    15
    Open issues
    0
    Contributors
    1
    Last commit
    Oct 23, 2026 (5 days ago)
    Last release
    Oct 12, 2026 (16 days ago)

    From GitHub (fetched Oct 24, 2026).

    Details

    Registry name
    io.github.roman-rr/trading-signals
    Version
    1.1.0
    Auth
    Auth not stated
    License
    License unknown
    Repository
    github.com/roman-rr/trading-skills
    Website
    signals.x70.ai/mcp-docs
    First seen
    Oct 24, 2026
    Last checked
    Oct 24, 2026
    Source
    Official MCP Registrygithub-graphql
    Cite this page

    Trading Signals MCP server. Agent Mart. https://agentmart.dev/connectors/roman-rr-trading-signals (last updated 2026-10-24)