Ichimoku Signal
REMOTE · ICHIMOKU-SIGNAL.ONRENDER.COM · SCANNED SEP 27
Free Ichimoku trend; paid confluence, levels, market scan and liquidity-ranked setups via x402.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
remote · ichimoku-signal.onrender.com
claude mcp add --transport http fizzl13-ichimoku-signal 'https://ichimoku-signal.onrender.com/mcp'
{
"mcpServers": {
"fizzl13-ichimoku-signal": {
"url": "https://ichimoku-signal.onrender.com/mcp"
}
}
} {
"servers": {
"fizzl13-ichimoku-signal": {
"type": "http",
"url": "https://ichimoku-signal.onrender.com/mcp"
}
}
} [mcp_servers.fizzl13-ichimoku-signal] url = "https://ichimoku-signal.onrender.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fizzl13-ichimoku-signal": {
"type": "remote",
"url": "https://ichimoku-signal.onrender.com/mcp",
"enabled": true
}
}
} openclaw mcp add fizzl13-ichimoku-signal --url 'https://ichimoku-signal.onrender.com/mcp' --transport streamable-http
mcp_servers:
fizzl13-ichimoku-signal:
url: "https://ichimoku-signal.onrender.com/mcp" {
"McpServers": {
"fizzl13-ichimoku-signal": {
"Transport": "http",
"Url": "https://ichimoku-signal.onrender.com/mcp"
}
}
} assistant mcp add fizzl13-ichimoku-signal -t streamable-http -u 'https://ichimoku-signal.onrender.com/mcp'
{
"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.
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.
- 27 Sept 26 +2
- 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 security
- Schema quality: 831 → 1096 ▼ functional
- Schema quality: 831 → 1057 ▼ functional
- Schema quality: excellent → good functional
- Server version: 1.3.0 → 1.5.0 functional
- New tool “trade_setups” functional
- “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) cosmetic
- 26 Sept 26 +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.
- 25 Sept 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
- 24 Sept 26 −1
- Tool “ichimoku_trend” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.1.0 → 1.2.0 functional
- New tool “confluence_signal” functional
- New tool “price_levels” functional
- “ichimoku_signal” reworded the description of “pair” cosmetic
- “ichimoku_trend” reworded the description of “pair” cosmetic
- 23 Sept 26 65
First indexed and scored.
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 27 Sept 2026 · Probed https://ichimoku-signal.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| 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.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | 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.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://ichimoku-signal.onrender.com/mcp | HTTPS enforced | 301 | https://ichimoku-signal.onrender.com/mcp |
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 →
confluence_signal Confluence signal: 6 indicators ($0.15 via x402) ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| interval | string | – | Candle interval, default 1h |
| pair | string | yes | Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins) |
No output schema declared.
No examples provided.
ichimoku_signal Ichimoku Cloud signal ($0.02 via x402) ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| interval | string | – | Candle interval, default 1h |
| pair | string | yes | Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins) |
No output schema declared.
No examples provided.
ichimoku_trend Ichimoku daily trend (free) ~182
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pair | string | yes | Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins) |
No output schema declared.
No examples provided.
market_scan Market scan: every top-200 coin ($0.10 via x402) ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| interval | string | – | Candle interval, default 1h |
| signal | string | – | Only return coins with this signal |
No output schema declared.
No examples provided.
price_levels Price levels and a long/short plan ($0.05 via x402) ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| interval | string | – | Candle interval, default 1h |
| pair | string | yes | Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins) |
No output schema declared.
No examples provided.
trade_setups Trade setups: every top-200 coin, ranked ($0.50 via x402) ~254
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
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.