Wavedash docs and workflow guidance for building and publishing browser games.
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-wvdsh-wavedash": {
"args": [
"-y",
"npm"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
The canonical skill source lives in the Wavedash docs repo under skills/ and is served from https://docs.wavedash.com/.well-known/skills/index.json. This repo syncs that source into skills/ so agent platforms can install or index the published assets from GitHub.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
One local source for the MCP servers, tools, and memory your AI coding agents share, synced into each tool's native config with a review gate and a receipt for every change. No daemon, no lock-in.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
MCP Security Weekly
Get CVE alerts and security updates for io.github.wvdsh/wavedash and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
AI integration assets for Wavedash.
The canonical skill source lives in the Wavedash docs repo under skills/ and
is served from https://docs.wavedash.com/.well-known/skills/index.json.
This repo syncs that source into skills/ so agent platforms can install or
index the published assets from GitHub.
The mcp/ package contains a read-only, unauthenticated remote MCP server for
public Wavedash docs. It does not access user accounts, local files, builds, or
private Wavedash data.
Provider plugins include Wavedash skills and, where supported, bundled config for the hosted remote MCP server.
skills/ - synced canonical skills for platforms that consume skills directly.providers/claude/plugin/ - Claude Code plugin package.providers/cursor/plugin/ - Cursor plugin package.providers/openai/plugin/ - Codex plugin package.mcp/ - read-only remote MCP server for public Wavedash docs..claude-plugin/marketplace.json - Claude Code marketplace manifest..cursor-plugin/marketplace.json - Cursor marketplace manifest..agents/plugins/marketplace.json - Codex marketplace manifest.gemini-extension.json - Gemini CLI extension manifest using the root
skills/ directory.Pull from the public docs endpoint:
npm run sync:skills
Pull from a local docs checkout:
WAVEDASH_SKILLS_SOURCE_DIR=/path/to/wvdsh/docs/skills npm run sync:skills
GitHub Actions runs the same sync daily and commits changes when docs updates change the generated skill files.
The Wavedash remote MCP server is live at:
https://mcp.wavedash.com/mcp
It is read-only and unauthenticated. It exposes public Wavedash docs, SDK guidance, engine setup help, and publishing checklists for agents.
Remote MCP clients that support Streamable HTTP can connect directly to the endpoint above.
Run the docs-only MCP server locally:
cd mcp
npm install
npm start
The endpoint is http://localhost:3000/mcp.
Validate the Cloudflare Worker bundle without publishing:
npm run mcp:deploy:dry-run
Deploy the MCP Worker from an environment that provides Cloudflare credentials:
npm run mcp:deploy
MIT