LuckDrop MCP server

• Registry nameapp.luckdrop/luckdropverified in the MCP registry

The registry name sits under luckdrop.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-21
• Tools5
• Server calls itselfluckdrop
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 213 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer572 ms
• Space in an agent's context≈ 1,533 tokensthe definitions of all its tools (5), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• luckdrop_get_draw

  Read 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)…

• luckdrop_check_entry

  Answer '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…

• luckdrop_get_results

  Read 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…

• luckdrop_list_market

  Read 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…

• luckdrop_check_prize

  Check whether a wallet has won a prize it has not yet collected, and get the transaction that claims it. Read from the chain, so it works for a wallet that entered without ever signing in to the website. SCOPE: this reads THIS…