Case file No.176 · pypi · stdio

mcp-video

io.github.KyaniteLabs/mcp-video · v1.6.17

Compatibility package: mcp-video now installs Kinocut (formerly mcp-video).

Package ↗GitHub ↗Website ↗

Security score

93/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 0 days ago

Source transparency15/15

public repo, license Apache-2.0

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

668 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

v1.6.16 → v1.6.17Oct 21, 2026
- version changed version bump
```
"1.6.16" → "1.6.17"
```
- packages.0.version changed package version bump
```
"1.6.16" → "1.6.17"
```
First snapshot (v1.6.16)Oct 16, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is mcp-video safe?

MCPWatch gives mcp-video a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does mcp-video have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package mcp-video. That is not proof of safety.

When was mcp-video last updated?

The latest registry version is 1.6.17, published Oct 21, 2026. The last push to KyaniteLabs/kinocut was on Oct 21, 2026. MCPWatch last checked it on Oct 21, 2026.

What license does mcp-video use?

GitHub reports the license of KyaniteLabs/kinocut as Apache-2.0.

Related servers

same publisher / similar score