Remote MCP · Endpoint
Weather MCP server
No. Weather answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://agent-evidence-api.thx93.workers.dev/weather/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.Thx93/weather
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 663 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 57.9% from 19 checks
- Described by its publisher as
- US weather for AI agents: active NWS alerts by state, 5-period forecasts by lat/lon. Paid per call.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 663 ms |
| 1 day ago | Handshake completed | 700 ms |
| 2 days ago | Handshake completed | 402 ms |
| 3 days ago | Handshake completed | 507 ms |
| 4 days ago | Handshake completed | 322 ms |
| 5 days ago | Handshake completed | 336 ms |
| 6 days ago | Handshake completed | 412 ms |
| 8 days ago | Handshake completed | 588 ms |
| 11 days ago | Handshake completed | 401 ms |
| 13 days ago | Handshake completed | 371 ms |
| 15 days ago | Handshake completed | 449 ms |
| 18 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 22 days ago | Failed - the server returned an HTTP error | — |
| 24 days ago | Failed - the server returned an HTTP error | — |
| 26 days ago | Failed - the server returned an HTTP error | — |
| 27 days ago | Failed - the server returned an HTTP error | — |
| 29 days ago | Failed - the server returned an HTTP error | — |
| 29 days ago | Failed - the server returned an HTTP error | — |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 Weather and makes no claim about it beyond what these checks measured.