# Ichimoku Signal (remote · ichimoku-signal.onrender.com)

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

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `ichimoku-signal.onrender.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/fizzl13-ichimoku-signal/ichimoku-signal.md), [page](https://verifymcp.io/servers/fizzl13-ichimoku-signal/ichimoku-signal)

## Channel facts

- Endpoint: `https://ichimoku-signal.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-27.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1096 tokens (~182/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Ichimoku Signal MCP server?

Ichimoku Signal is a hosted endpoint at https://ichimoku-signal.onrender.com/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.

### Claude

```bash
claude mcp add --transport http fizzl13-ichimoku-signal 'https://ichimoku-signal.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "fizzl13-ichimoku-signal": {
      "url": "https://ichimoku-signal.onrender.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fizzl13-ichimoku-signal": {
      "type": "http",
      "url": "https://ichimoku-signal.onrender.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fizzl13-ichimoku-signal]
url = "https://ichimoku-signal.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fizzl13-ichimoku-signal": {
      "type": "remote",
      "url": "https://ichimoku-signal.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fizzl13-ichimoku-signal --url 'https://ichimoku-signal.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fizzl13-ichimoku-signal:
    url: "https://ichimoku-signal.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fizzl13-ichimoku-signal": {
      "Transport": "http",
      "Url": "https://ichimoku-signal.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fizzl13-ichimoku-signal -t streamable-http -u 'https://ichimoku-signal.onrender.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fizzl13-ichimoku-signal": {
      "type": "http",
      "url": "https://ichimoku-signal.onrender.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-27 (score 67, +2)

- [security improvement] HSTS header: fail → pass
- [security] Tool “trade_setups” 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 “ichimoku_trend” rewrote its description, which is the text the model reads
- [security] Tool “market_scan” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 831 → 1096
- [functional regression] Schema quality: 831 → 1057
- [functional] Schema quality: excellent → good
- [functional] Server version: 1.3.0 → 1.5.0
- [functional] New tool “trade_setups”
- [cosmetic] “trade_setups” added an optional parameter “liquid_top”
- [cosmetic] Tool “confluence_signal” changed its title: Confluence signal: 6 indicators ($0.10 via x402) → Confluence signal: 6 indicators ($0.15 via x402)
- [cosmetic] Tool “market_scan” changed its title: Market scan: every top-200 coin ($0.25 via x402) → Market scan: every top-200 coin ($0.10 via x402)

### 2026-09-26 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 64, −1)

- [security] Tool “ichimoku_trend” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.1.0 → 1.2.0
- [functional] New tool “confluence_signal”
- [functional] New tool “price_levels”
- [cosmetic] “ichimoku_signal” reworded the description of “pair”
- [cosmetic] “ichimoku_trend” reworded the description of “pair”

### 2026-09-23 (score 65)

First indexed and scored.

## MCP tools (6)

### `ichimoku_trend` (~182 tokens)

Ichimoku daily trend (free)

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.

Input parameters:

- `pair` (string, required): Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins)

### `ichimoku_signal` (~159 tokens)

Ichimoku Cloud signal ($0.02 via x402)

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.

Input parameters:

- `interval` (string): Candle interval, default 1h
- `pair` (string, required): Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins)

### `confluence_signal` (~188 tokens)

Confluence signal: 6 indicators ($0.15 via x402)

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.

Input parameters:

- `interval` (string): Candle interval, default 1h
- `pair` (string, required): Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins)

### `price_levels` (~178 tokens)

Price levels and a long/short plan ($0.05 via x402)

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.

Input parameters:

- `interval` (string): Candle interval, default 1h
- `pair` (string, required): Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins)

### `market_scan` (~135 tokens)

Market scan: every top-200 coin ($0.10 via x402)

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.

Input parameters:

- `interval` (string): Candle interval, default 1h
- `signal` (string): Only return coins with this signal

### `trade_setups` (~254 tokens)

Trade setups: every top-200 coin, ranked ($0.50 via x402)

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.

Input parameters:

- `direction` (string): Only long or only short setups (default both)
- `interval` (string): Candle interval, default 4h
- `liquid_top` (integer): Only the N most traded coins, e.g. 30 (default all)
- `min_rr` (number): Minimum risk/reward to target 1 (default 1.5)
- `top` (integer): How many setups to return (default 10)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fizzl13-ichimoku-signal/ichimoku-signal#diagnostics

## Score history

- 2026-09-27: 67
- 2026-09-26: 65
- 2026-09-25: 64
- 2026-09-24: 64
- 2026-09-23: 65

## 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 confluence, levels, market scan and liquidity-ranked setups via x402. This page covers its hosted endpoint (https://ichimoku-signal.onrender.com/mcp).

### Is the Ichimoku Signal MCP server safe to use?

Ichimoku Signal scores 67 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 6 tools: ichimoku_trend, ichimoku_signal, confluence_signal, price_levels, market_scan, trade_setups. Their descriptions and schemas cost roughly 1,096 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 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://ichimoku-signal.onrender.com/mcp
- Repository: https://github.com/Fizzl13/ichimoku-signal
- Website: https://ichimoku-signal.onrender.com/
- Changelog RSS feed: https://verifymcp.io/servers/fizzl13-ichimoku-signal/ichimoku-signal.xml
- Changelog JSON feed: https://verifymcp.io/servers/fizzl13-ichimoku-signal/ichimoku-signal.json
- HTML version of this page: https://verifymcp.io/servers/fizzl13-ichimoku-signal/ichimoku-signal