_ registry / mcp http-sse · checked 8h ago

trading-signals

https://signals.x70.ai

Registry code: d7ae81893de12994

api record

Live AI crypto trading signals for agents. No API key needed to try — 3 signals + hit rate.

from a public catalogue that lists it, not from the operator

endpoint
https://signals.x70.ai/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is trading-signals live?
Yes — it answered the hub's last check (checked 8h ago). It answered 99% of checks over the last 30 days.
Is trading-signals free to use?
Yes — the hub reached it with no key and no payment.
What tools does trading-signals have?
5 tools: get_signals, get_signal_history, get_signal, register, get_stats.
Is trading-signals safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.7%· all time 99.7%

latency
204ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 305 checks · signed record
  • degraded → live
  • live → degraded· HTTP 502
  • degraded → live
  • unknown → live
_ what it is for
used for
  • get live crypto trading signals
  • get signal history and outcomes
  • get signal performance stats
takes → gives
data → data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open 4 never probed 1 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_stats reads open 15h ago

    Get aggregated performance: hit rate, average ROI per signal, average leverage, breakdown by direction. No API key required.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "days": {
          "type": "number",
          "default": 30,
          "maximum": 90,
          "minimum": 1,
          "description": "Lookback period in days"
        },
        "apiKey": {
          "type": "string",
          "description": "Optional for this tool — aggregate stats are public. Get a free key at https://signals.x70.ai/mcp-signup."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_signals reads unknown never probed

    Fetch live (active) crypto trading signals with entry, SL, TP, leverage, confidence. Optional research-backed filters let you build your own strategy: direction, coin include/exclude, SL distance %, R/R, confidence band, Open Interest range, 24h volume, tags, primary anomaly trigger, day-of-week skips, BTC 24h regime gate. Sorted by live PnL (most profitable first). WORKS WITHOUT AN API KEY: omit apiKey for a free 3-signal preview (coin + direction + confidence); a free account returns up to 100 signals with full reasoning and verified outcomes.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Single coin symbol (e.g. BTC). Case-insensitive. Convenience alias for coinInclude=<coin>."
        },
        "days": {
          "type": "number",
          "default": 7,
          "maximum": 30,
          "minimum": 1,
          "description": "Lookback window in days"
        },
        "limit": {
          "type": "number",
          "default": 10,
          "maximum": 100,
          "minimum": 1,
          "description": "Max signals to return (default 10, max 100)"
        },
        "apiKey": {
          "type": "string",
          "description": "Optional. Your Signals API key. Omit it for a 3-signal anonymous preview; get a free key at https://signals.x70.ai/mcp-signup for full metadata."
        },
        "skipDOW": {
          "type": "string",
          "description": "Comma-separated day names to skip (e.g. \"Saturday,Sunday\"). Mondays toxic, weekends weak."
        },
        "coinOiMax": {
          "type": "number",
          "description": "Maximum open interest in USD. R13 uses $500k-$10M."
        },
        "coinOiMin": {
          "type": "number",
          "description": "Minimum open interest in USD (e.g. 500000 for $500k). OI <$500k coins historically toxic."
        },
        "direction": {
          "enum": [
            "bullish",
            "bearish",
            "any"
          ],
          "type": "string",
          "description": "Filter by signal direction. \"bullish\" = long. Default = any."
        },
        "coinVolMin": {
          "type": "number",
          "description": "Minimum 24h notional volume in USD."
        },
        "coinExclude": {
          "type": "string",
          "description": "Comma-separated coin blocklist. Hyper-blacklist used by Lean v2-R: \"kPEPE,ADA,HYPER,LDO,LINEA,2Z\"."
        },
        "coinInclude": {
          "type": "string",
          "description": "Comma-separated coin allowlist (e.g. \"BTC,ETH,SOL\")."
        },
        "skipHourUtc": {
          "type": "string",
          "description": "Comma-separated hours UTC to skip (0..23). EU/US overlap 9-13 weakest."
        },
        "tagsInclude": {
          "type": "string",
          "description": "Comma-separated tags (any-of match)."
        },
        "btcRet24hMax": {
          "type": "number",
          "description": "Skip if BTC 24h return % > this (e.g. 1.5). H1 regime gate: BTC rally rotates flow away from alts."
        },
        "btcRet24hMin": {
          "type": "number",
          "description": "Skip if BTC 24h return % < this."
        },
        "slDistPctMax": {
          "type": "number",
          "description": "Maximum stop-loss distance in %."
        },
        "slDistPctMin": {
          "type": "number",
          "description": "Minimum stop-loss distance in % (e.g. 3 = ≥3% to SL). SL≥3 drops the toxic [2,3) bucket."
        },
        "confidenceMax": {
          "type": "number",
          "maximum": 1,
          "minimum": 0,
          "description": "Maximum confidence (0..1). Best band 0.62-0.76."
        },
        "confidenceMin": {
          "type": "number",
          "maximum": 1,
          "minimum": 0,
          "description": "Minimum confidence (0..1). Counter-intuitive: >0.76 historically underperforms."
        },
        "primaryTrigger": {
          "type": "string",
          "description": "Sentinel anomaly trigger name (e.g. \"vpin_toxicity\" for the S9 Vpin Sniper preset)."
        },
        "riskRewardRatioMax": {
          "type": "number",
          "description": "Maximum risk/reward ratio. Champion v1 uses RR<1.5."
        },
        "riskRewardRatioMin": {
          "type": "number",
          "description": "Minimum risk/reward ratio."
        }
      },
      "additionalProperties": false
    }
    arguments 110 lines
  • get_signal_history reads unknown never probed

    Fetch historical (verified) signals with pagination. Returns resolved signals (success/failed) ordered newest-first.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Filter by coin symbol (e.g. BTC, ETH). Case-insensitive."
        },
        "days": {
          "type": "number",
          "default": 30,
          "maximum": 90,
          "minimum": 1,
          "description": "Lookback window in days"
        },
        "limit": {
          "type": "number",
          "default": 10,
          "maximum": 100,
          "minimum": 1,
          "description": "Max signals per page (default 10, max 100)"
        },
        "apiKey": {
          "type": "string",
          "description": "Required. Get a free key at https://signals.x70.ai/mcp-signup."
        },
        "cursor": {
          "type": "string",
          "description": "Pagination cursor (signal ID). Pass the last signal ID from previous page to get next page."
        },
        "status": {
          "enum": [
            "success",
            "failed",
            "all"
          ],
          "type": "string",
          "default": "all",
          "description": "Filter by verification outcome"
        }
      },
      "additionalProperties": false
    }
    arguments 43 lines
  • get_signal reads unknown never probed

    Fetch a single signal by ID with live price and PnL. Use to check verification status and outcome.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "signalId"
      ],
      "properties": {
        "apiKey": {
          "type": "string",
          "description": "Required. Get a free key at https://signals.x70.ai/mcp-signup."
        },
        "signalId": {
          "type": "string",
          "description": "Signal ID to look up"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • register reads unknown never probed

    DEPRECATED — no longer issues API keys. Returns a link to https://signals.x70.ai/mcp-signup, where keys are created from a free account. Every other tool works without a key (3-signal preview), so there is no need to call this or to collect anyone's personal details for it.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "name": {
          "type": "string",
          "description": "Ignored — kept for backward compatibility"
        },
        "email": {
          "type": "string",
          "format": "email",
          "description": "Ignored — kept for backward compatibility"
        },
        "purpose": {
          "type": "string",
          "description": "Ignored — kept for backward compatibility"
        },
        "githubUrl": {
          "type": "string",
          "format": "uri",
          "description": "Ignored — kept for backward compatibility"
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d7ae81893de12994.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d7ae81893de12994/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d7ae81893de12994/badge.svg)](https://brick.blue/agent/d7ae81893de12994?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.