Vidofy MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Vidofy account-billed media generation: Do model availability and generated-asset costs remain attributable to the user's account before execution?

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

Best fit

Generate image, video, audio, speech and voice-cloning assets from a large hosted model catalog with cost preview.

What we know

Vidofy MCP browses the live model catalog, estimates cost, submits generation jobs, polls them and reads account balance/usage. Remote browser OAuth and local personal-token modes use the same account/coin balance.

Maintenance / activity evidence

@vidofy/mcp 0.1.2 published 2026-09-17T11:27:57.756Z

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.
Model discovery, paid generation jobs, account usage/balance reads. Writes: Submit paid generation jobs.
OAuth/personal MCP token.
Sensitive access: Creative assets, Voice/audio/image/video inputs, Account balance/token

Can spend account balance and process sensitive media; estimate cost before generation.

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

All limitations / Review context

Do model availability and generated-asset costs remain attributable to the user's account before execution?

The bounded review of the publisher's documented Vidofy account-billed media generation 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 spend account balance and process sensitive media; estimate cost before generation.
Model discovery, paid generation jobs, account usage/balance reads.
OAuth/personal MCP token.
Prompts/media inputs and outputs are processed by Vidofy/upstream model providers.
Reviewed write actions: Submit paid generation jobs
Sensitive access: Creative assets, Voice/audio/image/video inputs, Account balance/token
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.
Generation spends Vidofy coins.
Local server only accepts personal MCP token, not a differently billed API key.
Model catalog is live and large; exact counts drift.
Media prompts/uploads may be sensitive.

Original activity observations

@vidofy/mcp 0.1.2 published 2026-09-17T11:27:57.756Z

Technical identity

npm/@vidofy/mcp

Exact implementation source: https://www.npmjs.com/package/@vidofy/mcp ↗
Reviewed resource type: MCP Server
Repository identity: vidofy/mcp
Package identity: npm:@vidofy/mcp
Service endpoint: https://vidofy.ai/mcp-app

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 ↗
@vidofy/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

No third-party MCP installation, execution, connection, payment or mutation performed.
Official documentation may not prove currently operational service.
Generation consumes user coin balance.
VIDOFY_API_KEY is not a substitute for VIDOFY_TOKEN; generation can charge coins.
Targeted 2026-10-13 re-research: Publisher requires VIDOFY_TOKEN (vmt_); VIDOFY_API_KEY (vky_) is explicitly rejected. Usage consumes Vidofy coins.
Publisher requires VIDOFY_TOKEN (vmt_); VIDOFY_API_KEY (vky_) is explicitly rejected. Usage consumes Vidofy coins.
Token name and paid usage confirmed in publisher README.
Batch08 V3 source-specific finding: Media generation consumes credits; no paid smoke test.
Personal MCP token VIDOFY_TOKEN consumes coins; VIDOFY_API_KEY intentionally rejected.
Recorded publisher instruction; runtime not tested.
Client-specific example. Not interchangeable with VS Code servers or Codex TOML. No runtime test.

Install / connect
Publisher instructions
Use personal VIDOFY_TOKEN, which spends user coins; VIDOFY_API_KEY is rejected at startup.
publisher documented install or connect · Publisher instructions
npx -y @vidofy/mcp
Configure / authenticate
MCP100 setup guide
Vidofy supports remote OAuth or local VIDOFY_TOKEN (`vmt_` prefix). Generations spend Vidofy coins; VIDOFY_API_KEY is not interchangeable. Use tool discovery/read-only account status.
Environment variables referenced by this route (respect the alternatives above): VIDOFY_TOKEN
{ "mcpServers": { "vidofy": { "args": [ "-y", "@vidofy/mcp" ], "command": "npx", "env": { "VIDOFY_TOKEN": "YOUR_VIDOFY_TOKEN" } } } }
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

Vidofy MCP browses the live model catalog, estimates cost, submits generation jobs, polls them and reads account balance/usage. Remote browser OAuth and local personal-token modes use the same account/coin balance.

Capability: Design & Creative
Resource type: MCP Server
Industry: Media & Marketing, Sports & Entertainment
Best fit: Generate image, video, audio, speech and voice-cloning assets from a large hosted model catalog with cost preview.

Representative uses

List models/modes
Estimate generation cost
Generate images/video/audio/speech
Poll/result retrieval
Check account balance/usage

Limitations

Generation spends Vidofy coins.
Local server only accepts personal MCP token, not a differently billed API key.
Model catalog is live and large; exact counts drift.
Media prompts/uploads may be sensitive.

Reviewed access

Access & risk

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

Authentication: OAuth/personal MCP token.
Permissions: Model discovery, paid generation jobs, account usage/balance reads.
Data handling: Prompts/media inputs and outputs are processed by Vidofy/upstream model providers.
Cost: usage_based
Risk and cautions: Can spend account balance and process sensitive media; estimate cost before generation.

Access scope and cautions

Write actions: Submit paid generation jobs
Sensitive access: Creative assets Voice/audio/image/video inputs Account balance/token
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: List models/modes; Estimate generation cost; Generate images/video/audio/speech; Poll/result retrieval; Check account balance/usage.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @vidofy/mcp. Recorded endpoint: https://vidofy.ai/mcp-app. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: VIDOFY_TOKEN (local); VIDOFY_API_BASE (optional). No configuration values are supplied here. Prerequisites: Vidofy account. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Remote browser sign-in/OAuth or local `vmt_` personal token.

Can it modify data or perform write operations?

Documented write actions include: Submit paid generation jobs. Recorded permission boundary: Model discovery, paid generation jobs, account usage/balance reads.

What data-handling boundary should I consider?

Prompts/media inputs and outputs are processed by Vidofy/upstream model providers. Recorded sensitive-access context: Creative assets; Voice/audio/image/video inputs; Account balance/token.

What limitations and risks should I check before use?

Can spend account balance and process sensitive media; estimate cost before generation. Generation spends Vidofy coins. Local server only accepts personal MCP token, not a differently billed API key. Model catalog is live and large; exact counts drift. Media prompts/uploads may be sensitive. 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.

What cost model is recorded?

The reviewed cost model is usage based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.