Remote MCP · Endpoint

Quick Lotto lottery results MCP server

No. Quick Lotto lottery results answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://quicklotto.io/mcp

The last check completed an MCP handshake.

Registry name
io.quicklotto/lottery-results
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.16 s
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Winning numbers for 30+ world lotteries, minutes after each draw. Free, no key, CC BY 4.0.
Listing
From the official MCP registry (active).
Recent checks of Quick Lotto lottery results
CheckedResultHandshake
3 hours agoHandshake completed1.16 s
9 days agoHandshake completed929 ms
10 days agoHandshake completed839 ms
11 days agoHandshake completed797 ms
12 days agoHandshake completed2.81 s
14 days agoHandshake completed798 ms
14 days agoHandshake completed775 ms
15 days agoHandshake completed780 ms
17 days agoHandshake completed795 ms
19 days agoHandshake completed807 ms
21 days agoHandshake completed304 ms
24 days agoHandshake completed323 ms
26 days agoHandshake completed860 ms
28 days agoHandshake completed298 ms

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

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