mcp-video is now Kinocut
This package preserves existing installs after the project rename. It installs the matching
Kinocut release and keeps the mcp-video command and mcp_video Python import working.
New installations should use:
pip install kinocut
kino doctor
When upgrading an older shim, reinstall its matching canonical release after
the upgrade. Older installer records can remove the shared executable even when
pip check reports no dependency conflict:
python -m pip install --upgrade 'mcp-video==1.6.17'
python -m pip install --force-reinstall --no-deps 'kinocut==1.16.2'
python -m pip check
kino --version
kinocut --version
mcp-video --version
Preserve configured extras during the first upgrade. The new shim owns no console scripts; after this repair, removing it preserves all three canonical aliases.
Compatibility identifiers remain supported on the published Kinocut 1.16.x line and the prior 1.15.x line. Project home: kinocut.dev.
1 maintainer
Metadata
1 maintainer
Release files for mcp-video 1.6.18
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mcp_video-1.6.18.tar.gz | 2.7 kB | With provenance | Details for mcp_video-1.6.18.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_video-1.6.18-py3-none-any.whl | Python 3 | none | any | Details for mcp_video-1.6.18-py3-none-any.whl |
Total release size: 4.4 kB
Release files / mcp_video-1.6.18.tar.gz
| Download URL | mcp_video-1.6.18.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d4cbcd08a258857eed02b4948c78efdbe3e82cfded64fc7d6bfe53906a3b9b2
|
|
BLAKE2b-256 checksum How to use checksums |
cccbdd63f06934c41542c4bb227c10e7cf025c44c385a5bb860a4cf5cf947fa7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / mcp_video-1.6.18-py3-none-any.whl
| Download URL | mcp_video-1.6.18-py3-none-any.whl |
|---|---|
| Size | 1.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5643e2cb4bec41d7d1ba40e16c056926fad26cf5ecb634ac08fdd754f8c2b1b2
|
|
BLAKE2b-256 checksum How to use checksums |
7af3f9a30eb357c5be1b4b59b1cce19fc35d6ef62c08509b754ed1f566ea5911
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logSecurity for mcp-video 1.6.18
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for mcp_video-1.6.18.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
