Remote MCP · Endpoint

Skinow MCP server

No. Skinow answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://skinow.co/mcp

The last check completed an MCP handshake.

Registry name
eu.skimetric/skimetric
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
368 ms
Tools exposed
27 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Skinow, formerly Skimetric: snow forecasts, lift status, season history and AI ski trip planning
Listing
From the official MCP registry (active).
Recent checks of Skinow
CheckedResultHandshake
2 days agoHandshake completed368 ms
3 days agoHandshake completed440 ms
3 days agoHandshake completed464 ms
5 days agoHandshake completed365 ms
6 days agoHandshake completed363 ms
7 days agoHandshake completed391 ms
8 days agoHandshake completed375 ms
9 days agoHandshake completed398 ms
11 days agoHandshake completed462 ms
13 days agoHandshake completed386 ms
16 days agoHandshake completed476 ms
18 days agoHandshake completed162 ms
21 days agoHandshake completed358 ms
22 days agoHandshake completed511 ms
25 days agoHandshake completed475 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 Skinow and makes no claim about it beyond what these checks measured.