Remote MCP · Endpoint

Weather That Doesn't Suck MCP server

No. Weather That Doesn't Suck answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://weatherthatdoesntsuck.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.weatherthatdoesntsuck/weather
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
73 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Weather decisions for outdoor plans: should I go, when, what to wear, what you will meet en route.
Listing
From the official MCP registry (active).
Recent checks of Weather That Doesn't Suck
CheckedResultHandshake
1 hour agoHandshake completed73 ms
2 days agoHandshake completed36 ms
5 days agoHandshake completed145 ms
7 days agoHandshake completed50 ms
9 days agoHandshake completed51 ms
11 days agoHandshake completed39 ms
13 days agoHandshake completed41 ms
15 days agoHandshake completed41 ms
17 days agoHandshake completed37 ms
19 days agoHandshake completed38 ms
20 days agoHandshake completed45 ms
21 days agoHandshake completed40 ms
23 days agoHandshake completed39 ms

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

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 Weather That Doesn't Suck and makes no claim about it beyond what these checks measured.