Remote MCP · Endpoint

QR Wall MCP server

No. QR Wall answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://qrwall.live/mcp

The last check completed an MCP handshake.

Registry name
live.qrwall/qrwall
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
156 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Read-only facts, pricing, use cases and demo links for QR Wall, a live event photo wall.
Website
https://qrwall.live/
Listing
From the official MCP registry (active).
Recent checks of QR Wall
CheckedResultHandshake
19 minutes agoHandshake completed156 ms
9 days agoHandshake completed132 ms
9 days agoHandshake completed111 ms
11 days agoHandshake completed118 ms
12 days agoHandshake completed159 ms
13 days agoHandshake completed132 ms
14 days agoHandshake completed140 ms
15 days agoHandshake completed145 ms
16 days agoHandshake completed108 ms
19 days agoHandshake completed171 ms
21 days agoHandshake completed160 ms
24 days agoHandshake completed1.56 s

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with QR Wall and makes no claim about it beyond what these checks measured.