Remote MCP · Endpoint

Weather of Record MCP server

No. Weather of Record answered an MCP handshake 54 minutes ago.

UpLast checked 54 minutes ago

Server URL

https://weatherofrecord.com/mcp

The last check completed an MCP handshake.

Registry name
com.weatherofrecord/weather-of-record
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
49 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Published weather records for a U.S. address and date, with provenance, and current NWS forecasts.
Listing
From the official MCP registry (active).
Recent checks of Weather of Record
CheckedResultHandshake
54 minutes agoHandshake completed49 ms
3 days agoHandshake completed181 ms
12 days agoHandshake completed51 ms
13 days agoHandshake completed58 ms
15 days agoHandshake completed57 ms
15 days agoHandshake completed61 ms
17 days agoHandshake completed128 ms
18 days agoHandshake completed55 ms
18 days agoHandshake completed67 ms
20 days agoHandshake completed46 ms
22 days agoHandshake completed46 ms
25 days agoHandshake completed40 ms
27 days agoHandshake completed64 ms
29 days agoHandshake completed45 ms

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

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