Remote MCP · Endpoint

gtinfetch – Agentic Commerce MCP server

No. gtinfetch – Agentic Commerce answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://x402.gtinfetch.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.gtinfetch/gtinfetch
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
73 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
gtinfetch — the GTIN resolver for AI agents. Any barcode, one call. 84M GTINs. x402 at the door.
Listing
From the official MCP registry (active).
Recent checks of gtinfetch – Agentic Commerce
CheckedResultHandshake
34 minutes agoHandshake completed73 ms
9 days agoHandshake completed95 ms
10 days agoHandshake completed87 ms
11 days agoHandshake completed150 ms
12 days agoHandshake completed63 ms
14 days agoHandshake completed84 ms
14 days agoHandshake completed417 ms
15 days agoHandshake completed132 ms
17 days agoHandshake completed89 ms
19 days agoHandshake completed74 ms
21 days agoHandshake completed96 ms
24 days agoHandshake completed217 ms
26 days agoHandshake completed126 ms
28 days agoHandshake completed82 ms

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

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