Remote MCP · Endpoint

Election Index MCP server

No. Election Index answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://electionindex.org/mcp

The last check completed an MCP handshake.

Registry name
org.electionindex/elections
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
310 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Neutral, sourced election calendar: polling days, when provisional and final results are due.
Listing
From the official MCP registry (active).
Recent checks of Election Index
CheckedResultHandshake
1 hour agoHandshake completed310 ms
2 days agoHandshake completed303 ms
4 days agoHandshake completed333 ms
6 days agoHandshake completed200 ms
8 days agoHandshake completed169 ms
10 days agoHandshake completed186 ms
11 days agoHandshake completed277 ms
13 days agoHandshake completed204 ms
14 days agoHandshake completed334 ms
15 days agoHandshake completed127 ms
18 days agoHandshake completed131 ms
19 days agoHandshake completed60 ms
21 days agoHandshake completed256 ms
22 days agoHandshake completed219 ms
23 days agoHandshake completed225 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 Election Index and makes no claim about it beyond what these checks measured.