io.github.cryptoplayer/crypto-casinos
REMOTE · WAGERX.IO · SCANNED AUG 20
Real-money crypto casino audits: trust scores, live tests, rankings, new casinos, bonuses. Signed.
Available components
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 789 tokens (~112/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · wagerx.io
claude mcp add --transport http cryptoplayer-crypto-casinos https://wagerx.io/mcp
[mcp_servers.cryptoplayer-crypto-casinos] url = "https://wagerx.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cryptoplayer-crypto-casinos": {
"type": "remote",
"url": "https://wagerx.io/mcp",
"enabled": true
}
}
} openclaw mcp add cryptoplayer-crypto-casinos --url https://wagerx.io/mcp --transport streamable-http
mcp_servers:
cryptoplayer-crypto-casinos:
url: "https://wagerx.io/mcp" {
"mcpServers": {
"cryptoplayer-crypto-casinos": {
"type": "http",
"url": "https://wagerx.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Aug 26 0
- Tool “best_bonuses” rewrote its description, which is the text the model reads security
- Tool “check_casino” rewrote its description, which is the text the model reads security
- Tool “compare_casinos” rewrote its description, which is the text the model reads security
- Tool “latest_audits” rewrote its description, which is the text the model reads security
- Tool “list_casinos” rewrote its description, which is the text the model reads security
- Tool “new_casinos” rewrote its description, which is the text the model reads security
- Tool “top_casinos” rewrote its description, which is the text the model reads security
- Schema quality: 64 → 112 ▼ functional
- “check_casino” reworded the description of “name” cosmetic
- 18 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Aug 26 62
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 20 Aug 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=YE2,O=Let's Encrypt,C=US | 14 Jul 2026 | 12 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5728dff3ef7c8a39fc391caa4b37ad7b32b |
| SANs: wagerx.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 |
DNSSEC insecure
Validation of wagerx.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| wagerx.io. | 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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
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.
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 ~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 ~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.
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 ~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.
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.
top_casinos ~97
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 casino", "top crypto gambling site". Example call: {"limit": 10}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.