Game Development
luckdrop.app
Reads LuckDrop draw state, checks entry eligibility and unclaimed prizes, retrieves round results, and lists marketplace ticket listings.
ENDPOINT 1
https://luckdrop.app/mcp
MCP server metadata
- Name
- luckdrop
- Version
- 1.0.0
Known tools 5
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.
Inferred read-onlyluckdrop_check_entryAnswer 'can this wallet enter the draw right now, and what exactly does it send'.
Potential side effectsluckdrop_list_marketRead the live marketplace: which tickets are listed, at what price, and whether the trading window is currently open.
Inferred read-onlyluckdrop_check_prizeCheck whether a wallet has won a prize it has not yet collected, and get the transaction that claims it.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.luckdrop]
url = "https://luckdrop.app/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"luckdrop": {
"type": "http",
"url": "https://luckdrop.app/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: luckdrop
Remote MCP URL: https://luckdrop.app/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"luckdrop": {
"url": "https://luckdrop.app/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"luckdrop": {
"type": "http",
"url": "https://luckdrop.app/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "luckdrop",
"transport": "streamable-http",
"url": "https://luckdrop.app/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.