Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ResultsZA

NPM · RESULTSZA-MCP

Official ResultsZA tools for South African and international lottery results.

Available components

0 this week 81 Trust /100

Last scanned (14 hours ago)

Scores higher than 69% of npm servers

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Stef1986/resultsza-sdk). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 10 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1271 tokens (~127/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 10 Nov 26 66

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/resultsza-mcp@0.1.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Stef1986/resultsza-sdk
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Stef1986/resultsza-sdk/.github/workflows/publish-mcp.yml@refs/heads/main
Rekor log index 3785314793
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:8b36fd7df4a34fae822bbb7f6ed6e367d7afdec09966e907af32c5fe1c1afdc7b201990e5407bcb7c0d9e1b26f2b47cf80decf65f26fed0fd7dfce216

Background: How many MCP packages publish verified provenance →

Dependencies 4 packages
Packages resolved 4
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~1,200 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
bulk_check_lottery_numbers ~181

Check up to 500 lines against one South African National Lottery draw. Returns matches and the prize division per line for that draw. Uses 1 API call PER LINE (up to 500). Only use this when the user explicitly has more than 10 lines; otherwise use check_lottery_numbers, which costs 1 call for up to 10 lines.

NameTypeReqDescription
datestringyesDraw date as YYYY-MM-DD.
gamestringyesSouth African game. Daily Lotto Plus, Lotto Plus 2 and Powerball Plus only for draws before 2026-06-01.
lines–yesOne line (array of numbers) or several lines (array of arrays). Lotto games: 6 numbers. Powerball games: 5 main numbers then the Powerball as the 6th. Daily Lotto: 5 numbers.

No output schema declared.

No examples provided.

check_balance ~38

Show the user's ResultsZA plan, calls used this month and calls left, and the subscription end date. Free: does not use any API calls.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

check_lottery_numbers ~150

Check up to 10 lines of numbers against one South African National Lottery draw. Returns matches and the prize division per line for that draw. Uses 1 API call per request (up to 10 lines).

NameTypeReqDescription
datestringyesDraw date as YYYY-MM-DD.
gamestringyesSouth African game. Daily Lotto Plus, Lotto Plus 2 and Powerball Plus only for draws before 2026-06-01.
lines–yesOne line (array of numbers) or several lines (array of arrays). Lotto games: 6 numbers. Powerball games: 5 main numbers then the Powerball as the 6th. Daily Lotto: 5 numbers.

No output schema declared.

No examples provided.

generate_lottery_numbers ~109

Random lines for a game using its correct number ranges. Uses 1 API call from your ResultsZA plan (regardless of the number of lines). Unknown games are rejected without using a call.

NameTypeReqDescription
gamestringyesGame name as the API uses it, e.g. "Lotto", "Powerball", "Daily Lotto", "EuroMillions", "UK49s Lunchtime".
linesinteger–How many lines, 1 to 500 (default 1).

No output schema declared.

No examples provided.

get_horse_race ~88

The full runner table for one race at a South African meeting. Uses 1 API call from your ResultsZA plan.

NameTypeReqDescription
datestringyesMeeting date as YYYY-MM-DD.
race_nointegeryesRace number at that meeting.
venuestringyesRacecourse as named by get_horse_racing_meetings, e.g. "Greyville".

No output schema declared.

No examples provided.

get_horse_racing_card ~80

All races at one South African meeting with the top three finishers and tote dividends. Uses 1 API call from your ResultsZA plan.

NameTypeReqDescription
datestringyesMeeting date as YYYY-MM-DD.
venuestringyesRacecourse as named by get_horse_racing_meetings, e.g. "Greyville".

No output schema declared.

No examples provided.

get_horse_racing_meetings ~108

South African horse racing meetings (date, venue, number of races) in a date range of at most 7 days. Defaults to the last 7 days. Use it to find the venue name for the other racing tools. Uses 1 API call from your ResultsZA plan.

NameTypeReqDescription
from_datestring–Start date as YYYY-MM-DD.
to_datestring–End date as YYYY-MM-DD (at most 7 days after from_date).

No output schema declared.

No examples provided.

get_lottery_results ~218

Official draw results for one game: South African National Lottery games (with prize divisions, winners and jackpot), UK 49's, EuroMillions, Irish Lotto, US Powerball, Mega Millions, Kenya, Nigeria, Ghana and Gosloto. Omit date for the latest draw. Gosloto and Kenya with a date return every draw that day. Uses 1 API call from your ResultsZA plan.

NameTypeReqDescription
datestring–Draw date as YYYY-MM-DD. Omit for the latest draw.
draw_idstring–Gosloto only: one draw by its number (ignored when date is given).
draw_namestring–Nigeria or Ghana only: one draw, e.g. "PREMIER BINGO" or "Ghana Lucky Tuesday". Omit for all.
gamestringyesThe lottery game.
kenya_typestring–Kenya only: daily draws or the Mega Jackpot.
uk49s_drawstring–Required when game is UK49s.

No output schema declared.

No examples provided.

get_number_statistics ~126

Historical number statistics for a game: hot and cold numbers, how often each number was drawn, or the most common pairs. Products include the South African games, "UK49s" (all four draws combined), "EuroMillions", "US Powerball", "Kenya Lotto" and "Gosloto 6/45". Unknown products are rejected without using a call. Uses 1 API call from your ResultsZA plan.

NameTypeReqDescription
kindstringyesWhich statistics.
productstringyesGame, e.g. "Lotto" or "UK49s".

No output schema declared.

No examples provided.

lucky_numbers_from_text ~102

Personalised numbers for a game derived from a name, date or phrase (the same text always gives the same numbers). For fun only. Uses 1 API call from your ResultsZA plan.

NameTypeReqDescription
gamestringyesGame name as the API uses it, e.g. "Lotto", "Powerball", "Daily Lotto", "EuroMillions", "UK49s Lunchtime".
textstringyesA name, date or phrase.

No output schema declared.

No examples provided.

Install

How do I install the ResultsZA MCP server?

ResultsZA runs locally as an npm package, launched with npx -y resultsza-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · resultsza-mcp

# add to Claude Code
claude mcp add za-co-resultsza-mcp -- npx -y resultsza-mcp
Common questions

What is the ResultsZA MCP server?

ResultsZA is an MCP server listed in the public MCP registry as za.co.resultsza/mcp. Official ResultsZA tools for South African and international lottery results. This page covers its npm package (resultsza-mcp).

Is the ResultsZA MCP server safe to use?

ResultsZA scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ResultsZA MCP server expose?

ResultsZA exposes 10 tools: check_balance, get_lottery_results, check_lottery_numbers, bulk_check_lottery_numbers, get_horse_racing_meetings, and 5 more. Their descriptions and schemas cost roughly 1,200 tokens of context every time the server is loaded.

Is the ResultsZA MCP server still maintained?

ResultsZA is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the ResultsZA MCP server under?

ResultsZA declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the ResultsZA MCP server?

VerifyMCP ran 15 checks on ResultsZA, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about ResultsZA: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.