Remote MCP · Endpoint

QRtracer MCP server

No. QRtracer answered an MCP handshake 26 minutes ago.

UpLast checked 26 minutes ago

Server URL

https://qrtracer.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.danieldedaniel/qrtracer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
900 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Create and manage dynamic QR codes, export QR images, compare scan analytics and check QR links.
Listing
From the official MCP registry (active).
Recent checks of QRtracer
CheckedResultHandshake
26 minutes agoHandshake completed900 ms
10 days agoHandshake completed1.03 s
11 days agoHandshake completed1.00 s
12 days agoHandshake completed2.39 s
13 days agoHandshake completed1.18 s
14 days agoHandshake completed945 ms
15 days agoHandshake completed1.07 s
16 days agoHandshake completed793 ms
17 days agoHandshake completed771 ms
19 days agoHandshake completed1.17 s
22 days agoHandshake completed729 ms
24 days agoHandshake completed1.82 s
26 days agoHandshake completed744 ms
29 days agoHandshake completed837 ms

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

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