Remote MCP · Endpoint

LNX QR codes MCP server

No. LNX QR codes answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://qr.lnx.net/mcp

The last check completed an MCP handshake.

Registry name
net.lnx/qr
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
340 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Styled, print-ready QR codes for links, text, email or phone, with frames and custom colors.
Listing
From the official MCP registry (active).
Recent checks of LNX QR codes
CheckedResultHandshake
2 hours agoHandshake completed340 ms
2 days agoHandshake completed370 ms
4 days agoHandshake completed348 ms
7 days agoHandshake completed340 ms
9 days agoHandshake completed340 ms
11 days agoHandshake completed336 ms
13 days agoHandshake completed342 ms
15 days agoHandshake completed341 ms
16 days agoHandshake completed337 ms
18 days agoHandshake completed349 ms
19 days agoHandshake completed360 ms
20 days agoHandshake completed336 ms
23 days agoHandshake completed337 ms
24 days agoHandshake completed336 ms

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

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 LNX QR codes and makes no claim about it beyond what these checks measured.