Quick Lotto lottery results MCP server
io.quicklotto/lottery-resultsquicklotto.iostreamable-httpv1.0.0Scanned
Winning numbers for 30+ world lotteries, minutes after each draw. Free, no key, CC BY 4.0.
3 tools: 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Quick Lotto lottery results MCP server can do
The Quick Lotto lottery results MCP server is published by quicklotto.io, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: latest_results and lottery_results), but cannot delete data. 1 tool only reads.
1 tool brings in text other people can write (list_lotteries).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 2Claude Code: ask
latest_resultsThe most recent winning numbers for every lottery covered, in one call.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it The most recent winning numbers for every lottery covered, in one call. Use this for "what were last night's numbers" or any question that does not name a specific past date.
lottery_resultsWinning numbers for one lottery — either its recent draw history, or a specific past date.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Winning numbers for one lottery — either its recent draw history, or a specific past date. Use the codes from list_lotteries.
Only reads 1Show 1 read-only tool
list_lotteriesList every lottery this site publishes results for, with the size of each draw machine (how many numbers are picked, and from how many), and the official ticket lotteries it covers…Reads text others writeNo findings
Why it is in this group
- The name "list_lotteries" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it List every lottery this site publishes results for, with the size of each draw machine (how many numbers are picked, and from how many), and the official ticket lotteries it covers (Thai Government Lottery, Kerala State Lottery) where carried. Call this first if you are unsure which lotteries are covered or what code to use.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:14 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://quicklotto.io/mcp: tools/list returned 3 tools to an anonymous client, including latest_results (write), lottery_results (write)
Posture changes
- Nov 20, 2026
- Reachable: no to yes
- HTTP status of an anonymous initialize: none to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 2
- Protocol version: none to 2025-06-18
- Nov 13, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 200; tools/list served without credentials: no -> yes (and 2 more).View diff
- Reachable: no to yes
- HTTP status of an anonymous initialize: none to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 2
- Protocol version: none to 2025-06-18
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http lottery-results https://quicklotto.io/mcpclaude mcp add --transport http lottery-results https://quicklotto.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__lottery-results__list_lotteries"
],
"ask": [
"mcp__lottery-results__latest_results",
"mcp__lottery-results__lottery_results"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as lottery-results. Review it before you use it.
Capability tags behind 1 rule
- mcp__lottery-results__list_lotteries untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.quicklotto/lottery-results/verify?hash=959cea5db9088c689e0bbe6bb843ab51dae4235fcf9898752a54c8ad6ec48540" | jq -e '.changed == false'Pinned hash 959cea5db908, from Nov 18, 2026, 14:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.quicklotto/lottery-results/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.quicklotto/lottery-results)Source: MCP Registry. Synced Oct 21, 2026, 18:52 UTC.
Quick Lotto lottery results MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Quick Lotto lottery results MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Quick Lotto lottery results MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Quick Lotto lottery results MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Quick Lotto lottery results MCP server have?
- 3 tools: 2 write, 1 read. latest_results, lottery_results and list_lotteries.
Does the Quick Lotto lottery results MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Quick Lotto lottery results MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Quick Lotto lottery results MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.