Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ichimoku Signal

REMOTE · ICHIMOKU-SIGNAL.FIZZL.EU

Free Ichimoku trend; paid signals, levels, scan, setups and Telegram signal alerts via x402.

0 this week 78 Trust /100

Last scanned (15 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2915 tokens (~291/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 13 Nov 26 0
    • “feedback” added an optional parameter “payment” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 −1
    • Schema quality: 2377 → 2882 ▼ functional
    • Server version: 1.5.1 → 1.6.0 functional
    • New tool “signal_alert” functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 0
    • Tool “price_levels” rewrote its description, which is the text the model reads security
    • Tool “pair_setup” rewrote its description, which is the text the model reads security
    • Tool “market_scan” rewrote its description, which is the text the model reads security
    • Tool “ichimoku_signal” rewrote its description, which is the text the model reads security
    • Tool “confluence_signal” rewrote its description, which is the text the model reads security
    • Tool “trade_setups” rewrote its description, which is the text the model reads security
  • 31 Oct 26 0
    • Schema quality: 1979 → 2317 ▼ functional
    • New tool “pair_setup” functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
    • Tool “ichimoku_signal” rewrote its description, which is the text the model reads security
    • Tool “confluence_signal” rewrote its description, which is the text the model reads security
    • Tool “trade_setups” rewrote its description, which is the text the model reads security
    • Tool “price_levels” rewrote its description, which is the text the model reads security
    • Tool “market_scan” rewrote its description, which is the text the model reads security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://ichimoku-signal.fizzl.eu/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ichimoku-signal.fizzl.eu CN=WE1,O=Google Trust Services,C=US 28 Sept 2026 27 Dec 2026 ECDSA 256 ECDSA-SHA256 7f181003a2735a6613c82e2ac8fbefb5
SANs: ichimoku-signal.fizzl.eu
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ichimoku-signal.fizzl.eu. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
eu. DS published 35926 8 Verified
fizzl.eu. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
content-security-policy frame-ancestors 'none'; base-uri 'none'; object-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ichimoku-signal.fizzl.eu/mcp Verified 200
http (plaintext) http://ichimoku-signal.fizzl.eu/mcp HTTPS enforced 301 https://ichimoku-signal.fizzl.eu/mcp
MCP tools · 10 exposed · ~2,915 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
confluence_signal ~328

Paid ($0.15 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, 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.

NameTypeReqDescription
intervalstring–Candle interval, default 1h
pairstringyesCrypto 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…
NameTypeReqDescription
accepts––Only on an unpaid call: the x402 payment options
confidencestring|null–low, medium or high
indicators––Each indicator with its vote
intervalstring|null–Candle interval, e.g. 1h, 4h, 1d
news––Only when the news check is on: news from the last 72 hours that can break a technical signal (TypeSafe Jev). The signal itself never changes; treat high as a reason to wait.
pairstring|null–The pair, e.g. BTC-USDT
pricenumber|null–Last price
signal––Combined signal of six indicators
summarystring|null–e.g. 4 of 6 indicators bearish
timestampstring|null––

No examples provided.

feedback ~142

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.

NameTypeReqDescription
contactstring–Optional: how to reach you about it
endpointstring–Optional: the route or tool it is about, e.g. /v1/token
messagestringyesWhat happened or what you need
paymentobject–Optional: the payment it is about, when a paid call went wrong: its transaction (with the network) or a receipt id
typestring–bug, feature (something missing) or other
NameTypeReqDescription
idstringyesReport id, to refer to it later
notestring––
receivedbooleanyestrue: a person will read it
servicestring––
typestring––

No examples provided.

ichimoku_signal ~305

Paid ($0.01 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, 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.

NameTypeReqDescription
intervalstring–Candle interval, default 1h
pairstringyesCrypto 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…
NameTypeReqDescription
accepts––Only on an unpaid call: the x402 payment options
cloud_positionstring|null––
intervalstring|null–Candle interval, e.g. 1h, 4h, 1d
kijun_sennumber|null––
news––Only when the news check is on: news from the last 72 hours that can break a technical signal (TypeSafe Jev). The signal itself never changes; treat high as a reason to wait.
pairstring|null–The pair, e.g. BTC-USDT
pricenumber|null–Last price
signal––bullish, bearish or neutral (absent on the payment requirement)
tenkan_kijun_crossstring|null––
tenkan_sennumber|null––
timestampstring|null––

No examples provided.

ichimoku_trend ~243

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.

NameTypeReqDescription
pairstringyesCrypto 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…
NameTypeReqDescription
candle_timestring–Opening time (UTC) of the latest daily candle; it is still forming, so price is the latest trade
cloud_positionstring–above_cloud, below_cloud or in_cloud
exchangestring–Where the candles come from
intervalstringyes–
pairstringyes–
signalstringyesThe daily trend
tenkan_kijun_crossstring–bullish_cross, bearish_cross or none
timestampstring––

No examples provided.

market_scan ~201

Paid ($0.10 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, 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.

NameTypeReqDescription
intervalstring–Candle interval, default 1h
signalstring–Only return coins with this signal
NameTypeReqDescription
accepts––Only on an unpaid call: the x402 payment options
breadthstring|null–e.g. 71 of 148 coins bearish
coins––Every coin, strongest bullish first
coins_scannednumber|null––
intervalstring|null––
timestampstring|null––

No examples provided.

pair_lookup ~222

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.

NameTypeReqDescription
pairstringyesCrypto 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…
NameTypeReqDescription
exchangestring|null–Where the candles come from: Binance.US, Kraken, Gate, MEXC or XRPL DEX
intervalsarray–Intervals the signal tools accept for this pair
marketstring|null–The market used there, e.g. TAOUSD (another dollar quote can stand in for USDT)
pairstringyesThe pair as asked, e.g. TAO-USDT
sourcesstring–The exchanges that were searched
supportedbooleanyestrue: the signal tools work for this pair

No examples provided.

pair_setup ~348

Paid ($0.10 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, 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.

NameTypeReqDescription
pairstringyesCrypto 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…
NameTypeReqDescription
accepts––Only on an unpaid call: the x402 payment options
alignment––How many horizons point the same way, and on how many there is a setup
horizons––short (1h), medium (4h) and long (1d): bias, setup direction and the plan
pairstring|null––
timestampstring|null––

No examples provided.

price_levels ~288

Paid ($0.05 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, 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.

NameTypeReqDescription
intervalstring–Candle interval, default 1h
pairstringyesCrypto 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…
NameTypeReqDescription
accepts––Only on an unpaid call: the x402 payment options
biasstring|null–long, short or neutral, from the confluence signal
intervalstring|null–Candle interval, e.g. 1h, 4h, 1d
pairstring|null–The pair, e.g. BTC-USDT
pricenumber|null–Last price
resistances–––
supports–––
timestampstring|null––

No examples provided.

signal_alert ~505

Paid ($0.05 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, Algorand or Stellar, in RLUSD on the XRP Ledger, or in USD₮0 on X Layer), once for 7 days: instead of calling ichimoku_signal again and again, an alert whenever the Ichimoku Cloud signal of a crypto pair turns bullish, bearish or neutral on the timeframe you pick (15m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 3d, 1w; checked every 5 minutes). Delivery: "telegram": true gives a t.me link in the answer; your owner opens it once and presses Start, and every turn is then a Telegram message with the price, the plan in the new direction (entry, stop, two targets with risk/reward) and the nearest support and resistance; /levels in that chat shows the levels and targets at any time. And/or webhook_url (https): a POST signed with HMAC-SHA256 on every turn. "on" limits it to one direction (default any). Same as POST /watch. Keep the returned id and secret: status and cancel are free at GET/DELETE /watch/{id} with header X-Watch-Secret. Invalid input (pair, timeframe, webhook) is rejected before payment. Signals from price history, not trade advice.

NameTypeReqDescription
intervalstring–Timeframe of the signal to watch, default 1h
onstring–any (default): every turn; or only turns to this signal
pairstringyesCrypto 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…
telegramboolean–true: alerts in Telegram (the answer has the link to open and press Start)
webhook_urlstring–https URL that gets a signed POST on every turn
NameTypeReqDescription
accepts––Only on an unpaid call: the x402 payment options
current––The signal right now
expires_atstring|null––
idstring|null–The watch id, for GET/DELETE /watch/{id}
intervalstring|null–Timeframe of the watched signal
onstring|null–any, or the one signal that triggers an alert
pairstring|null––
secretstring|null–Shown once: header X-Watch-Secret for status and cancel, and the webhook signing key
telegram–––
webhook––Events, signature header and retries, when a webhook_url was given

No examples provided.

trade_setups ~333

Paid ($0.50 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, 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.

NameTypeReqDescription
directionstring–Only long or only short setups (default both)
intervalstring–Candle interval, default 4h
liquid_topinteger–Only the N most traded coins, e.g. 30 (default all)
min_rrnumber–Minimum risk/reward to target 1 (default 1.5)
topinteger–How many setups to return (default 10)
NameTypeReqDescription
accepts––Only on an unpaid call: the x402 payment options
coins_scannednumber|null––
intervalstring|null––
setups––Ranked setups with entry, stop and targets
setups_foundnumber|null––
timestampstring|null––

No examples provided.

Install

How do I install the Ichimoku Signal MCP server?

Ichimoku Signal is a hosted endpoint at https://ichimoku-signal.fizzl.eu/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · ichimoku-signal.fizzl.eu

# add to Claude Code
claude mcp add --transport http fizzl13-ichimoku-signal 'https://ichimoku-signal.fizzl.eu/mcp'
Common questions

What is the Ichimoku Signal MCP server?

Ichimoku Signal is an MCP server listed in the public MCP registry as io.github.Fizzl13/ichimoku-signal. Free Ichimoku trend; paid signals, levels, scan, setups and Telegram signal alerts via x402. This page covers its hosted endpoint (https://ichimoku-signal.fizzl.eu/mcp).

Is the Ichimoku Signal MCP server safe to use?

Ichimoku Signal scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Ichimoku Signal MCP server expose?

Ichimoku Signal exposes 10 tools: ichimoku_trend, pair_lookup, ichimoku_signal, confluence_signal, price_levels, and 5 more. Their descriptions and schemas cost roughly 2,915 tokens of context every time the server is loaded.

Does the Ichimoku Signal MCP server require authentication?

No. We connected to Ichimoku Signal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Ichimoku Signal MCP server still maintained?

Ichimoku Signal is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Ichimoku Signal MCP server?

VerifyMCP ran 12 checks on Ichimoku Signal, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Ichimoku Signal: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.