BizMuse MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to BizMuse asynchronous music-video workflow: Do job status and artifact results remain attributable across portable bundle and stdio releases?

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

Best fit

Create AI-generated music videos from music and reference imagery.

What we know

Create complete AI music videos from audio and reference images with the official BizMuse server. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Maintenance / activity evidence

bizmuse-mcp 0.1.6 published 2026-07-20T13:42:58.182Z

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Permissions not yet verified. Writes: Generate hosted media jobs (per source description).
Authentication not yet verified.
Sensitive access: Source audio, Reference images

Potential high-impact side effects: Generate hosted media jobs (per source description).

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

All limitations / Review context

Do job status and artifact results remain attributable across portable bundle and stdio releases?

The bounded review of the publisher's documented BizMuse asynchronous music-video workflow 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.

Potential high-impact side effects: Generate hosted media jobs (per source description).
Reviewed write actions: Generate hosted media jobs (per source description)
Sensitive access: Source audio, Reference images
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.
repositoryIdentity: no confirmed package-to-repository binding
authentication: exact official auth and credential handling
dataHandling: provider destinations, retention and egress
cost: plans, pay-per-call charges, and payment authorization details
Rendering provider, cost, media retention and rights are unverified
Treat generation as a write/spend operation, not a read-only integration

Original activity observations

bizmuse-mcp 0.1.6 published 2026-07-20T13:42:58.182Z

Technical identity

npm/bizmuse-mcp

Exact implementation source: https://www.npmjs.com/package/bizmuse-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:bizmuse-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 ↗
bizmuse-mcp
Recorded package identity, distribution or download evidence.
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.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Tools list without key but API actions require BIZMUSE_API_KEY; never label keyless tool listing authenticated
Credentials optional for tool enumeration only, but actual BizMuse API operations require BIZMUSE_API_KEY.
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Tools list without key but API actions require BIZMUSE_API_KEY; never label keyless tool listing authenticated | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Publisher instructions
npx -y bizmuse-mcp
Configure / authenticate
MCP100 setup guide
Publisher-documented connection/installation path shown under install.commands. Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim. Tools list without key but API actions require BIZMUSE_API_KEY; never label keyless tool listing authenticated Verify the correct host/transport from the publisher README; secure credentials in local client settings.
Required environment variables: BIZMUSE_API_KEY
Check connection
Suggested check
Check that the registered MCP tools are discoverable in the client; run only publisher-described read-only status/health tools if provided. No runtime verification was performed.
Remove / uninstall / revoke
MCP100 setup guide
If your Claude Code MCP registration is named `bizmuse-mcp`, run the client removal command. For Claude Desktop/Cursor/Codex or another registered name, remove the matching entry in that host’s MCP settings. Hosted OAuth disconnect and stopping a self-hosted process are separate; npx has no permanent global package install.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove bizmuse-mcp

Official Documentation & Sources

What it does

Create complete AI music videos from audio and reference images with the official BizMuse server. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Capability: Design & Creative
Resource type: MCP Server
Industry: Sports & Entertainment
Best fit: Create AI-generated music videos from music and reference imagery.

Representative uses

Submit an audio-based music-video project
Use reference visuals in generation
Retrieve completed media

Limitations

Rendering provider, cost, media retention and rights are unverified
Treat generation as a write/spend operation, not a read-only integration

Reviewed access

Access & risk

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

Authentication: Not documented in the reviewed sources
Permissions: Not documented in the reviewed sources
Data handling: Not documented in the reviewed sources
Cost: Not documented in the reviewed sources
Risk and cautions: Potential high-impact side effects: Generate hosted media jobs (per source description).

Access scope and cautions

Write actions: Generate hosted media jobs (per source description)
Sensitive access: Source audio Reference images
Risk level: moderate

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: Submit an audio-based music-video project; Use reference visuals in generation; Retrieve completed media.

Can it modify data or perform write operations?

Documented write actions include: Generate hosted media jobs (per source description).

What data-handling boundary should I consider?

Recorded sensitive-access context: Source audio; Reference images.

What limitations and risks should I check before use?

Potential high-impact side effects: Generate hosted media jobs (per source description). Rendering provider, cost, media retention and rights are unverified. Treat generation as a write/spend operation, not a read-only integration. 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.