Home / MCP registry index / io.github.Fizzl13/ichimoku-signal
Ichimoku Signal
io.github.Fizzl13/ichimoku-signal in the official MCP registry.
Endpoint https://ichimoku-signal.fizzl.eu/mcp. Source: github.com/Fizzl13/ichimoku-signal.
The registry describes it as: Free Ichimoku trend; paid confluence, levels, market scan and liquidity-ranked setups via x402.
We read its 8 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
ichimoku_trend pair_lookup ichimoku_signal confluence_signal price_levels market_scan trade_setups feedback
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-fizzl13-ichimoku-signal)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
Jira and Confluence MCP servers · Crypto and Web3 MCP servers
| Confluence io.github.pipeworx-io/confluence | 47 tools, nothing matched 2026-10-22 |
| ai.waystation/jira ai.waystation/jira | not reachable 2026-10-22 |
| Atlassian Rovo MCP Server com.atlassian/atlassian-mcp-server | not read yet |
| Jira io.github.pipeworx-io/jira | not read yet |
| Statuspage io.github.pipeworx-io/statuspage | not read yet |
| Jira Key Shape io.github.sadri-dridi/jira-key-shape | not read yet |