Ichimoku Signal
io-github-fizzl13-ichimoku-signal declares 8 capabilities across 8 tools, with 1 critical issue.
Issues
8 of 8 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
8 of 8 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
8 of 8 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
1 tool can modify data and declares no limit.
7 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
ichimoku_trend | read |
declared |
pair_lookup | read |
declared |
ichimoku_signal | read |
declared |
confluence_signal | read |
declared |
price_levels | read |
declared |
market_scan | read |
declared |
trade_setups | read |
declared |
feedback | write |
assumed |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-16 | 18 | tools/list on https://ichimoku-signal.fizzl.eu/mcp, published in the official MCP registry as io.github.Fizzl13/ichimoku-signal 1.5.1 |
| 2026-10-11 | 16 | tools/list on https://ichimoku-signal.fizzl.eu/mcp, published in the official MCP registry as io.github.Fizzl13/ichimoku-signal 1.5.1 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.