io.github.rtp-coder/stake-analyzer
REMOTE · STAKEANALYZER.LIVE
Stake Originals odds, house edge, payouts and bet verification, slot RTP and bonus drops.
Available components
Last scanned (3 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 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 1198 tokens (~92/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 45% of tool parameters carry a description.Partial
- 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Tool “stake_house_edge” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 73
First indexed and scored.
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 · Probed https://stakeanalyzer.live/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=stakeanalyzer.live | CN=WE1,O=Google Trust Services,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 3eb2a41cea604a5f1358dce18dfac1cc |
| SANs: stakeanalyzer.live, *.stakeanalyzer.live | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of stakeanalyzer.live. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| live. | present | 4724, 36322 | 8, 8 | Verified |
| stakeanalyzer.live. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-eval' 'unsafe-inline' *.umami.is static.cloudflareinsights.com; style-src 'self' 'unsafe-inline'; img-src 'self' blob: data: *.supabase.co *.googleusercontent.com; font-src 'self' data:; connect-src 'self' *.supabase.co *.umami.is api-gateway.umami.dev cloudflareinsights.com; frame-src 'self' https://*.engine.io https://*.stake-engine.com https://www.youtube-nocookie.com; object-src 'none'; base-uri 'self'; form-action 'self'; worker-src 'self' blob:; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://stakeanalyzer.live/mcp | Verified | 200 | |
| http (plaintext) | http://stakeanalyzer.live/mcp | HTTPS enforced | 301 | https://stakeanalyzer.live/mcp |
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 →
stake_bonus_drops Latest Stake bonus drop codes ~48
The newest bonus drop codes Stake posted to its official Telegram channels for Stake and Stake.us, with value, requirement and post time. Codes expire within minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
stake_chain_latest Latest Stake Crash, Slide or Zoo rounds ~60
The newest round checked on a Stake Crash, Slide or Zoo hash chain and the rounds before it, with each round's multiplier or animals. stake.com and stake.us run separate chains.
| Name | Type | Req | Description |
|---|---|---|---|
| game | string | yes | – |
| site | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
stake_crash_droughts Stake Crash and Slide droughts ~71
Rounds since the last 2x, 10x and 100x and the longest run without each, over the newest rounds checked on a Stake Crash or Slide chain. stake.com and stake.us run separate chains.
| Name | Type | Req | Description |
|---|---|---|---|
| game | string | – | – |
| site | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
stake_crash_odds Stake Crash and Slide odds ~102
Chance a Stake Crash or Slide round reaches a cash-out target, the return at that target, average rounds between hits, the chance of a hit within N rounds, and the chance of an instant 1.00x round.
| Name | Type | Req | Description |
|---|---|---|---|
| game | string | – | – |
| rounds | integer | – | Rounds to play, for the chance of at least one hit |
| target | number | yes | Cash-out multiplier, such as 2 or 10 |
Structured output declared, but exposes no named fields.
No examples provided.
stake_hilo_path Stake HiLo path payout ~89
Payout and odds of a HiLo path: the start card, then each guess and the card that came. The first guess carries the house edge, later guesses pay fair odds, skips deal a new card without multiplying.
| Name | Type | Req | Description |
|---|---|---|---|
| start | – | yes | Start card: 1 to 13 or A, 2 to 10, J, Q, K |
| steps | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
stake_house_edge Stake house edge and RTP ~54
Return to player, house edge and top payout for Stake Originals, computed from each game's payout table. Without a game it summarises the Originals it covers; with one it lists every setting.
| Name | Type | Req | Description |
|---|---|---|---|
| game | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
stake_list_games List Stake Originals ~36
Every Stake Original the tools cover, with its seed checker, simulator and verifier links. Call this first when unsure of a game id.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
stake_payout_odds Stake payout odds at a setting ~87
Multipliers and the exact chance of each result for one Stake Original at one setting, such as Mines with 3 mines and 5 gems, Keno medium risk with 5 picks, Plinko 16 rows high risk, or Dice over 50. Includes RTP, win chance and the top payout.
| Name | Type | Req | Description |
|---|---|---|---|
| game | string | yes | – |
| options | object | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
stake_seed_hunt_odds Odds of a payout within a run of nonces ~101
How often a Stake Original pays a given multiplier or more at a setting, and the chance at least one such payout sits inside a run of N nonces, the maths behind the Seed Hunter.
| Name | Type | Req | Description |
|---|---|---|---|
| game | string | yes | – |
| nonces | integer | – | Length of the run of nonces |
| options | object | – | – |
| threshold | number | yes | Payout multiplier to reach, such as 10 or 1000 |
Structured output declared, but exposes no named fields.
No examples provided.
stake_slot_lookup Look up a Stake Engine slot ~75
Finds Stake Engine slots on Stake by name or publisher and returns each mode's published RTP, with the max multiplier and its odds where the site has computed that mode's table.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | A mode name such as base or bonus to preview |
| query | string | yes | Part of the slot or publisher name |
Structured output declared, but exposes no named fields.
No examples provided.
stake_slot_rankings Top Stake Engine slots ~59
The most played Stake Engine slots on Stake by turnover or bet count over a range, with publisher and average bet, from Stake Engine Insights.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| range | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
stake_verify_bets Verify Stake bets from a seed pair ~171
Replays Stake Originals bets from a revealed server seed, client seed and nonce with Stake's provably fair algorithm and reports each result and multiplier, up to 200 nonces per call. Returns the SHA-256 of the server seed to compare with the hash Stake showed before the seed was revealed. Needs the unhashed server seed, which Stake reveals after the pair is rotated.
| Name | Type | Req | Description |
|---|---|---|---|
| clientSeed | string | yes | – |
| count | integer | – | How many nonces from the first one |
| game | string | yes | – |
| nonce | integer | yes | First nonce to verify |
| options | object | – | The bet settings, such as bombCount and gems for Mines or diceTarget and diceIsRollOver for Dice |
| serverSeed | string | yes | The revealed, unhashed server seed |
Structured output declared, but exposes no named fields.
No examples provided.
stake_vip_progress Stake VIP progress and cost ~104
Wager left to the next Stake VIP level from a level and progress percentage or a total wagered figure, with the expected cost of that wager on the cheapest games and the sports bet equivalent.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | Current level id, such as platinum or diamond-2 |
| progressPercent | number | – | Progress to the next level as Stake shows it |
| totalWager | number | – | Total wagered in USD, instead of level and progress |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.rtp-coder/stake-analyzer MCP server?
io.github.rtp-coder/stake-analyzer is a hosted endpoint at https://stakeanalyzer.live/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · stakeanalyzer.live
claude mcp add --transport http rtp-coder-stake-analyzer 'https://stakeanalyzer.live/mcp'
What is the io.github.rtp-coder/stake-analyzer MCP server?
io.github.rtp-coder/stake-analyzer is an MCP server listed in the public MCP registry as io.github.rtp-coder/stake-analyzer. Stake Originals odds, house edge, payouts and bet verification, slot RTP and bonus drops. This page covers its hosted endpoint (https://stakeanalyzer.live/mcp).
Is the io.github.rtp-coder/stake-analyzer MCP server safe to use?
io.github.rtp-coder/stake-analyzer scores 74 out of 100 on VerifyMCP. 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.rtp-coder/stake-analyzer MCP server expose?
io.github.rtp-coder/stake-analyzer exposes 13 tools: stake_list_games, stake_house_edge, stake_payout_odds, stake_crash_odds, stake_verify_bets, and 8 more. Their descriptions and schemas cost roughly 1,057 tokens of context every time the server is loaded.
Does the io.github.rtp-coder/stake-analyzer MCP server require authentication?
No. We connected to io.github.rtp-coder/stake-analyzer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.rtp-coder/stake-analyzer MCP server still maintained?
io.github.rtp-coder/stake-analyzer 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.