Wavedash
REMOTE · MCP.WAVEDASH.COM
Wavedash docs and workflow guidance for building and publishing browser games.
Available components
Last scanned (10 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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 Usability81
- 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
- Context-footprint check failed: tool/resource definitions use about 864 tokens (~172/item across 5 items; 4 tools + 1 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 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 28 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_wavedash_docs” rewrote its description, which is the text the model reads security
- 23 Oct 26 +12
- Stability: fail → pass ▲ 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
- 23 Sept 26 0
- Stability: pass → fail ▼ security
- Tool “wavedash_get_agent_workflow” was removed ▼ security
- Tool “wavedash_get_doc” was removed ▼ security
- Tool “wavedash_get_publishing_checklist” was removed ▼ security
- Tool “wavedash_get_quickstart” was removed ▼ security
- Tool “wavedash_get_sdk_reference” was removed ▼ security
- Tool “wavedash_search_docs” was removed ▼ security
- Tool “wavedash_validate_config” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “wavedash_implementation_planner” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Server version: 0.1.0 → 0.2.0 functional
- New tool “get_wavedash_doc” functional
- New tool “search_wavedash_docs” functional
- New tool “validate_wavedash_config” functional
- “wavedash_implementation_planner” added an optional parameter “stage” cosmetic
- “wavedash_implementation_planner” reworded the description of “engine” cosmetic
- “wavedash_implementation_planner” reworded the description of “features” cosmetic
- “wavedash_implementation_planner” reworded the description of “goal” cosmetic
- 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 0
- 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
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 5 Nov 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 | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 13a0c66e6721c1ec0e3c7269f86b22b2 |
| 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 →
get_wavedash_doc Get Wavedash Doc ~126
Fetch a full Wavedash docs page as Markdown by path or docs.wavedash.com URL, for example sdk/achievements, engines/unity, or cli/configuration. Use this when the user wants to see a Wavedash docs page or when exact SDK, CLI, or config details are needed. Only docs.wavedash.com pages can be fetched. 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 |
|---|---|---|---|
| slug | string | yes | – |
| text | string | yes | Page URL followed by the Markdown content. |
| url | string | yes | – |
No examples provided.
search_wavedash_docs Search Wavedash Docs ~113
Search official Wavedash docs (docs.wavedash.com) for browser game development, SDK integration, engines, CLI, upload, and publishing. Use this for any Wavedash question when the exact page is unknown. Returns ranked pages with paths, URLs, and excerpts. 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 |
|---|---|---|---|
| results | array | yes | – |
| text | string | yes | Human-readable results. |
No examples provided.
validate_wavedash_config Validate Wavedash Config ~111
Validate wavedash.toml contents for Wavedash CLI config issues (missing game_id or upload_dir, entrypoint repeating the upload_dir, absolute paths, engine sections). Call this whenever the user shares wavedash.toml text or asks to check their Wavedash config, even if the problem looks obvious. Accepts single-line or fenced input. Pass the config text as the toml argument; this does not read files.
| Name | Type | Req | Description |
|---|---|---|---|
| toml | string | yes | Contents of wavedash.toml. |
| Name | Type | Req | Description |
|---|---|---|---|
| issues | array | yes | – |
| ok | boolean | yes | – |
| text | string | yes | Human-readable validation report. |
| warnings | array | yes | – |
No examples provided.
wavedash_implementation_planner Plan Wavedash Implementation ~278
Plan and guide a Wavedash browser game integration from the user's goal, engine, and requested features. Call this first for any request to build, deploy, upload, or release a game on Wavedash, or to add Wavedash SDK features. Choose the stage: plan (architecture and reading order), setup (CLI install, sign-in, SDK init, wavedash.toml, local testing), features (SDK reference for the requested features), or deploy (upload and release checklist). Returns ordered steps, boundaries, and the relevant docs.wavedash.com pages with content. Read-only and unauthenticated.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | Optional engine or framework as the user names it, for example Phaser, Unity WebGL, Godot 4, three.js, React, Rust, or custom. |
| features | array | – | Optional requested Wavedash features, for example multiplayer, leaderboards, achievements, cloud saves, ugc, players, paid content. |
| goal | string | yes | What the user wants to build, deploy, or integrate, including the game type and the Wavedash outcome. |
| stage | string | – | plan: architecture and reading order. setup: CLI, SDK init, config, local testing. features: SDK reference for the requested features. deploy: upload and release checklist. |
| Name | Type | Req | Description |
|---|---|---|---|
| boundaries | array | yes | What this MCP and Wavedash do not do. |
| docs | array | yes | Docs pages to read for this stage. |
| engine | – | yes | – |
| features | array | yes | – |
| goal | string | yes | – |
| next_tools | array | yes | Recommended follow-up tool calls. |
| stage | string | yes | – |
| steps | array | yes | Ordered implementation steps for this stage. |
| text | string | yes | Human-readable plan. |
No examples provided.
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'
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 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 Wavedash MCP server expose?
Wavedash exposes 4 tools: wavedash_implementation_planner, search_wavedash_docs, get_wavedash_doc, validate_wavedash_config. Their descriptions and schemas cost roughly 628 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.