Remote MCP · Endpoint

Ichimoku Signal MCP server

No. Ichimoku Signal answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ichimoku-signal.fizzl.eu/mcp

The last check completed an MCP handshake.

Registry name
io.github.Fizzl13/ichimoku-signal
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
273 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Free Ichimoku trend; paid confluence, levels, market scan and liquidity-ranked setups via x402.
Listing
From the official MCP registry (active).
Recent checks of Ichimoku Signal
CheckedResultHandshake
1 hour agoHandshake completed273 ms
2 days agoHandshake completed156 ms
4 days agoHandshake completed142 ms
6 days agoHandshake completed267 ms
8 days agoHandshake completed179 ms
10 days agoHandshake completed141 ms
12 days agoHandshake completed259 ms
14 days agoHandshake completed143 ms
15 days agoHandshake completed309 ms
16 days agoHandshake completed279 ms
17 days agoHandshake completed186 ms
20 days agoHandshake completed1.01 s
22 days agoHandshake completed230 ms
23 days agoHandshake completed285 ms
25 days agoHandshake completed365 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Ichimoku Signal and makes no claim about it beyond what these checks measured.