Remote MCP · Endpoint

Agent Weather MCP server

No. Agent Weather answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.agentweather.io/mcp

The last check completed an MCP handshake.

Registry name
io.agentweather/agent-weather
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
252 ms
Tools exposed
29 tools
Uptime, last 30 days
93.3% from 15 checks
Described by its publisher as
Pay per call, solves one question. Raw public readings on AI agents and x402.
Listing
From the official MCP registry (active).
Recent checks of Agent Weather
CheckedResultHandshake
2 hours agoHandshake completed252 ms
1 day agoHandshake completed276 ms
3 days agoHandshake completed266 ms
3 days agoHandshake completed244 ms
4 days agoHandshake completed226 ms
5 days agoHandshake completed273 ms
7 days agoHandshake completed240 ms
10 days agoHandshake completed308 ms
12 days agoHandshake completed251 ms
15 days agoHandshake completed279 ms
17 days agoHandshake completed244 ms
19 days agoHandshake completed273 ms
21 days agoHandshake completed246 ms
23 days agoHandshake completed279 ms
25 days agoFailed - the server returned an HTTP error—

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 Agent Weather and makes no claim about it beyond what these checks measured.