# VidLet (npm · @spark-apps/vidlet)

Edit video by asking: auto-captions, jump cuts, narrated Shorts, GIFs, voiceover, YouTube upload.

- Trust score: 24/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@spark-apps/vidlet`: 24/100 (this document), [markdown](https://verifymcp.io/servers/app-vidlet-vidlet/spark-apps-vidlet.md), [page](https://verifymcp.io/servers/app-vidlet-vidlet/spark-apps-vidlet)

## Channel facts

- Registry: `npm`
- Package: `@spark-apps/vidlet`
- Version: `1.2.2`
- 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-05.

- **Supply Chain Security**: 66/100
  - No malware found by supply-chain analysis.
  - A critical CVE affects zod, and no fixed version has been published yet.
  - Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does.
  - Dependency health was assessed across the 387 of 393 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (AGPL-3.0).
  - Actively maintained (last published 37 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it.

## Install

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

VidLet runs locally as an npm package, launched with npx -y @spark-apps/vidlet. The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs. 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 app-vidlet-vidlet -- npx -y @spark-apps/vidlet
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Cursor

```json
{
  "mcpServers": {
    "app-vidlet-vidlet": {
      "command": "npx",
      "args": [
        "-y",
        "@spark-apps/vidlet"
      ]
    }
  }
}
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### VS Code

```json
{
  "servers": {
    "app-vidlet-vidlet": {
      "command": "npx",
      "args": [
        "-y",
        "@spark-apps/vidlet"
      ]
    }
  }
}
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Codex

```bash
codex mcp add app-vidlet-vidlet -- npx -y @spark-apps/vidlet
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-vidlet-vidlet": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@spark-apps/vidlet"
      ],
      "enabled": true
    }
  }
}
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### OpenClaw

```bash
openclaw mcp add app-vidlet-vidlet --command npx --arg -y --arg @spark-apps/vidlet
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Hermes

```yaml
mcp_servers:
  app-vidlet-vidlet:
    command: "npx"
    args: ["-y", "@spark-apps/vidlet"]
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Netclaw

```json
{
  "McpServers": {
    "app-vidlet-vidlet": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@spark-apps/vidlet"
      ]
    }
  }
}
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Vellum

```bash
assistant mcp add app-vidlet-vidlet -t stdio -c npx -a -y @spark-apps/vidlet
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Other

```json
{
  "mcpServers": {
    "app-vidlet-vidlet": {
      "command": "npx",
      "args": [
        "-y",
        "@spark-apps/vidlet"
      ]
    }
  }
}
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

## 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-09-30 (score 0)

- [security regression] CVE-2026-101894 affects this package: high
- [security improvement] Malware scan: unverified → pass

### 2026-09-29 (score 0)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/app-vidlet-vidlet/spark-apps-vidlet#diagnostics

## Score history

- 2026-11-05: 24
- 2026-11-04: 24
- 2026-11-03: 24
- 2026-11-02: 24
- 2026-11-01: 24
- 2026-10-31: 24
- 2026-10-30: 24
- 2026-10-29: 24
- 2026-10-28: 24
- 2026-10-27: 24
- 2026-10-26: 24
- 2026-10-25: 24
- 2026-10-24: 24
- 2026-10-23: 24
- 2026-10-22: 24
- 2026-10-21: 24
- 2026-10-20: 24
- 2026-10-19: 24
- 2026-10-18: 24
- 2026-10-17: 24
- 2026-10-16: 24
- 2026-10-15: 24
- 2026-10-14: 24
- 2026-10-13: 24
- 2026-10-12: 24
- 2026-10-11: 24
- 2026-10-04: 24
- 2026-10-03: 24
- 2026-10-02: 24
- 2026-10-01: 24

## Common questions

### What is the VidLet MCP server?

VidLet is an MCP server listed in the public MCP registry as app.vidlet/vidlet. Edit video by asking: auto-captions, jump cuts, narrated Shorts, GIFs, voiceover, YouTube upload. This page covers its npm package (@spark-apps/vidlet).

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

VidLet scores 24 out of 100 on VerifyMCP. We recorded 18 known advisories against it as of 5 November 2026. 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.

### Is the VidLet MCP server still maintained?

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

VidLet declares the AGPL-3.0 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 VidLet MCP server?

VerifyMCP ran 8 checks on VidLet, covering Malware scan, Known CVEs, Install scripts, Dependency health and 4 more. 6 items could not be completed, a gap on our side rather than a finding about VidLet: Security disclosure, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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/@spark-apps/vidlet
- Socket report: https://socket.dev/npm/package/@spark-apps/vidlet
- Website: https://vidlet.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-vidlet-vidlet/spark-apps-vidlet.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-vidlet-vidlet/spark-apps-vidlet/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-vidlet-vidlet/spark-apps-vidlet.json
- HTML version of this page: https://verifymcp.io/servers/app-vidlet-vidlet/spark-apps-vidlet