Remote MCP · Endpoint

LootCodes MCP server

No. LootCodes answered an MCP handshake 57 minutes ago.

UpLast checked 57 minutes ago

Server URL

https://www.lootcodes.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.lootcodes/catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
241 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search LootCodes game keys, gift cards and top-ups, compare prices and prepare a cart link.
Listing
From the official MCP registry (active).
Recent checks of LootCodes
CheckedResultHandshake
57 minutes agoHandshake completed241 ms
13 hours agoHandshake completed284 ms
1 day agoHandshake completed263 ms
2 days agoHandshake completed269 ms
4 days agoHandshake completed388 ms
7 days agoHandshake completed253 ms
9 days agoHandshake completed306 ms
12 days agoHandshake completed193 ms
14 days agoHandshake completed352 ms
16 days agoHandshake completed423 ms
18 days agoHandshake completed338 ms
20 days agoHandshake completed455 ms
22 days agoHandshake completed193 ms
23 days agoHandshake completed220 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 LootCodes and makes no claim about it beyond what these checks measured.