Remote MCP · Endpoint

io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13 MCP server

No. io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13 answered an MCP handshake 54 minutes ago.

UpLast checked 54 minutes ago

Server URL

https://mcp.zovo.one/mcp/barcode

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.44 s
Tools exposed
10 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
QR codes and barcodes offline: WiFi, vCards, SEPA payment codes, Code 128, EAN-13, SVG or PNG.
Listing
From the official MCP registry (active).
Recent checks of io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13
CheckedResultHandshake
54 minutes agoHandshake completed1.44 s
2 days agoHandshake completed193 ms
4 days agoHandshake completed704 ms
5 days agoHandshake completed558 ms
7 days agoHandshake completed799 ms
8 days agoHandshake completed583 ms
9 days agoHandshake completed174 ms
12 days agoHandshake completed498 ms
13 days agoHandshake completed298 ms
15 days agoHandshake completed866 ms
17 days agoHandshake completed900 ms
18 days agoHandshake completed507 ms
19 days agoHandshake completed475 ms
20 days agoHandshake completed818 ms
21 days agoHandshake completed53 ms
21 days agoHandshake completed608 ms
23 days agoHandshake completed29 ms

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

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 io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13 and makes no claim about it beyond what these checks measured.