Wavedash

REMOTE · MCP.WAVEDASH.COM · SCANNED AUG 3

Wavedash docs and workflow guidance for building and publishing browser games.

Available components

+6 this week 76 76 Trust /100

Trust breakdown (6 categories)

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 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 Usability85

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 Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

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 · mcp.wavedash.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http wvdsh-wavedash https://mcp.wavedash.com/mcp

# ~/.codex/config.toml

[mcp_servers.wvdsh-wavedash]
url = "https://mcp.wavedash.com/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wvdsh-wavedash": {
      "type": "remote",
      "url": "https://mcp.wavedash.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add wvdsh-wavedash --url https://mcp.wavedash.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  wvdsh-wavedash:
    url: "https://mcp.wavedash.com/mcp"

// mcp.json

{
  "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.

Changelog

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.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +2
- 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
29 Jul 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.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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 70

First indexed and scored.

Show 7 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 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	29 Jun 2026	27 Sept 2026	ECDSA 256	ECDSA-SHA256	1eb2c3286325b1da138bbe9d8ac6dbb0
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

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

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

MCP tools — 8 exposed · ~733 tokens

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.

Tool Tokens

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	70
27 Jul	70
28 Jul	71
29 Jul	72
30 Jul	72
31 Jul	74
1 Aug	75
2 Aug	75
3 Aug	76