Remote MCP · Endpoint

Dwd Climate MCP server

No. Dwd Climate answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gateway.pipeworx.io/dwd-climate/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/dwd-climate
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
79 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
DWD Climate Data Center — daily station observations for Germany.
Listing
From the official MCP registry (active).
Recent checks of Dwd Climate
CheckedResultHandshake
2 hours agoHandshake completed79 ms
1 day agoHandshake completed75 ms
2 days agoHandshake completed117 ms
3 days agoHandshake completed106 ms
4 days agoHandshake completed91 ms
5 days agoHandshake completed85 ms
7 days agoHandshake completed202 ms
9 days agoHandshake completed181 ms
11 days agoHandshake completed67 ms
14 days agoHandshake completed1.52 s
16 days agoHandshake completed57 ms
18 days agoHandshake completed133 ms
20 days agoHandshake completed135 ms
22 days agoHandshake completed60 ms
24 days agoHandshake completed976 ms

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