_ registry / mcp streamable-http · checked 2h ago

ichimoku-signal

https://ichimoku-signal.onrender.com

Registry code: d709639c3a267c2f

api record

Free Ichimoku trend; paid confluence, levels, market scan and ranked trade setups via x402.

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

endpoint
https://ichimoku-signal.onrender.com/mcp
protocol
streamable-http ·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 ichimoku-signal live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is ichimoku-signal free to use?
No — it charges per call, from 0.1 USDC, quoted in its own 402 answers.
What tools does ichimoku-signal have?
9 tools: ichimoku_signal, confluence_signal, pair_lookup, price_levels, pair_setup, trade_setups, feedback, ichimoku_trend, ….
Is ichimoku-signal 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
100%

90 days 100%· all time 100%

latency
679ms

last good check

priced tools
1

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 5 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
25

distinct

settlements
124

last 2026-10-30

received on chain
3.548 USDC

shared-payto

_ what it can do 9 tools
1 paid 8 never probed 1 of 9 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.

  • market_scan 0.1 USDC paid 2h ago

    Paid ($0.10 via x402 in USDC on Base, Solana, Algorand or Stellar, in RLUSD on the XRP Ledger, or in USD₮0 on X Layer): the Ichimoku Cloud signal for 148 top-200 coins (stablecoins excluded) in one call, sorted from strongest bullish to strongest bearish by the price's distance from the cloud, with market breadth ("69 of 147 coins bullish") and per coin the signal, price, cloud position, tenkan/kijun cross and exchange. Optional filter on bullish, bearish or neutral. Ichimoku only, no trade plans: for the market's direction at a glance; for coins with entry, stop and targets use trade_setups. Same as GET /scan.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "signal": {
      "enum": [
        "bullish",
        "bearish",
        "neutral"
      ],
      "type": "string",
      "description": "Only return coins with this signal"
    },
    "interval": {
      "enum": [
        "1m",
        "3m",
        "5m",
        "15m",
        "30m",
        "1h",
        "2h",
        "4h",
        "6h",
        "8h",
        "12h",
        "1d",
        "3d",
        "1w",
        "1M"
      ],
      "type": "string",
      "description": "Candle interval, default 1h"
    }
  }
}
    arguments 36 lines
  • ichimoku_signal unknown never probed

    Paid ($0.01 via x402 in USDC on Base, Solana, Algorand or Stellar, in RLUSD on the XRP Ledger, or in USD₮0 on X Layer): the full Ichimoku Cloud signal for a crypto pair on any timeframe (1m to 1M): bullish/bearish/neutral, cloud position, tenkan/kijun cross, price and tenkan, kijun, senkou span A/B values. A "news" field flags recent news (hack, delisting, unlock, legal action) that can break the signal. One pair, Ichimoku only: for six indicators use confluence_signal, for entry/stop/targets price_levels. Requires an x402-capable MCP client; invalid pairs are rejected before payment.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "pair"
  ],
  "properties": {
    "pair": {
      "type": "string",
      "description": "Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins). For the XRP Ledger DEX: xrpl:XRP-RLUSD, xrpl:SOLO-XRP, or with the issuer, xrpl:SOLO.rsoLo2S1kiGeCcn6hCUXVrCpGMWLrRrLZz-XRP"
    },
    "interval": {
      "enum": [
        "1m",
        "3m",
        "5m",
        "15m",
        "30m",
        "1h",
        "2h",
        "4h",
        "6h",
        "8h",
        "12h",
        "1d",
        "3d",
        "1w",
        "1M"
      ],
      "type": "string",
      "description": "Candle interval, default 1h"
    }
  }
}
    arguments 34 lines
  • confluence_signal unknown never probed

    Paid ($0.15 via x402 in USDC on Base, Solana, Algorand or Stellar, in RLUSD on the XRP Ledger, or in USD₮0 on X Layer): six indicators for a crypto pair in one call (Ichimoku, RSI 14, MACD 12/26/9, EMA 50/200, Bollinger Bands 20/2, volume OBV), each with its values and a bullish/bearish/neutral vote, plus the combined signal, confidence (high/medium/low), score and a summary like "4 of 6 indicators bullish". Same as GET /signals/{pair}. A "news" field flags recent news (hack, delisting, unlock, legal action) that can break the signal. One pair you already chose; to find which coins have a setup, use trade_setups. Invalid pairs are rejected before payment.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "pair"
  ],
  "properties": {
    "pair": {
      "type": "string",
      "description": "Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins). For the XRP Ledger DEX: xrpl:XRP-RLUSD, xrpl:SOLO-XRP, or with the issuer, xrpl:SOLO.rsoLo2S1kiGeCcn6hCUXVrCpGMWLrRrLZz-XRP"
    },
    "interval": {
      "enum": [
        "1m",
        "3m",
        "5m",
        "15m",
        "30m",
        "1h",
        "2h",
        "4h",
        "6h",
        "8h",
        "12h",
        "1d",
        "3d",
        "1w",
        "1M"
      ],
      "type": "string",
      "description": "Candle interval, default 1h"
    }
  }
}
    arguments 34 lines
  • pair_lookup unknown 2h ago

    Free: before paying, check whether a crypto pair is supported, on which exchange its candles come from (Binance.US, Kraken, Gate or MEXC, or the XRP Ledger DEX for xrpl: pairs) and which intervals the paid tools accept for it. Another dollar quote (USDT, USD, USDC) can stand in for the one you ask. Fetches no candles and returns no signal; for the daily trend use ichimoku_trend. Limited to 60 calls per hour.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "pair"
  ],
  "properties": {
    "pair": {
      "type": "string",
      "description": "Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins). For the XRP Ledger DEX: xrpl:XRP-RLUSD, xrpl:SOLO-XRP, or with the issuer, xrpl:SOLO.rsoLo2S1kiGeCcn6hCUXVrCpGMWLrRrLZz-XRP"
    }
  }
}
    arguments 13 lines
  • price_levels unknown never probed

    Paid ($0.05 via x402 in USDC on Base, Solana, Algorand or Stellar, in RLUSD on the XRP Ledger, or in USD₮0 on X Layer): price levels for a crypto pair: up to 3 supports and resistances (swing highs/lows and pivots), ATR, pivots, Fibonacci retracements and Ichimoku levels, the bias from the confluence signal, and a long and a short plan (entry, stop, two targets, risk/reward). Same as GET /levels/{pair}. Levels from price history, not trade advice. One pair; for ranked plans across all coins use trade_setups. Invalid pairs are rejected before payment.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "pair"
  ],
  "properties": {
    "pair": {
      "type": "string",
      "description": "Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins). For the XRP Ledger DEX: xrpl:XRP-RLUSD, xrpl:SOLO-XRP, or with the issuer, xrpl:SOLO.rsoLo2S1kiGeCcn6hCUXVrCpGMWLrRrLZz-XRP"
    },
    "interval": {
      "enum": [
        "1m",
        "3m",
        "5m",
        "15m",
        "30m",
        "1h",
        "2h",
        "4h",
        "6h",
        "8h",
        "12h",
        "1d",
        "3d",
        "1w",
        "1M"
      ],
      "type": "string",
      "description": "Candle interval, default 1h"
    }
  }
}
    arguments 34 lines
  • pair_setup unknown never probed

    Paid ($0.10 via x402 in USDC on Base, Solana, Algorand or Stellar, in RLUSD on the XRP Ledger, or in USD₮0 on X Layer): the trade setup for one crypto pair on three horizons at once: short term (1h candles), medium (4h) and long term (1d). Per horizon the six-indicator confluence signal (bias: long, short or none, with confidence) and, when the risk/reward to target 1 is at least 1.5, a plan (entry, stop, two take profit targets, risk/reward); otherwise the reason there is none. Plus alignment: how many horizons point the same way ("3 of 3 horizons short; a setup on 1 of 3"). Same as GET /setup/{pair}. Top-200 coins and XRPL DEX pairs. Not trade advice: in our backtest these setups did no better than random entries after fees. For the ranked list across all coins use trade_setups. Invalid pairs are rejected before payment.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "pair"
  ],
  "properties": {
    "pair": {
      "type": "string",
      "description": "Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins). For the XRP Ledger DEX: xrpl:XRP-RLUSD, xrpl:SOLO-XRP, or with the issuer, xrpl:SOLO.rsoLo2S1kiGeCcn6hCUXVrCpGMWLrRrLZz-XRP"
    }
  }
}
    arguments 13 lines
  • trade_setups unknown never probed

    Paid ($0.50 via x402 in USDC on Base, Solana, Algorand or Stellar, in RLUSD on the XRP Ledger, or in USD₮0 on X Layer): which crypto coins have a trade setup right now. For 148 top-200 coins: the six-indicator confluence signal (Ichimoku, RSI, MACD, EMA 50/200, Bollinger, OBV) and a trade plan in that direction (entry, stop, two take profit targets, risk/reward), ranked by signal strength x risk/reward, lower for high volatility, for support/resistance right after the entry and for thinly traded coins. Filters: direction (long/short/both), min_rr, top, liquid_top (only the N most traded coins). The screener across all coins; for one pair you already chose use confluence_signal and price_levels. Same as GET /setups. Levels from price history, not trade advice. A screener, not a strategy: in our backtest these setups did no better than random entries after fees.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "top": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "How many setups to return (default 10)"
    },
    "min_rr": {
      "type": "number",
      "maximum": 10,
      "minimum": 1,
      "description": "Minimum risk/reward to target 1 (default 1.5)"
    },
    "interval": {
      "enum": [
        "1m",
        "3m",
        "5m",
        "15m",
        "30m",
        "1h",
        "2h",
        "4h",
        "6h",
        "8h",
        "12h",
        "1d",
        "3d",
        "1w",
        "1M"
      ],
      "type": "string",
      "description": "Candle interval, default 4h"
    },
    "direction": {
      "enum": [
        "long",
        "short",
        "both"
      ],
      "type": "string",
      "description": "Only long or only short setups (default both)"
    },
    "liquid_top": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "Only the N most traded coins, e.g. 30 (default all)"
    }
  }
}
    arguments 54 lines
  • feedback unknown never probed

    Report a bug, a missing feature or anything else about this service, in a structured way. Free. A person reads every report; nothing is run or changed automatically.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "message"
  ],
  "properties": {
    "type": {
      "enum": [
        "bug",
        "feature",
        "other"
      ],
      "type": "string",
      "description": "bug, feature (something missing) or other"
    },
    "contact": {
      "type": "string",
      "description": "Optional: how to reach you about it"
    },
    "message": {
      "type": "string",
      "description": "What happened or what you need"
    },
    "endpoint": {
      "type": "string",
      "description": "Optional: the route or tool it is about, e.g. /v1/token"
    }
  }
}
    arguments 30 lines
  • ichimoku_trend unknown 2h ago

    Free: the daily (1d) Ichimoku Cloud trend for a crypto pair (top 200 coins, from Binance.US, Kraken, Gate or MEXC): bullish, bearish or neutral, whether price is above, below or in the cloud, and the tenkan/kijun cross. Limited to 20 calls per hour. For other timeframes and the line values use ichimoku_signal; for six indicators use confluence_signal, for support/resistance and targets price_levels, for every top-200 coin at once market_scan, for ranked trade setups across all coins trade_setups.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "pair"
  ],
  "properties": {
    "pair": {
      "type": "string",
      "description": "Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins). For the XRP Ledger DEX: xrpl:XRP-RLUSD, xrpl:SOLO-XRP, or with the issuer, xrpl:SOLO.rsoLo2S1kiGeCcn6hCUXVrCpGMWLrRrLZz-XRP"
    }
  }
}
    arguments 13 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 d709639c3a267c2f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d709639c3a267c2f/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/d709639c3a267c2f/badge.svg)](https://brick.blue/agent/d709639c3a267c2f?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
100%

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.