Remote MCP · Endpoint

vote.direct MCP server

No. vote.direct answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://vote.direct/api/mcp

The last check completed an MCP handshake.

Registry name
direct.vote/vote-direct
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
398 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Run a real election or board vote: price it, check state HOA rules, draft the ballot and voter list.
Listing
From the official MCP registry (active).
Recent checks of vote.direct
CheckedResultHandshake
1 hour agoHandshake completed398 ms
2 days agoHandshake completed269 ms
4 days agoHandshake completed273 ms
6 days agoHandshake completed175 ms
8 days agoHandshake completed195 ms
10 days agoHandshake completed184 ms
12 days agoHandshake completed1.16 s
14 days agoHandshake completed177 ms
16 days agoHandshake completed214 ms
17 days agoHandshake completed234 ms
18 days agoHandshake completed164 ms
21 days agoHandshake completed177 ms
22 days agoHandshake completed170 ms
24 days agoHandshake completed282 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 vote.direct and makes no claim about it beyond what these checks measured.