Remote MCP · Endpoint
Lottery Numbers MCP server
No. Lottery Numbers answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://hanaprism.com/mcp/lottery
The last check completed an MCP handshake.
- Registry name
- com.hanaprism/lottery-numbers
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 665 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- Lottery picks in any format, past draws, ticket check, and a link for numbers drawn from a sentence.
- Website
- https://hanaprism.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 665 ms |
| 1 day ago | Handshake completed | 690 ms |
| 2 days ago | Handshake completed | 653 ms |
| 2 days ago | Handshake completed | 646 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 Lottery Numbers and makes no claim about it beyond what these checks measured.