Remote MCP · Endpoint

TuLotero MCP server

No. TuLotero answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://mcp.tulotero.com/mcp

The last check completed an MCP handshake.

Registry name
com.tulotero/tulotero
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
309 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Resultados, botes, reglas y comprobación de premios de las loterías del Estado (España).
Listing
From the official MCP registry (active).
Recent checks of TuLotero
CheckedResultHandshake
43 minutes agoHandshake completed309 ms
8 days agoHandshake completed316 ms
9 days agoHandshake completed301 ms
11 days agoHandshake completed330 ms
12 days agoHandshake completed314 ms
13 days agoHandshake completed313 ms
14 days agoHandshake completed325 ms
14 days agoHandshake completed310 ms
16 days agoHandshake completed322 ms
19 days agoHandshake completed312 ms
21 days agoHandshake completed313 ms
24 days agoHandshake completed389 ms
26 days agoHandshake completed312 ms
28 days agoHandshake completed312 ms

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

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