LuckDrop

Last 30 days

Uptime

100%

Response time

191 ms typical, 222 ms slowest 5%

Last check

3 h ago

Next check

in 3 h

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "luckdrop": {
      "type": "http",
      "url": "https://luckdrop.app/mcp"
    }
  }
}

5 tools

• 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) -- they are different numbers for the same

• 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 reason mirroring the contract's own revert st

• 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 without it you get a valid-looking answer

• 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 database status, so trust tradingOpen in this

• 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 DEPLOYMENT's prize escrows, and the result names in

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks