Remote MCP · Endpoint

Ladepunktdaten MCP server

No. Ladepunktdaten answered an MCP handshake 38 minutes ago.

UpLast checked 38 minutes ago

Server URL

https://www.ladepunktdaten.de/mcp

The last check completed an MCP handshake.

Registry name
de.ladepunktdaten/ladesaeulen
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
336 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Ladesäulenregister der Bundesnetzagentur: Suche, Regionalstatistik, Änderungen, Export je Region.
Listing
From the official MCP registry (active).
Recent checks of Ladepunktdaten
CheckedResultHandshake
38 minutes agoHandshake completed336 ms
4 days agoHandshake completed304 ms
7 days agoHandshake completed298 ms
16 days agoHandshake completed288 ms
16 days agoHandshake completed288 ms
18 days agoHandshake completed287 ms
19 days agoHandshake completed298 ms
20 days agoHandshake completed291 ms
21 days agoHandshake completed309 ms
22 days agoHandshake completed290 ms
23 days agoHandshake completed335 ms
26 days agoHandshake completed297 ms
29 days agoHandshake completed291 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 Ladepunktdaten and makes no claim about it beyond what these checks measured.