Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MirrorEdge AI: Waves

NPM · WAVES-MCP · SCANNED AUG 24

Let your assistant see your recording's spectrogram, box the noise, and heal only that.

Available components

21 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency32
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the MirrorEdge AI: Waves MCP server?

MirrorEdge AI: Waves runs locally as an npm package, launched with npx -y waves-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · waves-mcp

# add to Claude Code
claude mcp add mirroredgeai-waves -- npx -y waves-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "mirroredgeai-waves": {
      "command": "npx",
      "args": [
        "-y",
        "waves-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mirroredgeai-waves": {
      "command": "npx",
      "args": [
        "-y",
        "waves-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add mirroredgeai-waves -- npx -y waves-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mirroredgeai-waves": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "waves-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mirroredgeai-waves --command npx --arg -y --arg waves-mcp
# ~/.hermes/config.yaml
mcp_servers:
  mirroredgeai-waves:
    command: "npx"
    args: ["-y", "waves-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mirroredgeai-waves": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "waves-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add mirroredgeai-waves -t stdio -c npx -a -y waves-mcp
// mcp.json
{
  "mcpServers": {
    "mirroredgeai-waves": {
      "command": "npx",
      "args": [
        "-y",
        "waves-mcp"
      ]
    }
  }
}
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.

  • 24 Aug 26 21

    First indexed and scored.

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 24 Aug 2026 · Analysed npm/waves-mcp@0.5.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Dependencies 0 packages
Packages resolved 0
Tree resolution Complete
MCP tools

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.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the MirrorEdge AI: Waves MCP server?

MirrorEdge AI: Waves is an MCP server listed in the public MCP registry as io.github.MirrorEdgeAI/waves. Let your assistant see your recording's spectrogram, box the noise, and heal only that. This page covers its npm package (waves-mcp).

Is the MirrorEdge AI: Waves MCP server safe to use?

MirrorEdge AI: Waves scores 21 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 August 2026. It declares no install or post-install scripts. 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.

Is the MirrorEdge AI: Waves MCP server still maintained?

MirrorEdge AI: Waves is still listed as active in the MCP registry. We last reached this channel on 24 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.