Remote MCP · Endpoint

qrcode.io QR codes MCP server

No. qrcode.io QR codes answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://agent.qrcode.io/mcp

The last check completed an MCP handshake.

Registry name
io.qrcode/qr-codes
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
276 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Free static QR codes (PNG or SVG) that never expire, for URLs, WiFi, vCards and text. No account.
Listing
From the official MCP registry (active).
Recent checks of qrcode.io QR codes
CheckedResultHandshake
17 minutes agoHandshake completed276 ms
9 days agoHandshake completed388 ms
9 days agoHandshake completed269 ms
11 days agoHandshake completed217 ms
12 days agoHandshake completed315 ms
13 days agoHandshake completed186 ms
14 days agoHandshake completed207 ms
14 days agoHandshake completed197 ms
16 days agoHandshake completed291 ms
19 days agoHandshake completed152 ms
21 days agoHandshake completed141 ms
24 days agoHandshake completed517 ms
26 days agoHandshake completed158 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 qrcode.io QR codes and makes no claim about it beyond what these checks measured.