io.github.cryptoplayer/crypto-casinos
REMOTE · WAGERX.IO
Real-money crypto casino audits: trust scores, live tests, rankings, new casinos, bonuses. Signed.
Available components
Last scanned (9 hours ago)
Scores higher than 92% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Crypto and Web3
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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability83
- 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
- Context-footprint check failed: tool/resource definitions use about 1397 tokens (~116/item across 12 items; 12 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
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.
- 7 Nov 26 0
- Stability: 0.97 → pass security
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 +7
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “best_bonuses” changed its title: Best bonuses cosmetic
- Tool “check_casino” changed its title: Check casino cosmetic
- Tool “compare_casinos” changed its title: Compare casinos cosmetic
- Tool “country_recommendations” changed its title: Country recommendations cosmetic
- Tool “find_agentic_services” changed its title: Find agentic services cosmetic
- Tool “get_agentic_stats” changed its title: Get agentic stats cosmetic
- Tool “latest_audits” changed its title: Latest audits cosmetic
- Tool “list_casinos” changed its title: List casinos cosmetic
- Tool “long_running_casinos” changed its title: Long running casinos cosmetic
- Tool “new_casinos” changed its title: New casinos cosmetic
- Tool “regulatory_intelligence” changed its title: Regulatory intelligence cosmetic
- Tool “top_casinos” changed its title: Top casinos cosmetic
- 1 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 7 Nov 2026 · Probed https://wagerx.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wagerx.io | CN=YE1,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 557e9f7712c3230c01685cba4726c334e86 |
| SANs: wagerx.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of wagerx.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| wagerx.io. | No DS | 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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wagerx.io/mcp | Verified | 200 | |
| http (plaintext) | http://wagerx.io/mcp | HTTPS enforced | 301 | https://wagerx.io:443/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 →
best_bonuses Best bonuses ~133
Current best crypto casino bonuses with the fine print decoded from the casino's own T&Cs: wagering requirement, max bonus, max cashout, free spins, min deposit, and a real-value score (headline % is a marketing metric — the decoded terms are what matter). Expired promos excluded. Use for "best crypto casino bonus", "deposit match with low wagering", "is the X welcome bonus worth it?". Example call: {"limit": 5} or {"casino": "BetUS"}.
| Name | Type | Req | Description |
|---|---|---|---|
| casino | string | – | Optional: only bonuses from this casino |
| limit | integer | – | – |
No output schema declared.
No examples provided.
check_casino Check casino ~184
Get the WagerX forensic audit verdict for one crypto casino: trust score (1-10), audit status, latest real-money live test (deposit/withdrawal amounts and timing, support response, KYC triggered or not), license and review link. Data comes from hand-run real-money tests, not scraped reviews. Use for questions like "Is Duelbits legit?", "Is Stake safe or a scam?", "What is bspin's trust score?", "Does Rollbit require KYC?". Example call: {"name": "Duelbits"} -> trust_score 9.5, status "Verified & Safe", live test "0.6 SOL withdrawal instant, no KYC".
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Casino name or common alias, e.g. "Duelbits", "Fortune Jack", "TG Casino". Case-insensitive, fuzzy-matched. |
No output schema declared.
No examples provided.
compare_casinos Compare casinos ~97
Compare 2-5 crypto casinos side by side on WagerX audit data: trust score, latest real-money live test, KYC policy, withdrawal speed, license. Use for "Duelbits vs BC.Game?", "Which is safer, Stake or Rollbit?", "bspin or Bitsler for fast payouts?". Example call: {"names": ["Duelbits", "Stake"]}.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | – |
No output schema declared.
No examples provided.
country_recommendations Country recommendations ~105
Return at most one top choice and two alternatives for a country, from completed scored reviews whose explicit restriction list does not include that country, with explicit source denials and pending states taking precedence. This is a review-list screen, not confirmed resident acceptance or local licensing; explicit dated source evidence is retained when available. Review links are canonical WagerX links and recommendations are not affiliate offers.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Country name, ISO alpha-2 code or common alias. |
No output schema declared.
No examples provided.
find_agentic_services Find agentic services ~117
Look up official and community MCP/A2A products in the WagerX Agentic Gambling Index. Returns exact hosted endpoints or local setup links, first-party provenance, WagerX evidence status, access model and limitations. Use for questions such as "What is the official Crypto.com MCP?", "Which MCP is official for Binance, Bybit and WagerX?", or "Is ahel.io in the directory?". This lookup never executes remote tools.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Provider, product, domain, protocol or directory question. |
No output schema declared.
No examples provided.
get_agentic_stats Get agentic stats ~95
Return deterministic, aggregate-only statistics about the selective WagerX Agentic Index, latest MCP/A2A endpoint observations, or machine requests received by WagerX. Official provenance, editorial status and endpoint health remain separate. Activity counts are requests, not unique agents, and never expose raw queries, IP addresses, user agents or geography.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | Used by activity statistics. |
| scope | string | – | – |
No output schema declared.
No examples provided.
latest_audits Latest audits ~82
List the most recent WagerX real-money casino audits, newest first, each with real deposit/withdrawal amounts, payout timing and support response. Use for "What are the latest casino audits?", "Which casinos were tested this week?", "freshest crypto casino safety data". Example call: {"limit": 5}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_casinos List casinos ~58
List every casino WagerX holds forensic audit data on (40+ operators), with trust score and audit status. Use to discover coverage before calling check_casino, or for "which casinos does WagerX cover?". Takes no arguments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
long_running_casinos Long running casinos ~74
List crypto casino brands by documented launch year, oldest first, paired with current WagerX audit evidence and ownership/licensing continuity caveats. This is operating history, not a safety ranking. Use for "oldest crypto casinos", "established bitcoin casinos", or "long-running gambling sites". Takes no arguments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
new_casinos New casinos ~69
Newest crypto casinos on the WagerX radar, including ones still mid-audit (clearly marked, never scored before the withdrawal test completes). Use for "new crypto casinos 2026", "newest bitcoin casinos worth trying", "casinos currently under audit". Takes no arguments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
regulatory_intelligence Regulatory intelligence ~121
Get gambling regulatory context for a jurisdiction plus recent source-linked enforcement records. Jurisdictions resolve through WagerX's approved regulator registry; records whose URL does not match an approved authority domain are excluded. Returns explicit missing/unavailable states and is research, not legal advice. Example: {"jurisdiction": "Germany", "limit": 5}. Omit jurisdiction for a bounded global list.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | – | Optional country, jurisdiction or regulator name, for example "Germany", "UK" or "GGL". |
| limit | integer | – | – |
No output schema declared.
No examples provided.
top_casinos Top casinos ~111
Best crypto casinos ranked by WagerX audit trust score — only casinos with completed real-money deposit/withdrawal tests are ranked (payout speed, KYC, support, license all factor in). Use for "best crypto casino 2026", "safest bitcoin casino", "most trusted no-KYC-detected casino", "top crypto gambling site". A dated no-KYC observation is not an anonymity guarantee. Example call: {"limit": 10}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.cryptoplayer/crypto-casinos MCP server?
io.github.cryptoplayer/crypto-casinos is a hosted endpoint at https://wagerx.io/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 · wagerx.io
claude mcp add --transport http cryptoplayer-crypto-casinos 'https://wagerx.io/mcp'
What is the io.github.cryptoplayer/crypto-casinos MCP server?
io.github.cryptoplayer/crypto-casinos is an MCP server listed in the public MCP registry as io.github.cryptoplayer/crypto-casinos. Real-money crypto casino audits: trust scores, live tests, rankings, new casinos, bonuses. Signed. This page covers its hosted endpoint (https://wagerx.io/mcp).
Is the io.github.cryptoplayer/crypto-casinos MCP server safe to use?
io.github.cryptoplayer/crypto-casinos scores 86 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.cryptoplayer/crypto-casinos MCP server expose?
io.github.cryptoplayer/crypto-casinos exposes 12 tools: get_agentic_stats, find_agentic_services, check_casino, compare_casinos, latest_audits, and 7 more. Their descriptions and schemas cost roughly 1,246 tokens of context every time the server is loaded.
Does the io.github.cryptoplayer/crypto-casinos MCP server require authentication?
No. We connected to io.github.cryptoplayer/crypto-casinos without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.cryptoplayer/crypto-casinos MCP server still maintained?
io.github.cryptoplayer/crypto-casinos is still listed as active in the MCP registry. We last reached this channel on 7 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 io.github.cryptoplayer/crypto-casinos MCP server?
VerifyMCP ran 13 checks on io.github.cryptoplayer/crypto-casinos, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.