Lucky Numbers
REMOTE · LUCKYNUMBERS.FUSEAPI.APP
Random number picks for fun: lottery-style presets, a custom range, daily numbers from a name.
Available components
Last scanned (4 minutes ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Entertainment and Games
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 Security83
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 448 tokens (~224/item across 2 items; 1 tools + 1 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
- Supports UI / widget rendering.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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 75
First indexed and scored.
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://luckynumbers.fuseapi.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fuseapi.app | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 7eca8a20975abd9b0e96fc1a06cb3bb3 |
| SANs: fuseapi.app, *.fuseapi.app | ||||||
| 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 secure
Validation of luckynumbers.fuseapi.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| fuseapi.app. | present | 2371 | 13 | Verified |
| luckynumbers.fuseapi.app. | Verified address RRset verified with the apex keys |
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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://luckynumbers.fuseapi.app/mcp | Verified | 200 | |
| http (plaintext) | http://luckynumbers.fuseapi.app/mcp | HTTPS enforced | 301 | https://luckynumbers.fuseapi.app/mcp |
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 →
lucky_numbers Lucky Numbers ~317
Random number picks for fun, like an "I'm feeling lucky" button. Presets: powerball (5 of 1-69 plus 1 of 1-26), mega_millions (5 of 1-70 plus 1 of 1-24), euromillions (5 of 1-50 plus 2 Lucky Stars of 1-12), uk_lotto (6 of 1-59), or custom with min, max and numbers. Give seed_text (a name or a birthday) for one set of numbers that stays the same for that text all day (UTC) and changes the next day. This is entertainment only: it predicts nothing, every combination has exactly the same odds, and no pick improves the chance of winning. Always show the user the note field with the numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many lines (sets of numbers) to draw. |
| date | string | – | Only with seed_text: the UTC day (YYYY-MM-DD) to draw for. Defaults to today. |
| game | string | yes | Which ball set to draw from. custom needs max, and takes min and numbers. |
| max | integer | – | custom only: the highest number. |
| min | integer | – | custom only: the lowest number. |
| numbers | integer | – | custom only: how many different numbers per line. |
| seed_text | string | – | Optional text such as a name or a birthday. The same text gives the same numbers all day. It is not stored. |
| Name | Type | Req | Description |
|---|---|---|---|
| bonusLabel | string | – | – |
| date | string | – | – |
| error | string | – | – |
| game | string | – | – |
| lines | array | – | – |
| mode | string | – | – |
| note | string | yes | – |
| title | string | – | – |
No examples provided.
How do I install the Lucky Numbers MCP server?
Lucky Numbers is a hosted endpoint at https://luckynumbers.fuseapi.app/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 · luckynumbers.fuseapi.app
claude mcp add --transport http app-openkrill-lucky-numbers 'https://luckynumbers.fuseapi.app/mcp'
What is the Lucky Numbers MCP server?
Lucky Numbers is an MCP server listed in the public MCP registry as app.openkrill/lucky-numbers. Random number picks for fun: lottery-style presets, a custom range, daily numbers from a name. This page covers its hosted endpoint (https://luckynumbers.fuseapi.app/mcp).
Is the Lucky Numbers MCP server safe to use?
Lucky Numbers scores 78 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 Lucky Numbers MCP server expose?
Lucky Numbers exposes 1 tool: lucky_numbers. Their descriptions and schemas cost roughly 317 tokens of context every time the server is loaded.
Does the Lucky Numbers MCP server require authentication?
No. We connected to Lucky Numbers without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Lucky Numbers MCP server still maintained?
Lucky Numbers 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.