Remote MCP · Endpoint

Gtin MCP server

No. Gtin answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/gtin/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/gtin
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
185 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Barcode / GTIN validation MCP (EAN-13, UPC-A, EAN-8, GTIN-14).
Listing
From the official MCP registry (active).
Recent checks of Gtin
CheckedResultHandshake
1 hour agoHandshake completed185 ms
22 hours agoHandshake completed90 ms
2 days agoHandshake completed157 ms
3 days agoHandshake completed67 ms
4 days agoHandshake completed245 ms
5 days agoHandshake completed112 ms
6 days agoHandshake completed254 ms
8 days agoHandshake completed559 ms
11 days agoHandshake completed91 ms
13 days agoHandshake completed1.92 s
16 days agoHandshake completed75 ms
18 days agoHandshake completed54 ms
20 days agoHandshake completed355 ms
22 days agoHandshake completed60 ms
24 days agoHandshake completed55 ms
26 days agoHandshake completed67 ms
27 days agoHandshake completed56 ms
29 days agoHandshake completed80 ms

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

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