Wavedash
REMOTE · MCP.WAVEDASH.COM · SCANNED SEP 21
Wavedash docs and workflow guidance for building and publishing browser games.
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 → Why this is hard to score →
Endpoint Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability90
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 749 tokens (~83/item across 9 items; 8 tools + 1 resources), lean.Pass
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
How do I install the Wavedash MCP server?
Wavedash is a hosted endpoint at https://mcp.wavedash.com/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 · mcp.wavedash.com
claude mcp add --transport http wvdsh-wavedash 'https://mcp.wavedash.com/mcp'
{
"mcpServers": {
"wvdsh-wavedash": {
"url": "https://mcp.wavedash.com/mcp"
}
}
} {
"servers": {
"wvdsh-wavedash": {
"type": "http",
"url": "https://mcp.wavedash.com/mcp"
}
}
} [mcp_servers.wvdsh-wavedash] url = "https://mcp.wavedash.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wvdsh-wavedash": {
"type": "remote",
"url": "https://mcp.wavedash.com/mcp",
"enabled": true
}
}
} openclaw mcp add wvdsh-wavedash --url 'https://mcp.wavedash.com/mcp' --transport streamable-http
mcp_servers:
wvdsh-wavedash:
url: "https://mcp.wavedash.com/mcp" {
"McpServers": {
"wvdsh-wavedash": {
"Transport": "http",
"Url": "https://mcp.wavedash.com/mcp"
}
}
} assistant mcp add wvdsh-wavedash -t streamable-http -u 'https://mcp.wavedash.com/mcp'
{
"mcpServers": {
"wvdsh-wavedash": {
"type": "http",
"url": "https://mcp.wavedash.com/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.
- 26 Aug 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 Aug 26 +1
- Stability: 0.97 → pass security
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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
- 27 Jul 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
- 26 Jul 26 0
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 21 Sept 2026 · Probed https://mcp.wavedash.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wavedash.com | CN=WE1,O=Google Trust Services,C=US | 27 Aug 2026 | 25 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | c86dce9335c4e4a213efa63ebd6b006e |
| SANs: wavedash.com, mcp.wavedash.com, *.mcp.wavedash.com | ||||||
| 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 mcp.wavedash.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| wavedash.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.wavedash.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.wavedash.com/mcp | HTTPS enforced | 301 | https://mcp.wavedash.com/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 →
wavedash_get_agent_workflow Get Wavedash Agent Workflow ~118
Return a concise end-to-end workflow for AI agents creating a browser game from scratch and preparing it for Wavedash upload. Read-only and unauthenticated; upload still happens through the Wavedash CLI or Developer Portal.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | Optional engine/framework, for example javascript, phaser, unity, godot, three.js, react, or custom. |
| features | array | – | Optional requested Wavedash features, for example multiplayer, achievements, leaderboards, cloud-saves, ugc, players. |
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Human-readable tool result text. |
No examples provided.
wavedash_get_doc Get Wavedash Doc ~71
Fetch a full Wavedash docs page as Markdown by path or docs.wavedash.com URL. Read-only and unauthenticated.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Docs path or URL, for example sdk/setup, engines/phaser, publishing/upload, or https://docs.wavedash.com/sdk/setup. |
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Human-readable tool result text. |
No examples provided.
wavedash_get_publishing_checklist Get Wavedash Publishing Checklist ~68
Return Wavedash upload and publishing checklist guidance, optionally including an engine-specific docs page. Read-only and unauthenticated.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | Optional engine/framework, for example unity, godot, phaser, three.js, react, rust, or custom. |
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Human-readable tool result text. |
No examples provided.
wavedash_get_quickstart Get Wavedash Quickstart ~99
Return the Wavedash setup path for a browser game, optionally including an engine and SDK features. Read-only and unauthenticated.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | Optional engine/framework, for example phaser, unity, godot, three.js, react, rust, or custom. |
| features | array | – | Optional Wavedash features, for example multiplayer, achievements, leaderboards, cloud-saves, ugc, players. |
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Human-readable tool result text. |
No examples provided.
wavedash_get_sdk_reference Get Wavedash SDK Reference ~94
Fetch Wavedash SDK docs for a specific feature such as setup, multiplayer, achievements, leaderboards, cloud saves, UGC, players, events, or types. Read-only and unauthenticated.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | SDK topic, for example setup, multiplayer, lobbies, p2p, achievements, stats, leaderboards, cloud-saves, ugc, players, cli, config. |
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Human-readable tool result text. |
No examples provided.
wavedash_implementation_planner Plan Wavedash Implementation ~151
Plan a Wavedash game implementation from the user's goal, engine, and requested features. Use this before making architecture claims, selecting SDK features, or writing Wavedash integration code. Read-only and unauthenticated.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | Optional engine/framework, for example phaser, unity, godot, three.js, react, rust, or custom. |
| features | array | – | Optional requested Wavedash features, for example multiplayer, achievements, leaderboards, cloud-saves, ugc, players, paid-content, upload, or publishing. |
| goal | string | yes | What the user wants to build or integrate, including the game type and Wavedash-related outcome. |
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Human-readable tool result text. |
No examples provided.
wavedash_search_docs Search Wavedash Docs ~79
Search official Wavedash docs for browser game development, SDK integration, engines, CLI, upload, and publishing. Read-only and unauthenticated.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results to return. |
| query | string | yes | Search query, for example: sdk setup, multiplayer lobbies, unity webgl, build push. |
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Human-readable tool result text. |
No examples provided.
wavedash_validate_config Validate Wavedash Config ~53
Validate pasted wavedash.toml text for basic Wavedash CLI config issues. This does not read files; provide the config text as input.
| Name | Type | Req | Description |
|---|---|---|---|
| toml | string | yes | Contents of wavedash.toml. |
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Human-readable tool result text. |
No examples provided.
What is the Wavedash MCP server?
Wavedash is an MCP server listed in the public MCP registry as io.github.wvdsh/wavedash. Wavedash docs and workflow guidance for building and publishing browser games. This page covers its hosted endpoint (https://mcp.wavedash.com/mcp).
Is the Wavedash MCP server safe to use?
Wavedash scores 88 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 Wavedash MCP server expose?
Wavedash exposes 8 tools: wavedash_implementation_planner, wavedash_get_agent_workflow, wavedash_search_docs, wavedash_get_doc, wavedash_get_quickstart, and 3 more. Their descriptions and schemas cost roughly 733 tokens of context every time the server is loaded.
Does the Wavedash MCP server require authentication?
No. We connected to Wavedash without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Wavedash MCP server still maintained?
Wavedash is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.