LuckDrop
app.luckdrop/luckdrop · 1.0.0
Enter LuckDrop's free weekly on-chain prize draw, check the live draw, and claim prizes.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://luckdrop.app/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 5 tools.
- Protocol
- 2025-06-18
- Calls itself
- luckdrop 1.0.0
- Handshake time
- 150 ms
- HTTP status
- 200
The tools it lists (5, as of 6 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
luckdrop_get_drawRead the state of the live LuckDrop draw: which draw is running, its phase, the prize, how many tickets are in, and the countdown to the next round. Publishes both weekNumber (the display number) and contractWeekId (the on-chain number) -- they are different numbers for the same draw. The `week` block comes from our database and the `chain` block from the contracts; `chain.inSync` says whether they agree. Trust `chain` when they disagree. Do NOT compare chain.state to week.status yourself: the two advance at different moments and both are correct, so a string comparison reports a healthy draw
luckdrop_check_entryAnswer 'can this wallet enter the draw right now, and what exactly does it send'. Sourced from the CHAIN rather than our database, because this gates a transaction and a stale yes costs the caller gas on a revert. Returns canEnter, a reason mirroring the contract's own revert strings, and the exact transaction to send. Entry is free -- the entrant pays only gas. Call this before sending an entry, every time. This returns an UNSIGNED transaction ({to, data, value}). This service never signs for the user and never holds keys. The user must approve and send it from their own wallet on Base Sepo
luckdrop_get_resultsRead a single draw's five rounds and its winner. `week` is the DISPLAY week number by default. If you are following contractWeekId from the chain, pass idSpace='contract' -- the same number means different draws in the two id spaces, and without it you get a valid-looking answer describing the WRONG draw. The response echoes back which space it used, plus both ids. NETWORK: LuckDrop is currently running on Base Sepolia, a TEST NETWORK. LUCK coins earned or won here are for testing and have no monetary value. The contracts do not exist on Base mainnet.
luckdrop_list_marketRead the live market: which tickets are listed, at what price, and whether the trading window is currently open. Tickets are NFTs and can be traded while a draw is running. The CONTRACT decides whether trading is open, not the draw's database status, so trust tradingOpen in this result rather than inferring it from the phase. A completed sale pays a fee read from feeBasisPoints() on the market contract, and part of that fee goes into the draw's prize pool -- the share is prizeShareBasisPoints() on the same contract. BOTH are admin setters (fee ceiling 10%), so read both rather than assuming
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
app.luckdrop/luckdrop, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 27 days ago. The registry entry · luckdrop.app