WaveSpeed MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to WaveSpeed live-model execution, schema discovery and price quotes: Do explicit file-upload markers and unpriced-input disclosure remain correct as the live model catalog changes?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Agent-driven image, video, audio and 3D generation with schema discovery and cost checks.

What we know

WaveSpeed adapter for live model discovery, schema validation, price estimates, local-file upload and multimodal prediction execution.

Maintenance / activity evidence

@wavespeed/mcp 1.0.8 published 2026-10-01T10:45:05.222Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Catalog/balance reads, file upload and generation submission. Writes: Upload local files; Submit generation jobs consuming credits.
WaveSpeed API key or stored CLI credential.
Sensitive access: Private media, Prompts, Generated outputs, API key

Can upload local content and spend credits; inspect schema and price before execution.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do explicit file-upload markers and unpriced-input disclosure remain correct as the live model catalog changes?

The bounded review of the publisher's documented WaveSpeed live-model execution, schema discovery and price quotes and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Can upload local content and spend credits; inspect schema and price before execution.
Catalog/balance reads, file upload and generation submission.
WaveSpeed API key or stored CLI credential.
Files marked with `@path`, prompts and outputs are sent to WaveSpeed.
Reviewed write actions: Upload local files; Submit generation jobs consuming credits
Sensitive access: Private media, Prompts, Generated outputs, API key
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
privacy/retention of uploads/outputs
live catalog/pricing
Jobs can take minutes/hours.
Catalog and input schemas are live.
Price estimates may be incomplete for some parameters.
Hosted input/output retention was not established.

Original activity observations

@wavespeed/mcp 1.0.8 published 2026-10-01T10:45:05.222Z

Technical identity

npm/@wavespeed/mcp

Exact implementation source: https://www.npmjs.com/package/@wavespeed/mcp ↗
Reviewed resource type: MCP Server
Repository identity: WaveSpeedAI/mcp-server
Package identity: npm:@wavespeed/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@wavespeed/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
wavespeedai/mcp-server
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.
Evidence source ↗
wavespeed.ai/
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
API key or saved CLI login via wavespeed login.
publisher documented install or connect · Publisher instructions
claude mcp add wavespeed -- npx -y @wavespeed/mcp
Configure / authenticate
MCP100 setup guide
WAVESPEED_API_KEY or shared WaveSpeed CLI login may authenticate. Do not create billed media merely to test MCP setup.
WAVESPEED_API_KEY OR stored wavespeed CLI login.
Environment variables referenced by this route (respect the alternatives above): WAVESPEED_API_KEY (unless wavespeed CLI login already exists)
Check connection
Suggested check
User-side suggested check (not executed): inspect registered tools/connection and perform publisher-supported read-only status/list operations. Do not send, purchase, publish, delete, sign, trade or alter data as a smoke test.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
Remove local stored keys/tokens and revoke or rotate corresponding provider authorization using documented provider account controls if available; exact procedure not verified for this package. Wallet private keys cannot be revoked.

Official Documentation & Sources

What it does

WaveSpeed adapter for live model discovery, schema validation, price estimates, local-file upload and multimodal prediction execution.

Capability: Design & Creative
Resource type: MCP Server
Industry: Media & Marketing, Sports & Entertainment
Best fit: Agent-driven image, video, audio and 3D generation with schema discovery and cost checks.

Representative uses

Search model catalog
Inspect model schemas
Quote generation cost
Run image/video/audio/3D jobs
Upload local files and poll long-running predictions

Limitations

Jobs can take minutes/hours.
Catalog and input schemas are live.
Price estimates may be incomplete for some parameters.
Hosted input/output retention was not established.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: WaveSpeed API key or stored CLI credential.
Permissions: Catalog/balance reads, file upload and generation submission.
Data handling: Files marked with `@path`, prompts and outputs are sent to WaveSpeed.
Cost: usage_based
Risk and cautions: Can upload local content and spend credits; inspect schema and price before execution.

Access scope and cautions

Write actions: Upload local files Submit generation jobs consuming credits
Sensitive access: Private media Prompts Generated outputs API key
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Search model catalog; Inspect model schemas; Quote generation cost; Run image/video/audio/3D jobs; Upload local files and poll long-running predictions.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @wavespeed/mcp. Recorded transport: stdio. Recorded environment-variable notes: WAVESPEED_API_KEY (optional if CLI login exists). No configuration values are supplied here. Prerequisites: Node/npm; WaveSpeed account/credits. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: API key or stored WaveSpeed CLI login.

Can it modify data or perform write operations?

Documented write actions include: Upload local files; Submit generation jobs consuming credits. Recorded permission boundary: Catalog/balance reads, file upload and generation submission.

What data-handling boundary should I consider?

Files marked with `@path`, prompts and outputs are sent to WaveSpeed. Recorded sensitive-access context: Private media; Prompts; Generated outputs; API key.

What limitations and risks should I check before use?

Can upload local content and spend credits; inspect schema and price before execution. Jobs can take minutes/hours. Catalog and input schemas are live. Price estimates may be incomplete for some parameters. Hosted input/output retention was not established. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

WaveSpeed AI is listed as First-party MCP in MCP100’s current evidence.