WagerX iGaming Gateway MCP MCP server

Provides AI agents with read-only access to WagerX's forensic audit data for crypto casinos, including trust scores, live test results, KYC policies, and regulatory intelligence. It enables agents to verify casino safety, compare operators, and retrieve recent audit findings without executing trades or accessing private wallets.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by WagerX

MCP endpoint (Streamable HTTP)

https://wagerx.io/mcp

Vendor documentation

What you can do with it

Check forensic audit verdict and trust score for a specific crypto casino
Compare multiple crypto casinos side-by-side on safety and payout metrics
List the most recent real-money casino audits and test results
Discover which casinos are covered in the WagerX audit database

Tools advertised by the last live check:

get_agentic_stats
find_agentic_services
check_casino
compare_casinos
latest_audits
list_casinos
top_casinos
new_casinos
long_running_casinos
best_bonuses
regulatory_intelligence
country_recommendations

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http wagerx-igaming-gateway-mcp https://wagerx.io/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add wagerx-igaming-gateway-mcp --url https://wagerx.io/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable wagerx-igaming-gateway-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "wagerx-igaming-gateway-mcp": {
      "url": "https://wagerx.io/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "wagerx-igaming-gateway-mcp": {
      "type": "streamableHttp",
      "url": "https://wagerx.io/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start wagerx-igaming-gateway-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "wagerx-igaming-gateway-mcp": {
      "type": "http",
      "url": "https://wagerx.io/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http wagerx-igaming-gateway-mcp https://wagerx.io/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "wagerx-igaming-gateway-mcp": {
      "url": "https://wagerx.io/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "wagerx-igaming-gateway-mcp": {
      "serverUrl": "https://wagerx.io/mcp"
    }
  }
}

See all 1,583

Do you run WagerX iGaming Gateway MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing