Block Lottos
PYPI · BLOCKLOTTOS-MCP
Safe Block Lottos MCP for Base tickets and Base or Polygon jackpot reads.
Available components
Last scanned (1 day ago)
Scores higher than 84% of PyPI servers
Category Crypto and Web3
Recent critical change
GHSA-6q48-6c7w-9gw2 affects this package (21 Oct 2026). See the changelog before you install this server.
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
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 56 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 627 tokens (~52/item across 12 items; 10 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- Maintenance
- Security disclosure
- Schema quality
- Stability
- 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.
- License in Provenance & TransparencyLicence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
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 →
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 2 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 +1
- Stability: 0.97 → pass security
- 30 Oct 26 −1
- Stability: pass → 0.97 functional
- 28 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 27 Oct 26 +5
- Source repository: fail → pass ▲ security
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 5 Nov 2026 · Analysed pypi/blocklottos-mcp@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_wallet_prizes ~31
Check whether a Base wallet has an outstanding failed automatic prize payout.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet_address | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
confirm_ticket_purchase ~60
Verify the Base receipt, sender, contract, method, and TicketPurchased event. This is the only completion check.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| execution_id | – | – | – |
| tx_hash | string | yes | – |
| wallet_address | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_capabilities ~31
Read the authoritative Base game, 1-USDC price, gas, workflow, payout, and safety details.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_draw_history ~39
Read one to ten completed Base draws, or begin at a specified public draw ID.
| Name | Type | Req | Description |
|---|---|---|---|
| draw_id | – | – | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_draw_proof ~37
Read the public proof for a Base draw. Omit draw_id for the current public proof when available.
| Name | Type | Req | Description |
|---|---|---|---|
| draw_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_jackpot ~42
Read the effective jackpot. Minimum: 100 USDC on Base or 100 POL on Polygon; higher live jackpot applies.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_or_create_referral ~54
Create or retrieve a free referral ID tied to an EVM payout wallet. No funds move and the wallet cannot later be replaced by this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| wallet_address | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_stats ~25
Read the current Base draw number, jackpot, next draw time, and contract metadata.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_wallet_tickets ~35
Read a Base wallet's tickets for the active draw. This does not move funds.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet_address | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
prepare_ticket_purchase ~95
Prepare exactly one unsigned 1-USDC Base ticket purchase. It never signs or broadcasts. Obtain owner approval or apply a narrow owner policy before submitting returned wallet transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| idempotency_key | string | yes | – |
| max_price_usdc | string | – | – |
| numbers | array | yes | – |
| referral_id | – | – | – |
| valid_until | – | – | – |
| wallet_address | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Block Lottos MCP server?
Block Lottos runs locally as a PyPI package, launched with uvx blocklottos-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · blocklottos-mcp
claude mcp add com-blocklottos-blocklottos -- uvx blocklottos-mcp
What is the Block Lottos MCP server?
Block Lottos is an MCP server listed in the public MCP registry as com.blocklottos/blocklottos. Safe Block Lottos MCP for Base tickets and Base or Polygon jackpot reads. This page covers its PyPI package (blocklottos-mcp).
Is the Block Lottos MCP server safe to use?
Block Lottos scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 Block Lottos MCP server expose?
Block Lottos exposes 10 tools: get_capabilities, get_jackpot, get_stats, get_draw_history, get_draw_proof, and 5 more. Their descriptions and schemas cost roughly 449 tokens of context every time the server is loaded.
Is the Block Lottos MCP server still maintained?
Block Lottos is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Block Lottos MCP server?
VerifyMCP ran 15 checks on Block Lottos, 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 Block Lottos: License. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.