Ichimoku Signal MCP server
io.github.Fizzl13/ichimoku-signalFizzl13streamable-httpv1.6.0Scanned
Free Ichimoku trend; paid signals, levels, scan, setups and Telegram signal alerts via x402.
10 tools: 9 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 9
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
9 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Ichimoku Signal MCP server can do
The Ichimoku Signal MCP server is published by the GitHub account Fizzl13. It has 10 tools. It can create or change data (9 tools: ichimoku_trend, ichimoku_signal, confluence_signal, price_levels and 5 more), but cannot delete data. 1 tool only reads.
9 tools bring in text other people can write (ichimoku_trend, pair_lookup, ichimoku_signal and 6 more); 2 tools can send data out of your system (signal_alert and feedback).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 8, 2026, version 1.6.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Changes things 9Claude Code: ask
confluence_signalPaid ($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 cr…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
feedbackReport a bug, a missing feature or anything else about this service, in a structured way.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- openWorldHint: false
ichimoku_signalPaid ($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…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
ichimoku_trendFree: 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…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
market_scanPaid ($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 sign…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
pair_setupPaid ($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…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
price_levelsPaid ($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 cryp…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
signal_alertPaid ($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: instea…Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.webhook_url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: false
- openWorldHint: true
trade_setupsPaid ($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…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
Only reads 1Show 1 read-only tool
pair_lookupFree: 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…Reads text others writeNo findings
Why it is in this group
- The name "pair_lookup" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write9
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:58 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 9
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 9 tools that change things (9 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://ichimoku-signal.fizzl.eu/mcp: tools/list returned 10 tools to an anonymous client, including ichimoku_trend (write), ichimoku_signal (write), confluence_signal (write), price_levels (write), pair_setup (write) and 4 more
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 8 to 9
- Nov 6, 2026
- Tools that change things, listed without credentials: 7 to 8
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 9.View diff
- Tools that change things, listed without credentials: 8 to 9
Tools1 added, 6 changed.+1 added~6 changedView diff
- Added:signal_alertChanges things
- Changed:confluence_signalChanges thingsdescription
- Changed:ichimoku_signalChanges thingsdescription
- Changed:market_scanChanges thingsdescription
- Changed:pair_setupChanges thingsdescription
- Changed:price_levelsChanges thingsdescription
- Changed:trade_setupsChanges thingsdescription
PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 8.View diff
- Tools that change things, listed without credentials: 7 to 8
Tools1 added, 8 changed.+1 added~8 changedView diff
- Added:pair_setupChanges things
- Changed:confluence_signalChanges thingsdescriptioninputSchema
- Changed:feedbackChanges thingsinputSchema
- Changed:ichimoku_signalChanges thingsdescriptioninputSchema
- Changed:ichimoku_trendChanges thingsinputSchema
- Changed:market_scanChanges thingsdescriptioninputSchema
- Changed:pair_lookupOnly readsinputSchema
- Changed:price_levelsChanges thingsdescriptioninputSchema
- Changed:trade_setupsChanges thingsdescriptioninputSchema
Install
Pinned to version 1.6.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ichimoku-signal https://ichimoku-signal.fizzl.eu/mcpclaude mcp add --transport http ichimoku-signal https://ichimoku-signal.fizzl.eu/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ichimoku-signal__pair_lookup"
],
"ask": [
"mcp__ichimoku-signal__ichimoku_trend",
"mcp__ichimoku-signal__ichimoku_signal",
"mcp__ichimoku-signal__confluence_signal",
"mcp__ichimoku-signal__price_levels",
"mcp__ichimoku-signal__pair_setup",
"mcp__ichimoku-signal__market_scan",
"mcp__ichimoku-signal__trade_setups",
"mcp__ichimoku-signal__signal_alert",
"mcp__ichimoku-signal__feedback"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ichimoku-signal. Review it before you use it.
Capability tags behind 10 rules
- mcp__ichimoku-signal__ichimoku_trend untrusted-input
- mcp__ichimoku-signal__pair_lookup untrusted-input
- mcp__ichimoku-signal__ichimoku_signal untrusted-input
- mcp__ichimoku-signal__confluence_signal untrusted-input
- mcp__ichimoku-signal__price_levels untrusted-input
- mcp__ichimoku-signal__pair_setup untrusted-input
- mcp__ichimoku-signal__market_scan untrusted-input
- mcp__ichimoku-signal__trade_setups untrusted-input
- mcp__ichimoku-signal__signal_alert untrusted-input, outbound
- mcp__ichimoku-signal__feedback outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Fizzl13/ichimoku-signal/verify?hash=eb71b7f46157dfb8e3c0e3d36c61b5576aa07e67c84022fa732d0d6e5b6914e2" | jq -e '.changed == false'Pinned hash eb71b7f46157, from Nov 8, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Fizzl13/ichimoku-signal/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Fizzl13/ichimoku-signal)Source: MCP Registry · repository. Synced Nov 8, 2026, 13:17 UTC.
Ichimoku Signal MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Ichimoku Signal MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 9 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Ichimoku Signal MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Ichimoku Signal MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Ichimoku Signal MCP server have?
- 10 tools: 9 write, 1 read. ichimoku_trend, ichimoku_signal, confluence_signal, price_levels, pair_setup, market_scan, trade_setups, signal_alert and 2 more.
Does the Ichimoku Signal MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Ichimoku Signal MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): signal_alert and feedback.
Has the Ichimoku Signal MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.