Remote MCP · Endpoint

Jackpot Calculator MCP server

No. Jackpot Calculator answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://jackpot-calculator-mcp.jiankn.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.jiankn/jackpot-calculator
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
291 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Estimate US lottery taxes, compare cash and annuity, split pool prizes and calculate jackpot odds.
Listing
From the official MCP registry (active).
Recent checks of Jackpot Calculator
CheckedResultHandshake
1 hour agoHandshake completed291 ms
3 days agoHandshake completed291 ms
12 days agoHandshake completed315 ms
13 days agoHandshake completed241 ms
15 days agoHandshake completed356 ms
15 days agoHandshake completed176 ms
17 days agoHandshake completed166 ms
18 days agoHandshake completed172 ms
18 days agoHandshake completed145 ms
20 days agoHandshake completed226 ms
22 days agoHandshake completed307 ms
25 days agoHandshake completed499 ms
27 days agoHandshake completed191 ms
29 days agoHandshake completed276 ms

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

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