Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

OpenCaptions

NPM · OPENCAPTIONS

Animated word-by-word captions for your videos, on your computer or your own OpenCaptions server

Available components

−12 this week 69 Trust /100

Last scanned (10 hours ago)

Scores higher than 40% of npm servers

Category Design and Media

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security48
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 102 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to leogaudin/opencaptions). View diagnostics → Pass
  • Clear OSI-approved license (AGPL-3.0-only).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 966 tokens (~107/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 1.3.2 → 1.3.3 functional
  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 0
    • Stability: 0.07 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 1.3.1 → 1.3.2 functional
  • 12 Nov 26 +1
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.07 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 1.3.0 → 1.3.1 functional
  • 11 Nov 26 +25
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.87 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/opencaptions@1.3.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo leogaudin/opencaptions
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/leogaudin/opencaptions/.github/workflows/ci.yml@refs/tags/v1.3.3
Rekor log index 4033059372
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:1e5bba77f4f747d0f1c748618e01095742a48dc1de57d269390b61ee2cf501e148fc9d7fa8d1103c66e6b5d1f0328f67c354eb547de966cc14c79ac20

Background: How many MCP packages publish verified provenance →

Dependencies 102 packages
Packages resolved 102
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~923 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
caption_video ~345

Adds animated word-by-word captions to a video: transcribes the speech, styles it with a look, and saves the captioned video next to the source. Returns its path and a project id for follow-ups (get_transcript, fix_words, set_style, save_video). If it takes longer than the call allows, it returns a ticket: pass it to check_progress.

NameTypeReqDescription
captions_onlyboolean–The captions alone over solid green, with no sound, to key out in Remotion or a video editor
formatstring–mp4 (the default), mp4-hevc, webm or mov (ProRes)
frame_ratestring–Frames per second, or the source's
languagestring–ISO 639-1 code, or auto (the default)
lookstring–A built-in look (list_looks): Purple Punch, Bold, Plain, Karaoke, Paper, Boom, Lyric, Stickers, Cinema, Terminal, Neon, Typewriter, Handwritten, Pop, Cascade, Slam, Poster, Title Card, Editorial
modelstring–A speech model id the server offers; its default if left out. Without a server, parakeet-ultra only
outputstring–Where to write the file. Default: next to the source, named <name>.captioned
resolutionstring–The short side in pixels, or the source's
sourcestringyesA video file path, or a direct http(s) link to one
styleobject–Style settings over the look (describe_style lists every one)

No output schema declared.

No examples provided.

check_progress ~37

Carries on with a caption_video or save_video that returned a ticket.

NameTypeReqDescription
ticketobjectyesThe ticket, as it was returned

No output schema declared.

No examples provided.

describe_style ~32

Every style setting with its type, range, default and meaning, for caption_video's and set_style's `style`.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

export_subtitles ~77

Writes a project's captions as SRT or VTT subtitles, or its transcript as JSON.

NameTypeReqDescription
formatstringyes–
outputstring–Where to write it; next to the video by default
project_idstringyesThe project id a caption_video call returned (on this computer, a file's path)

No output schema declared.

No examples provided.

fix_words ~87

Sets words by the index get_transcript gave them, keeping their timing; empty text removes a word, and count joins that many words into one spanning them all (two words heard for one). Then save_video writes the video again.

NameTypeReqDescription
fixesarrayyes–
project_idstringyesThe project id a caption_video call returned (on this computer, a file's path)

No output schema declared.

No examples provided.

get_transcript ~60

A project's captions as they show on the video, and every word with its index, to check names and spelling before fix_words.

NameTypeReqDescription
project_idstringyesThe project id a caption_video call returned (on this computer, a file's path)

No output schema declared.

No examples provided.

list_looks ~24

The built-in caption looks, each with its animation, font and colours.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

save_video ~172

Saves a project's captioned video again, after fix_words or set_style, or in another format, size or as captions only.

NameTypeReqDescription
captions_onlyboolean–The captions alone over solid green, with no sound, to key out in Remotion or a video editor
formatstring–mp4 (the default), mp4-hevc, webm or mov (ProRes)
frame_ratestring–Frames per second, or the source's
outputstring–Where to write the file. Default: next to the source, named <name>.captioned
project_idstringyesThe project id a caption_video call returned (on this computer, a file's path)
resolutionstring–The short side in pixels, or the source's

No output schema declared.

No examples provided.

set_style ~89

Changes a project's style: a look, settings over it, or settings alone over the style it has. Then save_video writes the video again.

NameTypeReqDescription
lookstring–A built-in look (list_looks)
project_idstringyesThe project id a caption_video call returned (on this computer, a file's path)
styleobject–Style settings (describe_style)

No output schema declared.

No examples provided.

Install

How do I install the OpenCaptions MCP server?

OpenCaptions runs locally as an npm package, launched with npx -y opencaptions mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · opencaptions

# add to Claude Code
claude mcp add leogaudin-opencaptions -- npx -y opencaptions mcp
Common questions

What is the OpenCaptions MCP server?

OpenCaptions is an MCP server listed in the public MCP registry as io.github.leogaudin/opencaptions. Animated word-by-word captions for your videos, on your computer or your own OpenCaptions server. This page covers its npm package (opencaptions).

Is the OpenCaptions MCP server safe to use?

OpenCaptions scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.

What tools does the OpenCaptions MCP server expose?

OpenCaptions exposes 9 tools: caption_video, check_progress, list_looks, describe_style, get_transcript, and 4 more. Their descriptions and schemas cost roughly 923 tokens of context every time the server is loaded.

Is the OpenCaptions MCP server still maintained?

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

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

VerifyMCP ran 15 checks on OpenCaptions, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about OpenCaptions: Malware scan. 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.