Jackpot Calculator
REMOTE · JACKPOT-CALCULATOR-MCP.JIANKN.WORKERS.DEV
Estimate US lottery taxes, compare cash and annuity, split pool prizes and calculate jackpot odds.
Available components
Last scanned (1 hour ago)
Scores higher than 61% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 584 tokens (~146/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://jackpot-calculator-mcp.jiankn.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jiankn.workers.dev | CN=WE1,O=Google Trust Services,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a069e1183578c9af13262ecce3f73f53 |
| SANs: jiankn.workers.dev, *.jiankn.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jackpot-calculator-mcp.jiankn.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jackpot-calculator-mcp.jiankn.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://jackpot-calculator-mcp.jiankn.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
calculate_lottery_odds Jackpot probability and expected return ~78
Calculate jackpot coverage for distinct combinations in one drawing and optional before-tax expected ticket return.
| Name | Type | Req | Description |
|---|---|---|---|
| game | string | yes | – |
| jackpotCash | number | – | Optional jackpot cash option in US dollars, required to compute expected ticket return. |
| tickets | integer | – | Different number combinations in the SAME drawing; repeated combinations do not add coverage. |
No output schema declared.
No examples provided.
calculate_lottery_payout Lottery cash prize after taxes ~124
Estimate taxes and withholding on a known lottery cash prize. Input dollars; result integer cents. Bundled 2026 rules.
| Name | Type | Req | Description |
|---|---|---|---|
| game | string | – | – |
| locality | string | – | Only valid with stateCode NY. |
| otherIncome | number | – | Other annual income in US dollars before the standard deduction. |
| prize | number | yes | US dollars, not cents. Maximum $1 trillion. |
| stateCode | string | yes | US residence and ticket-purchase state, two-letter code. Cross-state claims are not modeled. |
| status | string | – | – |
No output schema declared.
No examples provided.
calculate_pool_share Equal lottery pool shares ~139
Estimate one equal member’s cash prize, taxes and withholding. Each member is assumed to have the specified tax profile.
| Name | Type | Req | Description |
|---|---|---|---|
| game | string | – | – |
| locality | string | – | Only valid with stateCode NY. |
| members | integer | yes | Equal owners of one ticket. Result assumes every member has the specified tax profile. |
| otherIncome | number | – | Other annual income in US dollars before the standard deduction. |
| prize | number | yes | Whole ticket cash prize in US dollars. |
| stateCode | string | yes | US residence and ticket-purchase state, two-letter code. Cross-state claims are not modeled. |
| status | string | – | – |
No output schema declared.
No examples provided.
compare_lump_sum_annuity Compare cash and annuity ~198
Compare a published cash option with 30 growing annuity payments after taxes, including present value and break-even rate.
| Name | Type | Req | Description |
|---|---|---|---|
| cashValue | number | yes | Published cash option in US dollars; do not infer it from a fixed ratio. |
| discountRate | number | – | Annual discount rate as a fraction, e.g. 0.04 for 4%. |
| game | string | – | – |
| jackpot | number | yes | Advertised annuity total in US dollars. |
| locality | string | – | Only valid with stateCode NY. |
| otherIncome | number | – | Other annual income in US dollars before the standard deduction. |
| sharePercent | number | – | Your percentage of one winning ticket. |
| stateCode | string | yes | US residence and ticket-purchase state, two-letter code. Cross-state claims are not modeled. |
| status | string | – | – |
| winners | integer | – | Number of jackpot-winning tickets sharing the prize. |
No output schema declared.
No examples provided.
How do I install the Jackpot Calculator MCP server?
Jackpot Calculator is a hosted endpoint at https://jackpot-calculator-mcp.jiankn.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · jackpot-calculator-mcp.jiankn.workers.dev
claude mcp add --transport http jiankn-jackpot-calculator 'https://jackpot-calculator-mcp.jiankn.workers.dev/mcp'
What is the Jackpot Calculator MCP server?
Jackpot Calculator is an MCP server listed in the public MCP registry as io.github.jiankn/jackpot-calculator. Estimate US lottery taxes, compare cash and annuity, split pool prizes and calculate jackpot odds. This page covers its hosted endpoint (https://jackpot-calculator-mcp.jiankn.workers.dev/mcp).
Is the Jackpot Calculator MCP server safe to use?
Jackpot Calculator scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Jackpot Calculator MCP server expose?
Jackpot Calculator exposes 4 tools: calculate_lottery_payout, compare_lump_sum_annuity, calculate_pool_share, calculate_lottery_odds. Their descriptions and schemas cost roughly 539 tokens of context every time the server is loaded.
Does the Jackpot Calculator MCP server require authentication?
No. We connected to Jackpot Calculator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Jackpot Calculator MCP server still maintained?
Jackpot Calculator is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.