Remote MCP · Endpoint

io.snowsignals/snowsignals MCP server

No. io.snowsignals/snowsignals answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://snowsignals.io/mcp

The last check completed an MCP handshake.

Registry name
io.snowsignals/snowsignals
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
510 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Market-phase classifications over a metered API — phase events per currency and timeframe.
Listing
From the official MCP registry (active).
Recent checks of io.snowsignals/snowsignals
CheckedResultHandshake
1 hour agoHandshake completed510 ms
9 days agoHandshake completed327 ms
10 days agoHandshake completed413 ms
11 days agoHandshake completed327 ms
12 days agoHandshake completed310 ms
14 days agoHandshake completed326 ms
14 days agoHandshake completed326 ms
15 days agoHandshake completed440 ms
17 days agoHandshake completed352 ms
19 days agoHandshake completed449 ms
21 days agoHandshake completed388 ms
24 days agoHandshake completed604 ms
26 days agoHandshake completed379 ms
28 days agoHandshake completed426 ms

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

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 io.snowsignals/snowsignals and makes no claim about it beyond what these checks measured.