Remote MCP · Endpoint

EP Votes MCP server

No. EP Votes answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://epvotes.com/mcp

The last check completed an MCP handshake.

Registry name
com.epvotes/epvotes
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
62 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
European Parliament roll-call votes, MEP records and dossiers from official records.
Listing
From the official MCP registry (active).
Recent checks of EP Votes
CheckedResultHandshake
44 minutes agoHandshake completed62 ms
3 days agoHandshake completed562 ms
12 days agoHandshake completed91 ms
13 days agoHandshake completed515 ms
14 days agoHandshake completed1.08 s
15 days agoHandshake completed942 ms
16 days agoHandshake completed57 ms
17 days agoHandshake completed1.62 s
18 days agoHandshake completed885 ms
19 days agoHandshake completed87 ms
22 days agoHandshake completed675 ms
25 days agoHandshake completed48 ms
27 days agoHandshake completed157 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 EP Votes and makes no claim about it beyond what these checks measured.