Remote MCP · Endpoint

Vertical Weather MCP server

No. Vertical Weather answered an MCP handshake 48 minutes ago.

UpLast checked 48 minutes ago

Server URL

https://api.verticalweather.com/mcp

The last check completed an MCP handshake.

Registry name
com.verticalweather/vertical-weather
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
45 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Wind, temperature, pressure, humidity and air density at chosen heights, from NOAA GFS.
Listing
From the official MCP registry (active).
Recent checks of Vertical Weather
CheckedResultHandshake
48 minutes agoHandshake completed45 ms
10 days agoHandshake completed30 ms
10 days agoHandshake completed44 ms
11 days agoHandshake completed41 ms
12 days agoHandshake completed5.18 s
14 days agoHandshake completed5.46 s
14 days agoHandshake completed52 ms
15 days agoHandshake completed41 ms
17 days agoHandshake completed40 ms
19 days agoHandshake completed34 ms
21 days agoHandshake completed31 ms
24 days agoHandshake completed37 ms
26 days agoHandshake completed47 ms
28 days agoHandshake completed345 ms

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

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