Remote MCP · Endpoint

Lottery Numbers MCP server

Yes, as of 4 days ago: the server returned an HTTP error.

DownLast checked 4 days ago

Server URL

https://hanaprism.com/mcp/lottery

The last check failed: the server returned an HTTP error.

Registry name
com.hanaprism/lottery-numbers
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
77.8% from 9 checks
Described by its publisher as
Lottery picks in any format, past draws, ticket check, and a link for numbers drawn from a sentence.
Listing
From the official MCP registry (deprecated).
Recent checks of Lottery Numbers
CheckedResultHandshake
4 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
16 days agoHandshake completed746 ms
17 days agoHandshake completed687 ms
19 days agoHandshake completed651 ms
20 days agoHandshake completed665 ms
21 days agoHandshake completed690 ms
22 days agoHandshake completed653 ms
22 days agoHandshake completed646 ms

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

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.