Overview
Pass a supported game identifier—powerball, megamillions, euromillions, or lottomax. The lookup returns the latest drawn numbers, game-specific bonus balls, draw date, and jackpot totals updated daily. EuroMillions draws include Lucky Stars, while Powerball and Mega Millions return their respective special balls. Paid plans can pass a past date for historical drawings or access upcoming draw estimates.
Live Test Lottery Results Skill Skill →
The tool
Once your client is connected to the VerveKit server, this appears in its tool list as LotteryResultsSkill. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.
{
"name": "LotteryResultsSkill",
"arguments": {
"numbers": "powerball"
}
}You do not name the tool yourself; the model picks it. Asking about powerball in the terms this skill covers is enough for it to reach for LotteryResultsSkill on its own — naming it explicitly also works, and is the way to force the call.
Connecting
One server URL covers every skill in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.
{
"mcpServers": {
"vervekit": {
"url": "https://api.vervekit.com/v1/mcp"
}
}
}https://api.vervekit.com/v1/mcpPer-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.
Arguments
These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.
| Argument | Type | Description |
|---|---|---|
numbersRequired | string | The lottery game to lookup: powerball, megamillions, euromillions, or lottomaxpowerballmegamillionseuromillionslottomax |
dateOptionalPremium | string | Optional date for historical lookup (YYYY-MM-DD). Returns the nearest draw to this date. date |
What the model gets back
The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.
{
"status": "ok",
"error": null,
"data": {
"lotteryType": "megamillions",
"drawDate": "2026-02-04",
"numbers": [
10,
50,
55,
58,
59,
5
],
"megaBall": 5,
"jackpot": "$70 Million",
"jackpotValue": 70000000,
"jackpotFormatted": "$70 Million",
"nextDraw": {
"drawDate": "2026-02-07",
"jackpot": "$82 Million",
"jackpotValue": 82000000,
"cashValue": "$37.2 Million",
"cashValueValue": 37200000
}
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
lotteryType | string | megamillions | Which lottery game this result is for: powerball, megamillions, euromillions, or lottomax |
drawDate | string | 2026-02-04 | Date of the drawing |
numbers | array | [10,50,55] | Array of winning main numbers (for Powerball and Mega Millions, also includes the bonus ball as the final entry) |
megaBall | number | 5 | The Mega Ball number drawn. Mega Millions only |
jackpot | string | $70 Million | Jackpot amount for this drawing |
jackpotValue | number | 70000000 | Jackpot amount for this drawing as a numeric value |
jackpotFormatted | string | $70 Million | Jackpot amount for this drawing, formatted as a currency string (same value as `jackpot`) |
nextDrawPremium | object | {…} | Estimated details for the upcoming, not-yet-drawn draw. Absent for a short window after each draw, while the operator recalculates the estimate |
nextDraw.drawDatePremium | string | 2026-02-07 | Date of the upcoming draw (best-effort; may be null when the source lists it only as a relative time) |
nextDraw.jackpotPremium | string | $82 Million | Estimated jackpot for the upcoming draw |
nextDraw.jackpotValuePremium | number | 82000000 | Estimated jackpot for the upcoming draw as a numeric value |
nextDraw.cashValuePremium | string | $37.2 Million | Estimated cash (lump-sum) value for the upcoming draw. Powerball and Mega Millions only |
nextDraw.cashValueValuePremium | number | 37200000 | Estimated cash value for the upcoming draw as a numeric value. Powerball and Mega Millions only |
Failure modes
Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.
| Status | What it means |
|---|---|
400 / 422 | The arguments did not validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Blocked by a key restriction or an IP allow-list. Never a bad identity. |
404 | This skill is not part of VerveKit. Check the catalog. |
429 | Out of credits, or a brief rate limit. The message tells them apart. |
A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.
Use cases
- Ticket Verification Portals
- Lottery tracking apps compare user-submitted ticket numbers against returned winning numbers and bonus balls to alert players to matching prizes.
- News Media Drawboards
- When a major draw concludes, regional news outlets display winning numbers and jackpot values on automated result widgets.
- Convenience Retail Displays
- Broadcast updated winning numbers and current jackpot totals on in-store digital screens to inform lottery customers at the checkout counter.
- Office Lottery Syndicates
- Pool managers verify group ticket entries against the latest draw dates and winning number arrays to automate weekly payout calculations.
Other ways to use Lottery Results Skill
Set up Lottery Results Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.
Related
More in Data Lookup: