Verified conversions across 205 color spaces: CSS strings, gamut checks, .cube LUTs
Cuecaps 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.
What it does
Animated word-by-word captions for your video and audio files, rendered on your machine by Cuecaps.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user cuecaps-mcp '--' npx -y cuecaps-mcp
# 2 — ask your agent for something these tools do
# list_styles, studio_link, account_status and 2 more
Remote: no sign-in · Package: optional API key.
Cuecaps costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
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 cuecaps-mcp '--' npx -y cuecaps-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Its publisher also runs it at https://cuecaps.com/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http cuecaps-mcp https://cuecaps.com/mcpNothing is required, but it can take CUECAPS_API_KEY (Your key from cuecaps.com/account (Creator or Pro). list_styles and studio_link work without one.), CUECAPS_CHROME (Path to Chrome or Edge, when it isn't at a standard install path.) if you want to set them. Its publisher says some of its tools need one of them, and the rest work without.
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.
5 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.
Lists the 10 Cuecaps caption styles, each with the id to pass as style to caption_video or studio_link, its name and how it looks. The list is fixed and needs no key. Call it when the user hasn't picked a style or asks what the styles look like.
No parameter schema on file.
Returns a URL to the Cuecaps studio, opened with these caption settings, for the user to finish in their browser: they drop in the video, can fix words and export there. Creates nothing and needs no key, so it works on every plan, Free included. Use it when the user wants to edit by hand, has no…
No parameter schema on file.
Reads the Cuecaps account behind CUECAPS_API_KEY: the plan, cloud minutes left this period, the date they reset, and whether agent captioning is included. Uses no minutes. Call it before transcribe or caption_video to check the plan and minutes; with no key or an invalid key it returns an error…
No parameter schema on file.
Transcribes a local video or audio file and returns every word with its start and end time in seconds, plus the SRT text and the engine used. Writes no file: use caption_video when the user wants a captioned video, an overlay or a subtitle file. Needs a Creator or Pro key. engine "cloud" uses the…
No parameter schema on file.
Captions a local video or audio file with the Cuecaps studio's renderer in headless Chrome or Edge and writes <name>.captions.<ext> next to it, never replacing a file: an MP4 with the captions burned in, a transparent MOV or WebM overlay, or SRT or VTT subtitles. Returns the file, its duration in…
No parameter schema on file.
- 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 Cuecaps or to call it, at any volume.
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.
| 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 |
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.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, 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 |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
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
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.2. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
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.
Any signed-in account that does not publish Cuecaps can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.