WaveSpeed MCP (official)
Capped at 70: no passing tool call yet; the tests add up to 100. Why scores are capped
Test points add up to 100; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology
Test points before the cap (100/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested npm @wavespeed/mcp 1.2.5 (repo WaveSpeedAI/mcp-server). Its 16 tools listed without credentials, but every tool needs a WaveSpeed API key: list_models and get_balance both returned 'No WaveSpeed API key configured. Set WAVESPEED_API_KEY, or run `wavespeed login`.' (live endpoint probe, Nov 2, 2026). No generation, upload or billing tool was called. WaveSpeed's hosted endpoint https://api.wavespeed.ai/mcp answered HTTP 401 with an OAuth challenge and is not listed separately. Score capped: no passing tool call.
Transport (tested 2026-11-02): stdio
Score 70/100 · Tools 16 · Token cost ~4,598 · Compare · Last tested 2026-11-02 · Version tested 1.2.5 · Package @wavespeed/mcp · Repo WaveSpeedAI/mcp-server
Summary: WaveSpeed MCP (official) completed an MCP handshake without credentials and exposed 16 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 16
- Context cost
- 4,598 model-visible tokens (name, description, inputSchema; tiktoken cl100k_base)
Extra payload (sent by the server, usually not read by the model): 960 tokens; raw tools/list total 5,558. Clients differ in what they forward. ranking · add up your servers' context cost - API key
- Needs a key
- Tested
- 2026-11-02
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install @wavespeed/mcp (Node 20, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 16 tools listed in 0.1s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 36 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Automated check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Schema context cost: ~4,598 tokens for 16 tools (18,247 bytes) · about 56% of an 8k context. Method: tiktoken cl100k_base over compact JSON of name+description+inputSchema (approximate).
Small-model friendly (schema heuristic, not a model result): unknown.
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-02
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 16 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Tool-schema token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that it is safe to give it access to your data.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-02 test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
8eda2ddb8043: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "@wavespeed/mcp",
"version": "1.2.5",
"registry": "npm",
"status": "working",
"tested": "2026-11-02",
"tools_count": 16,
"tools_schema_tokens_est": 4598,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install @wavespeed/mcp` (Node 20, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 16 tools listed in 0.1s."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 36 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Automated check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
}
}Install
npx -y @wavespeed/mcp
Tools listed
list_models, get_model_schema, run_model, generate_image, edit_image, generate_video, edit_video, extend_video, get_price, get_balance, list_predictions, list_billings, get_usage, delete_predictions, upload_file, get_prediction
Quick config
{
"mcpServers": {
"wavespeed-mcp": {
"command": "npx",
"args": [
"-y",
"@wavespeed/mcp"
],
"env": {
"WAVESPEED_API_KEY": "<your key>"
}
}
}
}API key: set WAVESPEED_API_KEY in env (replace <your key>). Our handshake ran without it; real use needs it.
Add to config Opens the config generator with this server selected.
Setup
Env var seen in our test: WAVESPEED_API_KEY
- Install. Run
npm install @wavespeed/mcp(Node 20). This is the exact command we ran on 2026-11-02. - Configure. Add the mcpServers entry below to your MCP client config and set WAVESPEED_API_KEY.
- Verify. Restart the client and check that tools/list returns tools (16 in our test).
{
"mcpServers": {
"wavespeed-mcp": {
"command": "npx",
"args": [
"-y",
"@wavespeed/mcp"
],
"env": {
"WAVESPEED_API_KEY": "<your key>"
}
}
}
}Test history
No dated events yet.
FAQ
Is WaveSpeed MCP (official) deprecated?
No. @wavespeed/mcp was not deprecated or archived when we last tested it on 2026-11-02.
What replaces WaveSpeed MCP (official)?
Nothing; WaveSpeed MCP (official) is not deprecated as of 2026-11-02.
Does WaveSpeed MCP (official) need an API key?
The handshake works without a key; real use needs WAVESPEED_API_KEY.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.