Verified conversions across 205 color spaces: CSS strings, gamut checks, .cube LUTs
Nothing to run from here
Videokit is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
trust score
7
tools declared
local
runs on your machine
—
downloads a day
What it does
Probe, trim, transcode and extract frames or audio from local video files with ffmpeg.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user videokit-mcp '--' npx -y @reneturcios/videokit mcp
# 2 — ask your agent for something these tools do
# probe_video, get_thumbnail, extract_frames and 4 more
Videokit costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CLAll 68 servers
CloudCorpRecords68 servers
20 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Videokit as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user videokit-mcp '--' npx -y @reneturcios/videokit mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Probe a local video file for duration, dimensions, codecs and format
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_path | yes | Path to the local video file to probe. |
Extract a single frame of a video as a thumbnail image file
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_path | yes | Path to the local video file to extract the thumbnail frame from. | |
| output_file | yes | Path of the image file to write the extracted thumbnail frame to. | |
| timestamp_seconds | no | Optional timestamp in seconds into the video at which to capture the thumbnail frame; defaults to 0 and must be >= 0. |
Extract frames of a video as image files in an output directory at a given rate
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_path | yes | Path to the local video file to extract frames from. | |
| fps | no | Optional rate in frames per second at which to extract frames; defaults to 1 and must be > 0. | |
| output_dir | yes | Directory to write the extracted frame image files into, named frame-%04d.png. |
Extract the audio track of a video into an audio file
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_path | yes | Path to the local video file to extract the audio track from. | |
| output_file | yes | Path of the audio file to write the extracted audio track to. |
Trim a video to a segment starting at an offset, optionally with a duration
| Parameter | Type | Required | Notes |
|---|---|---|---|
| duration_seconds | no | Optional length in seconds of the trimmed segment, starting at start_seconds; must be > 0 when given. | |
| file_path | yes | Path to the local video file to trim. | |
| output_file | yes | Path of the video file to write the trimmed segment to. | |
| start_seconds | yes | Offset in seconds from the start of the video at which the trimmed segment begins; must be >= 0. |
Transcode a video to another container format
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_path | yes | Path to the local video file to transcode. | |
| format | yes | Target container format to transcode the video to; output_file must end with '.' followed by this format. | |
| output_file | yes | Path of the video file to write the transcoded video to; must end with '.' followed by the target format. |
Resize a video to the given width and height
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_path | yes | Path to the local video file to resize. | |
| height | yes | Target height in pixels for the resized video; must be > 0. | |
| output_file | yes | Path of the video file to write the resized video to. | |
| width | yes | Target width in pixels for the resized video; must be > 0. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Videokit or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 0.1.0 · scanned 31 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings1 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digestbb5ddc848038a8b18979e9eb49e15c70a3f60c89c4b4bba66933dfb1af831ba2
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (7 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| probe_video | no tags | |
| get_thumbnail | no tags | |
| extract_frames | no tags | |
| extract_audio | no tags | |
| trim_video | no tags | |
| transcode_video | no tags | |
| resize_video | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestbb5ddc848038a8b1
Scanned2026-10-31
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Videokit can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.