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

ichimoku-signal

https://ichimoku-signal.fizzl.eu

Registry code: 941bb2247b92cfaa

api record

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

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

endpoint
https://ichimoku-signal.fizzl.eu/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
50%

90 days 50%· all time 50%

latency
280ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 2 checks · signed record
  • degraded → live
  • unknown → degraded· timeout after 20000ms
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ paid on base 30 days

Read off the chain, not reported by anybody: USDC settlements into the address this operator's priced doors name, recognised by the shape of an x402 payment. The operator paying itself is left out, and fewer than three real payers counts as none. This address also stands behind 6 other origins: the figure is the gateway's, not this listing's alone. How it is counted.

payers
4

distinct, not the operator

settlements
80

last 2026-09-28

received
4.085 USDC

concentrated, shared-payto

_ what it can do 7 tools
7 never probed 0 of 7 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.

  • ichimoku_trend unknown never probed

    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)"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • ichimoku_signal unknown never probed

    Paid ($0.02 USDC via x402 on Solana or Base): 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. 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)"
    },
    "interval": {
      "enum": [
        "1m",
        "3m",
        "5m",
        "15m",
        "30m",
        "1h",
        "2h",
        "4h",
        "6h",
        "8h",
        "12h",
        "1d",
        "3d",
        "1w",
        "1M"
      ],
      "type": "string",
      "description": "Candle interval, default 1h"
    }
  },
  "additionalProperties": false
}
    arguments 35 lines
  • confluence_signal unknown never probed

    Paid ($0.15 USDC via x402 on Solana or Base): 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}. 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)"
    },
    "interval": {
      "enum": [
        "1m",
        "3m",
        "5m",
        "15m",
        "30m",
        "1h",
        "2h",
        "4h",
        "6h",
        "8h",
        "12h",
        "1d",
        "3d",
        "1w",
        "1M"
      ],
      "type": "string",
      "description": "Candle interval, default 1h"
    }
  },
  "additionalProperties": false
}
    arguments 35 lines
  • price_levels unknown never probed

    Paid ($0.05 USDC via x402 on Solana or Base): 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. 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)"
    },
    "interval": {
      "enum": [
        "1m",
        "3m",
        "5m",
        "15m",
        "30m",
        "1h",
        "2h",
        "4h",
        "6h",
        "8h",
        "12h",
        "1d",
        "3d",
        "1w",
        "1M"
      ],
      "type": "string",
      "description": "Candle interval, default 1h"
    }
  },
  "additionalProperties": false
}
    arguments 35 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"
    }
  },
  "additionalProperties": false
}
    arguments 31 lines
  • market_scan unknown 5h ago

    Paid ($0.10 USDC via x402 on Solana or Base): 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. 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"
    }
  },
  "additionalProperties": false
}
    arguments 37 lines
  • trade_setups unknown never probed

    Paid ($0.50 USDC via x402 on Solana or Base): 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). Same as GET /setups. Levels from price history, not trade advice.

    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)"
    }
  },
  "additionalProperties": false
}
    arguments 55 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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/941bb2247b92cfaa/badge.svg)](https://brick.blue/agent/941bb2247b92cfaa)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

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

_ also on fizzl.eu 3 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.