Remote MCP · Endpoint

qrvote MCP server

No. qrvote answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.qrvote.org/mcp

The last check completed an MCP handshake.

Registry name
org.qrvote/qrvote
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
77 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
QR-code contests, surveys, quizzes and scavenger hunts: read results, manage your own.
Listing
From the official MCP registry (active).
Recent checks of qrvote
CheckedResultHandshake
1 hour agoHandshake completed77 ms
2 days agoHandshake completed351 ms
4 days agoHandshake completed174 ms
6 days agoHandshake completed107 ms
8 days agoHandshake completed87 ms
10 days agoHandshake completed114 ms
12 days agoHandshake completed87 ms
14 days agoHandshake completed143 ms
15 days agoHandshake completed95 ms
16 days agoHandshake completed333 ms
18 days agoHandshake completed110 ms
20 days agoHandshake completed72 ms
22 days agoHandshake completed115 ms
24 days agoHandshake completed88 ms
25 days agoHandshake completed154 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 qrvote and makes no claim about it beyond what these checks measured.