Remote MCP · Endpoint

QRvote MCP server

No. QRvote answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes 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
441 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
QR-code contests, surveys, quizzes, hunts, Q&As and idea boards: read results, manage your own.
Listing
From the official MCP registry (active).
Recent checks of QRvote
CheckedResultHandshake
20 minutes agoHandshake completed441 ms
8 days agoHandshake completed117 ms
9 days agoHandshake completed86 ms
11 days agoHandshake completed77 ms
12 days agoHandshake completed462 ms
13 days agoHandshake completed101 ms
14 days agoHandshake completed123 ms
14 days agoHandshake completed88 ms
16 days agoHandshake completed59 ms
19 days agoHandshake completed203 ms
21 days agoHandshake completed77 ms
24 days agoHandshake completed351 ms
26 days agoHandshake completed174 ms
28 days agoHandshake completed107 ms

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

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.