Remote MCP · Endpoint

GERDA German Election Data MCP server

No. GERDA German Election Data answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://mcp.german-elections.com/mcp

The last check completed an MCP handshake.

Registry name
com.german-elections/gerda
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
210 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only German federal election results for municipalities, with harmonized geography.
Listing
From the official MCP registry (active).
Recent checks of GERDA German Election Data
CheckedResultHandshake
43 minutes agoHandshake completed210 ms
8 days agoHandshake completed206 ms
9 days agoHandshake completed202 ms
11 days agoHandshake completed202 ms
12 days agoHandshake completed211 ms
13 days agoHandshake completed210 ms
14 days agoHandshake completed219 ms
14 days agoHandshake completed206 ms
16 days agoHandshake completed226 ms
19 days agoHandshake completed218 ms
21 days agoHandshake completed202 ms
24 days agoHandshake completed334 ms
26 days agoHandshake completed204 ms
28 days agoHandshake completed207 ms

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

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 GERDA German Election Data and makes no claim about it beyond what these checks measured.