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.

io.github.vicseeai/vicsee-mcp-server

NPM · @VICSEE/MCP-SERVER · 2 COMPONENTS · SCANNED SEP 20

Generate, edit and upscale AI video and images from any agent via VicSee.

0 this week 82 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1165 tokens (~166/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.vicseeai/vicsee-mcp-server server?

io.github.vicseeai/vicsee-mcp-server runs locally as an npm package, launched with npx -y @vicsee/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @vicsee/mcp-server

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

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 −2
    • Stability: pass → 0.83 functional
  • 10 Sept 26 0
    • Stability: 0.97 → pass security
  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

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 20 Sept 2026 · Analysed npm/@vicsee/mcp-server@0.3.3

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 97 packages
Packages resolved 97
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~1,165 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
vicsee_generate ~694

Create an AI image or video with VicSee. Generation is ASYNCHRONOUS: this returns a task `id` immediately, then poll `vicsee_get_task` with that id until status is "completed" (the result URL appears in result.url) or "failed". Use vicsee_list_models to pick a `model` and see its valid options. For image-to-video / image-to-image, pass source images in `image_urls`. For reference-to-video models (e.g. "seedance-2-0-reference-to-video"), pass references in reference_image_urls / reference_video_urls / reference_audio_urls and refer to them positionally in the prompt as @Image1, @Image2, … IMAGE inputs (image_urls, reference_image_urls) may be a public https URL, a local file path (this server reads and base64-encodes it for you), or a base64 data URI. VIDEO/AUDIO inputs (reference_video_urls, reference_audio_urls) must be public https URLs. For video-edit models (e.g. "happyhorse-video-edit"), pass the source clip in video_url and optionally set audio_setting ("auto" or "origin").

NameTypeReqDescription
aspect_ratiostringe.g. "16:9", "9:16", "1:1", "landscape", "portrait"
audiobooleanEnable native audio (supported video models)
audio_settingstringVideo-edit models only: "auto" (regenerate audio) or "origin" (keep the source audio).
durationnumberVideo length in seconds (e.g. 5, 6, 10, 15) — video models only
extraobjectAny additional model-specific params (see the model's options from vicsee_list_models)
image_urlsarraySource image(s) for image-to-video / image-to-image. Each may be a public https URL, a local file path (this server reads and base64-encodes it for you), or a base64 data URI.
modelstringyesModel id from vicsee_list_models, e.g. "nano-banana-pro-text-to-image" or "seedance-2-0-text-to-video"
output_formatstringImage output format, e.g. "png" or "jpeg"
promptstringText prompt (required for most models)
reference_audio_urlsarrayReference-to-video only: up to 3 public https audio URLs.
reference_image_urlsarrayReference-to-video only: up to 7 reference images. Each may be a public https URL, a local file path (this server reads and base64-encodes it for you), or a base64 data URI. Refer to them in the prom…
reference_video_urlsarrayReference-to-video only: up to 3 public https video URLs (2-15s each, ≤15s total).
resolutionstringe.g. "1K", "2K", "4K", "720P", "1080P"
video_urlstringVideo-edit models (e.g. "happyhorse-video-edit") only: one public https video URL, 3-15s, to edit.

No output schema declared.

No examples provided.

vicsee_get_credits ~24

Get the current VicSee credit balance for the configured API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

vicsee_get_task ~105

Poll a generation or upscale task by its id. status is one of "pending" | "processing" | "queued" | "completed" | "failed". When "completed", the media URL is in result.url (videos/images) or result.songs (music). When "failed", details are in error. Poll every few seconds until completed or failed.

NameTypeReqDescription
task_idstringyesThe task id returned by vicsee_generate / vicsee_upscale_*

No output schema declared.

No examples provided.

vicsee_list_models ~55

List available VicSee models with their capabilities and credit costs. Call this first to find a model id to pass to vicsee_generate. Optionally filter by media type.

NameTypeReqDescription
typestringFilter by media type

No output schema declared.

No examples provided.

vicsee_upload ~130

Upload a LOCAL file (image, video, or audio) from this machine and get back a public https URL. Use the returned url as an input for vicsee_generate — e.g. drop it into reference_image_urls for a reference-to-video storyboard, or image_urls for image-to-video. PREFER this over inline base64 for references: large base64 strings get truncated in tool-call output and the model rejects them. The file uploads directly to storage; only its public URL comes back.

NameTypeReqDescription
file_pathstringyesAbsolute path to a local file (image/video/audio) on this machine.

No output schema declared.

No examples provided.

vicsee_upscale_image ~75

Upscale a publicly accessible image (JPEG/PNG/WebP). Asynchronous: returns a task id — poll vicsee_get_task until completed. upscale_factor defaults to "2".

NameTypeReqDescription
image_urlstringyesPublicly accessible image URL
upscale_factorstringUpscale factor (default "2")

No output schema declared.

No examples provided.

vicsee_upscale_video ~82

Upscale a publicly accessible video (MP4/MOV/MKV, up to 60s). Asynchronous: returns a task id — poll vicsee_get_task until completed. upscale_factor defaults to "2".

NameTypeReqDescription
upscale_factorstringUpscale factor (default "2")
video_urlstringyesPublicly accessible video URL

No output schema declared.

No examples provided.

Common questions

What is the io.github.vicseeai/vicsee-mcp-server server?

io.github.vicseeai/vicsee-mcp-server is listed in the public MCP registry as io.github.vicseeai/vicsee-mcp-server. Generate, edit and upscale AI video and images from any agent via VicSee. This page covers its npm package (@vicsee/mcp-server).

Is the io.github.vicseeai/vicsee-mcp-server server safe to use?

io.github.vicseeai/vicsee-mcp-server scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.

What tools does the io.github.vicseeai/vicsee-mcp-server server expose?

io.github.vicseeai/vicsee-mcp-server exposes 7 tools: vicsee_list_models, vicsee_generate, vicsee_get_task, vicsee_upscale_image, vicsee_upscale_video, and 2 more. Their descriptions and schemas cost roughly 1,165 tokens of context every time the server is loaded.

Is the io.github.vicseeai/vicsee-mcp-server server still maintained?

io.github.vicseeai/vicsee-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.vicseeai/vicsee-mcp-server server under?

io.github.vicseeai/vicsee-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.