# openmode (npm · openmode)

Video editing and rendering for coding agents: look at footage, render edits to MP4, keep versions.

- Trust score: 72/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- npm · `openmode`: 72/100 (this document), [markdown](https://verifymcp.io/servers/shansabnani-openmode/openmode.md), [page](https://verifymcp.io/servers/shansabnani-openmode/openmode)

## Channel facts

- Registry: `npm`
- Package: `openmode`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1437 tokens (~205/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 97% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the openmode MCP server?

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

### Claude

```bash
claude mcp add shansabnani-openmode -- npx -y openmode mcp
```

### Cursor

```json
{
  "mcpServers": {
    "shansabnani-openmode": {
      "command": "npx",
      "args": [
        "-y",
        "openmode",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "shansabnani-openmode": {
      "command": "npx",
      "args": [
        "-y",
        "openmode",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add shansabnani-openmode -- npx -y openmode mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shansabnani-openmode": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "openmode",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add shansabnani-openmode --command npx --arg -y --arg openmode --arg mcp
```

### Hermes

```yaml
mcp_servers:
  shansabnani-openmode:
    command: "npx"
    args: ["-y", "openmode", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "shansabnani-openmode": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "openmode",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add shansabnani-openmode -t stdio -c npx -a -y openmode mcp
```

### Other

```json
{
  "mcpServers": {
    "shansabnani-openmode": {
      "command": "npx",
      "args": [
        "-y",
        "openmode",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-22 (score 72, +1)

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

### 2026-11-20 (score 71, +1)

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

### 2026-11-18 (score 70, +1)

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

### 2026-11-16 (score 69, +1)

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

### 2026-11-14 (score 68, +15)

- [security improvement] Malware scan: unverified → pass
- [functional regression] Schema quality: 185 → 205
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.1.1 → 0.2.0

### 2026-11-13 (score 53)

First indexed and scored.

## MCP tools (7)

### `look` (~196 tokens)

Look at a video

See a video, an image or a folder of frames. Returns one contact sheet (evenly spaced frames, each labelled with its timestamp) and facts: duration, size, fps, loudness in LUFS, silent stretches, black stretches, missing frames. Use it before editing footage and after every render to check your own work. Pass `at` for one full-size frame, or `start`/`end` to look closer at a stretch.

Input parameters:

- `at` (number): Return one full frame at this second.
- `end` (number): Look up to this second.
- `frames` (integer): Tiles on the sheet. Default 12.
- `out` (string): Also save the sheet here (.jpg).
- `path` (string, required): Video file, image file, or folder of numbered frames.
- `quick` (boolean): Skip sound and black-frame analysis.
- `start` (number): Look from this second.

### `render_edit` (~231 tokens)

Render an edit to MP4

Render an edit file to an MP4 with the local ffmpeg. An edit lists clips in order (video or image, with trims, speed, volume, cut or fade), audio tracks (music, voiceover), timed captions, an end card and a target loudness. Call edit_schema once to see the format. Render with quality draft first, look at it, then final. Returns the MP4 path, duration, size and render time.

Input parameters:

- `baseDir` (string): With `edit`: the folder clip paths are relative to. Default: the working directory.
- `edit`: Or the edit object itself, instead of a file.
- `file` (string): Path to the edit JSON file. Clip paths inside are relative to this file. Preferred.
- `out` (string): Output .mp4 path. Default: renders/<name>-<quality>.mp4 next to the edit file.
- `quality` (string): draft = fast and small, to check your work; final = full quality.
- `validateOnly` (boolean): Check the edit and report the timeline without rendering.

### `render_frames` (~152 tokens)

Render frames to MP4

Join a folder of numbered image frames (frame_0001.png ...) into an MP4, with an optional soundtrack. Use it for a headless-browser capture or any renderer that writes frames. Reports missing frame numbers instead of producing a broken film.

Input parameters:

- `audio` (string): Soundtrack file to lay under the frames.
- `dir` (string, required): Folder of numbered frames.
- `fps` (number): Frames per second. Default 24.
- `loudness` (number): Target loudness in LUFS, e.g. -14.
- `out` (string): Output .mp4 path.
- `quality` (string): draft = fast and small, to check your work; final = full quality.

### `render_blender` (~295 tokens)

Render a Blender scene to MP4

Render a .blend file, or a Python script that builds a scene with bpy, to an MP4 using the Blender installed on this machine. quality draft is small (360p), low-sample and may skip frames so you can check the scene in seconds; look at it, then render final at the scene's own size and samples. Returns the MP4 path, duration, size, renderer and frame count. Needs Blender; status says if it is installed.

Input parameters:

- `allowScripts` (boolean): Let Python stored inside the .blend run. Off by default.
- `audio` (string): Soundtrack file to lay under the film.
- `file` (string, required): A .blend file or a .py scene script.
- `loudness` (number): Target loudness in LUFS, e.g. -14.
- `out` (string): Output .mp4 path. Default: renders/<name>-<quality>.mp4 next to the scene.
- `quality` (string): draft = fast and small, to check your work; final = full quality.
- `range` (string): Frames to render, e.g. "1-48" or "12". Default: the scene's range.
- `renderer` (string): Override the scene's renderer.
- `samples` (integer): Override samples per pixel.
- `step` (integer): Render every Nth frame; the film keeps its length.

### `versions` (~228 tokens)

Save, list, restore and compare versions

Version history for the film folder (the working directory, or `dir`). save records every file with a message and the prompt that led to it; unchanged footage is stored once. list shows the history. restore puts the folder back to a version: unsaved work is saved first and the restore becomes a new version, so nothing is ever lost. diff shows which files changed between two versions (or a version and now), with a line diff for text files such as the edit.

Input parameters:

- `action` (string, required)
- `dir` (string): Film folder. Default: the working directory.
- `from` (string): diff: older version, e.g. v2.
- `id` (string): restore: the version to go back to, e.g. v3.
- `message` (string): save: what changed, in one line.
- `model` (string): save: the model that made it.
- `prompt` (string): save: the user's request that led to this version.
- `to` (string): diff: newer version, or "current" (default).

### `edit_schema` (~30 tokens)

Edit file format

The format of the edit file render_edit reads, with an example. Call once before writing your first edit.

### `status` (~44 tokens)

Check this machine

Check that ffmpeg is installed, whether Blender is, and which features work here (hardware encoder, captions). Call it if a render fails for a reason that is not the edit.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/shansabnani-openmode/openmode#diagnostics

## Score history

- 2026-11-22: 72
- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 70
- 2026-11-18: 70
- 2026-11-17: 69
- 2026-11-16: 69
- 2026-11-15: 68
- 2026-11-14: 68
- 2026-11-13: 53

## Common questions

### What is the openmode MCP server?

openmode is an MCP server listed in the public MCP registry as io.github.shansabnani/openmode. Video editing and rendering for coding agents: look at footage, render edits to MP4, keep versions. This page covers its npm package (openmode).

### Is the openmode MCP server safe to use?

openmode scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 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 openmode MCP server expose?

openmode exposes 7 tools: look, render_edit, render_frames, render_blender, versions, and 2 more. Their descriptions and schemas cost roughly 1,176 tokens of context every time the server is loaded.

### Is the openmode MCP server still maintained?

openmode is still listed as active in the MCP registry. We last reached this channel on 22 November 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 openmode MCP server under?

openmode declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the openmode MCP server?

VerifyMCP ran 16 checks on openmode, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/openmode
- Socket report: https://socket.dev/npm/package/openmode
- Repository: https://github.com/shansabnani/openmode
- Website: https://openmode.ai/
- Changelog RSS feed: https://verifymcp.io/servers/shansabnani-openmode/openmode.xml
- Changelog JSON feed: https://verifymcp.io/servers/shansabnani-openmode/openmode/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/shansabnani-openmode/openmode.json
- HTML version of this page: https://verifymcp.io/servers/shansabnani-openmode/openmode
