Remote MCP · Endpoint

ElectionsMCP MCP server

No. ElectionsMCP answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://www.electionsmcp.com/mcp

The last check completed an MCP handshake.

Registry name
com.electionsmcp/electionsmcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
261 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Model and map any 2028 U.S. race down to the precinct: scenarios, swing, turnout, and roll-ups.
Listing
From the official MCP registry (active).
Recent checks of ElectionsMCP
CheckedResultHandshake
1 day agoHandshake completed261 ms
3 days agoHandshake completed270 ms
5 days agoHandshake completed250 ms
7 days agoHandshake completed250 ms
9 days agoHandshake completed226 ms
10 days agoHandshake completed237 ms
12 days agoHandshake completed238 ms
13 days agoHandshake completed96 ms
15 days agoHandshake completed230 ms
17 days agoHandshake completed239 ms
19 days agoHandshake completed227 ms
20 days agoHandshake completed241 ms
21 days agoHandshake completed237 ms
22 days agoHandshake completed243 ms

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

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