Whale.io Casino MCP

Whale.io · Casinos

Officialoffline

Whale.io now displays in-product instructions for connecting Claude Code, OpenAI Codex CLI and OpenClaw to its published casino MCP URL. Whale describes the connection as a way for an AI assistant to play games. WagerX separately completed a real-money casino test, but has not verified the MCP tool inventory or financial permissions: the published route returned HTTP 404 to GET and MCP initialize requests on August 21, 2026.

Evidence & discovery

This profile records public discovery and WagerX observations. It does not establish legality, security, availability or correctness of provider claims.

GitHubprovider campaign repo↗Provider announcementprovider-supplied launch claim↗

Provider documentation ↗

Separate casino testing track

Dated casino testing evidence

This is the current WagerX live-testing record for the exact Whale.io casino review entity. It is separate from MCP discovery and endpoint status.

Test date: August 21, 2026
Deposit observed: 0.9 ETH
Withdrawal amount observed: 1.2 ETH
Withdrawal time observed: Instant
KYC observed: None

Raw withdrawal result: 1.2 ETH — Instant

KYC scope: This is what WagerX observed during this test only; it is not an operator-wide promise about future withdrawals or other accounts.

Concerns recorded with this test

Team communication has been difficult and remains under monitoring.

Independence: A successful withdrawal does not verify the MCP endpoint, tools, authorization or permissions. A working MCP does not guarantee casino safety, lawful operation, payout reliability or suitability.

Live Testing Notes → Whale.io casino review →

Append-only observations

Protocol observation history

Routine checks collect metadata only: protocol initialization and declared capabilities. Separately authorized read-only tests, where published, are recorded below with their exact inputs and limits.

August 26, 2026 · 12:24 UTCMCP · manual

http errorEndpoint returned HTTP 404 before inspection completed.https://api.playwhale.io/mcp

HTTP 404 · 1620 ms

August 21, 2026 · 12:00 UTCMCP · legacy import

legacy snapshotLegacy editorial snapshot; detailed protocol telemetry was not retained.https://api.playwhale.io/mcp

Published baseline

Test results

Separate from protocol observation history. Results record the dated inputs, returned response and stated limits of an authorized read-only test.

Download JSON

original-protocol

mcp · https://api.playwhale.io/mcp

Inspection did not complete

Checked: 2026-09-10T14:36:40.599699+00:00
Test input: Initialize an MCP session and list the available tools.
Curated response: The published route returned HTTP 404 before MCP inspection completed.
Limit: One point-in-time metadata inspection.
Contract hash
Response hash

Evidence source

original-task

mcp · https://api.playwhale.io/mcp

No task call

Checked: 2026-09-10T14:40:09.258142+00:00
Test input: No tool call; protocol inspection did not complete.
Curated response: No application result was obtained.
Limit: This preserves the attempted follow-up without treating it as an executed tool call.
Contract hash
Response hash

Evidence source

supplemental-transport

http · https://api.playwhale.io/mcp

Route not found

Checked: 2026-09-10T14:40:21.882864+00:00
Test input: Inspect response status and content type with a bounded GET.
Curated response: A bounded GET returned HTTP 404.
Limit: This transport observation was not an MCP tool call.
Contract hash
Response hash

Evidence source

Method & limitations

The published remote route did not complete MCP inspection in this snapshot.

Suggest a correction or request a retest