io.github.csacanam/lotero
NPM · LOTERO-MCP
Provably fair on-chain slot machine for AI agents: x402 spins on Base, Chainlink VRF results.
Available components
Last scanned (8 hours ago)
Scores higher than 49% of npm servers
Category Crypto and Web3
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 112 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 115 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 537 tokens (~107/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "spin" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −6
- Stability: pass → 0.63 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → 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 npm/lotero-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 112 packages
| Packages resolved | 112 |
|---|---|
| Stale | 30 |
| 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 →
claim ~100
Withdraw ALL accumulated winnings (wins + referral earnings) to the player's wallet — COSTS 0.1 USDC via x402, gasless for the player. The fee is flat and the claim withdraws everything, so claim ONCE at the end of the session, not after each win. Check get_balances first (claimable must be > 0).
| Name | Type | Req | Description |
|---|---|---|---|
| player | string | – | Player wallet to claim for (defaults to LOTERO_PLAYER_ADDRESS) |
No output schema declared.
No examples provided.
get_balances ~82
Player balances: moneyAdded, moneyEarned, moneyClaimed, earnedByReferrals, claimedByReferrals (USDC base units, 6 decimals). Free. Claimable = moneyEarned - moneyClaimed. Check before claiming to avoid paying for an empty claim.
| Name | Type | Req | Description |
|---|---|---|---|
| player | string | – | Player wallet (defaults to LOTERO_PLAYER_ADDRESS) |
No output schema declared.
No examples provided.
get_contract_health ~48
System status: executor ETH/USDC balances, contract bankroll, VRF subscription funding. Free. Use to diagnose stuck rounds or before a session (if the contract is unhealthy, don't spin).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_round ~146
Get a spin's result by requestId. Free. resolved=false means Chainlink VRF hasn't delivered yet — poll every ~3s; if still unresolved after ~10 minutes check the `pending.vrfSubscriptionFunded` flag in the response (the requestId never expires; re-poll later, never re-spin to replace a pending round). Reels: 0-4 DOGE (5x), 5-6 BNB (14x), 7-8 ETH (20x), 9 BTC (30x); three matching symbols win; prize is in USDC base units (6 decimals).
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | requestId returned by spin |
No output schema declared.
No examples provided.
spin ~161
Execute one slot-machine spin — COSTS 1.1 USDC (1 bet + 0.1 fee) via x402, paid by the configured wallet. GAMBLING with negative expected value (RTP ~93%): require the human's explicit authorization and budget BEFORE calling, report every result honestly, and never loop spins to 'chase' a win. `player` should be the HUMAN's wallet (winnings accrue and get claimed there). Returns a requestId — the result is async (Chainlink VRF): poll get_round until resolved.
| Name | Type | Req | Description |
|---|---|---|---|
| player | string | – | Player wallet — the human's address (defaults to LOTERO_PLAYER_ADDRESS) |
| referral | string | – | Optional referral address (earns 1% of bets) |
No output schema declared.
No examples provided.
How do I install the io.github.csacanam/lotero MCP server?
io.github.csacanam/lotero runs locally as an npm package, launched with npx -y lotero-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 · lotero-mcp
claude mcp add csacanam-lotero -- npx -y lotero-mcp
What is the io.github.csacanam/lotero MCP server?
io.github.csacanam/lotero is an MCP server listed in the public MCP registry as io.github.csacanam/lotero. Provably fair on-chain slot machine for AI agents: x402 spins on Base, Chainlink VRF results. This page covers its npm package (lotero-mcp).
Is the io.github.csacanam/lotero MCP server safe to use?
io.github.csacanam/lotero scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.csacanam/lotero MCP server expose?
io.github.csacanam/lotero exposes 5 tools: spin, get_round, get_balances, claim, get_contract_health. Their descriptions and schemas cost roughly 537 tokens of context every time the server is loaded.
Is the io.github.csacanam/lotero MCP server still maintained?
io.github.csacanam/lotero 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 licence is the io.github.csacanam/lotero MCP server under?
io.github.csacanam/lotero declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.