showtime
NPM · @FAVIOVAZQUEZ/SHOWTIME-MCP · 2 COMPONENTS
Local video studio for your coding agent: scenes, voice, music and captions, on your machine.
Available components
Last scanned (15 hours ago)
Scores higher than 42% of npm servers
Category Design and Media
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2695 tokens (~269/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management24
- Stability check failed: the tool surface changed between 0.2.0 and 0.4.6: 10 tool removals, 0 breaking changes, 2 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 18 to 21.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 11 to 14.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 4 to 8.
- 16 Oct 26 0
- Package version: 0.4.5 → 0.4.6 functional
- 15 Oct 26 0
- Tool safety: pass → unverified ▼ security
- Stability: fail → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 0.4.4 → 0.4.5 functional
- 14 Oct 26 +29
- Stability: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Schema quality: 220 → 269 ▼ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Package version: 0.4.3 → 0.4.4 functional
- 13 Oct 26 0
- Package version: 0.3.5 → 0.4.3 functional
- Package version: 0.3.5 → 0.4.2 functional
- 12 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- Package version: 0.4.1 → 0.4.2 functional
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 23 Oct 2026 · Analysed npm/@faviovazquez/showtime-mcp@0.4.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check Check a project before rendering ~146
Pre-render checks of a project: page errors, determinism, text off-canvas or overlapping, contrast, readability, dead air, fonts. Lists problems with timestamps and fixes, plus a contact sheet path.
| Name | Type | Req | Description |
|---|---|---|---|
| background | boolean | – | answer at once with a task id and keep working in the background; the status tool with {"task": id} reports progress and the result. Default false: wait for the result (a host with a short tool-call… |
| project | string | yes | project folder |
| samples | integer | – | evenly spaced sample times (default 9) |
| strict | boolean | – | treat warnings as failures |
No output schema declared.
No examples provided.
deliver_exports Export for platforms ~361
Turn one master video into platform files (youtube, x, linkedin, reels, tiktok, shorts, square, github, chat, original, or all): aspect conversion, length and size limits, loudness; or silent README/docs loops (webp, gif, webp-small, gif-small; from/to/width/fps apply to these only). Files go to <video folder>/exports/.
| Name | Type | Req | Description |
|---|---|---|---|
| background | boolean | – | answer at once with a task id and keep working in the background; the status tool with {"task": id} reports progress and the result. Default false: wait for the result (a host with a short tool-call… |
| fit | string | – | aspect conversion (default auto) |
| fps | number | – | loops: frame rate |
| from | number | – | loops: window start in seconds |
| lufs | number | – | loudness for every export (default: the job's target, else -14) |
| max_mb | number | – | size cap in MB for original/github/chat/web and the loops (for every target when none of those is listed; YouTube and the other platforms keep full quality otherwise) |
| max_mb_per_target | object | – | size caps for single targets, e.g. {"shorts": 19, "original": 20} |
| preview | boolean | – | fast, lower-quality encodes to check framing |
| targets | array | yes | platforms, e.g. ["youtube", "reels"] |
| to | number | – | loops: window end in seconds |
| video | string | yes | master video, or a job folder/name (its latest final) |
| width | integer | – | loops: width in px |
No output schema declared.
No examples provided.
doctor Check the showtime installation ~148
Check that showtime is installed and working (ffmpeg, Python, Node, browser, models). Returns PASS/WARN/FAIL per item with a one-line fix. Run this first; if setup is missing it says the exact command to run.
| Name | Type | Req | Description |
|---|---|---|---|
| background | boolean | – | answer at once with a task id and keep working in the background; the status tool with {"task": id} reports progress and the result. Default false: wait for the result (a host with a short tool-call… |
| full | boolean | – | also launch a browser and run a test encode (slower, about 30-60 s). Default false. |
No output schema declared.
No examples provided.
export_html Export an interactive HTML video ~277
Export a project as one self-contained HTML file that plays offline in any browser (player with scrubber, chapters, keyboard controls; frames drawn live by the same runtime as the MP4).
| Name | Type | Req | Description |
|---|---|---|---|
| audio | string | – | audio mode (default auto) |
| autoplay_muted | boolean | – | start playing muted as soon as it loads (for embedding) |
| background | boolean | – | answer at once with a task id and keep working in the background; the status tool with {"task": id} reports progress and the result. Default false: wait for the result (a host with a short tool-call… |
| controls | string | – | player chrome: full (default), minimal, or none (for embedding) |
| folder | boolean | – | write a folder (index.html + assets/) for hosting instead of one file; output is then a folder |
| job | string | – | write into this job folder or job name (with output: that file name inside it) |
| loop | boolean | – | loop by default |
| output | string | – | output .html (default: a new showtime-out/ job folder) |
| project | string | yes | project folder |
| target | string | – | file (default) or artifact (one file under 16 MB for sandboxed hosts) |
No output schema declared.
No examples provided.
guide Read the showtime references ~169
The references by the piece: with topic alone, its Essentials (the rules for that step) and its section list; with section, that one section (a number, a name, or a sub-heading such as a component or a command); with find, every line that mentions all the words. No arguments lists the topics. Read what the step needs, not whole files.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | the whole file (large; prefer a section) |
| find | string | – | words to find (every word must be on the line) |
| section | string | – | a section number or name, e.g. 3, count-up, showtime check |
| topic | string | – | a reference: components, render, story, launch (the launch workflow), data-story, manim ... |
No output schema declared.
No examples provided.
new_project Create a video project ~500
Create a new video project folder from a template (showtime.json + index.html + assets). Edit its index.html to make the video, then call render. Templates: dom (HTML motion graphics, 16:9), short (vertical social), data (animated charts), film (canvas), tutorial (app walkthrough), series (episodes), showreel (a dense 15 s motion reel: shader, particles, 3D, kinetic and glitch type). tone: showreel for a showreel, hype reel or "go all out" brief. mode: quality (the default: every finished video gets the full review, and qa says "review pending" until a critic round has a verdict) or lean (a cheaper draft pass, only when the user asks for a quick draft: no critic round unless publish-bound).
| Name | Type | Req | Description |
|---|---|---|---|
| aspect | string | – | frame shape at 1080p |
| dir | string | yes | new project folder (must not exist or be empty); relative paths are under the project folder |
| duration | number | – | length in seconds; every scene, the poster and the music are rescaled |
| look | string | – | look signature for dom, launch, short or data: auto (default: picked away from recent looks), template (the template's own look) or an id (`showtime signature`); a brand kit wins |
| mode | string | – | review mode: quality (default, full review with a critic round before delivery) or lean (draft pass; only when the user asks for a quick or cheap draft) |
| size | string | – | exact frame size WxH, e.g. 1280x720 (overrides aspect) |
| storyboard | string | – | a storyboard from another tool: a Markdown table (Shot | Length | Visual | Narration) or a storyboard.json; one scene per shot (DOM templates; not with duration), its narration as narration.md |
| template | string | yes | template name |
| title | string | – | video title (default: the folder name) |
| tone | string | – | tone preset (showtime.json "tone", references/tones.md). showreel: a showreel, hype reel or "go all out" brief (flash words allowed, 12-14 shots per 15 s, a ~1 s end card, no shot twice, the showreel… |
No output schema declared.
No examples provided.
qa Verify a finished video ~248
Check a rendered video (or a job's latest render): codec and color tags, duration, loudness and true peak, silence, black or frozen stretches, captions, credits, and the platform's limits. PASS/WARN/FAIL with timestamps. Do not call a video ready until qa passes. In quality mode (the default) a job's final also needs a critic round: a "review pending" line names the command (showtime review-pack, then a critic sub-agent on its CRITIC.md) until that round has a verdict; lean mode skips it.
| Name | Type | Req | Description |
|---|---|---|---|
| background | boolean | – | answer at once with a task id and keep working in the background; the status tool with {"task": id} reports progress and the result. Default false: wait for the result (a host with a short tool-call… |
| platform | string | – | where it will be posted |
| project | string | – | project folder (default: found from the render report) |
| strict | boolean | – | treat warnings as failures |
| video | string | – | video file, or a job folder/name (default: the current or newest job) |
No output schema declared.
No examples provided.
receipt Write the receipt of a job ~105
Write the job's receipt (receipt.md, receipt.json and one line in share.txt): the request as typed, assumptions, review rounds, full and partial renders, the images showtime made for looking, wall time, and tokens and cost when the agent's session log is known. Anything unknown says "not reported by this agent". Call it last, after delivering.
| Name | Type | Req | Description |
|---|---|---|---|
| job | string | – | job folder or job name (default: the current or newest job under showtime-out/) |
No output schema declared.
No examples provided.
render Render a project to video ~398
Render a project folder to MP4 (frame-exact, H.264, loudness-normalised audio). Use preview=true first for a fast 720p draft, then qa, then a final render. Output goes to a new showtime-out/<title>-<time>/ job folder (or into job); earlier renders are never overwritten. Reports progress while it runs.
| Name | Type | Req | Description |
|---|---|---|---|
| alpha | string | – | transparent output: prores (.mov ProRes 4444, large), animation (.mov QuickTime Animation, small for flat graphics) or webm (VP9, web) |
| audio | boolean | – | include the soundtrack (default true) |
| background | boolean | – | answer at once with a task id and keep working in the background; the status tool with {"task": id} reports progress and the result. Default false: wait for the result (a host with a short tool-call… |
| from | number | – | start time in seconds (partial render: with job and a full render there, the span is spliced into a new full final; otherwise a span-A-B.mp4 clip, not the video) |
| job | string | – | render into this job folder or job name |
| output | string | – | output file (.mp4, .mov or .webm) instead of a new job folder |
| page | string | – | page inside the project to render (default index.html), e.g. square.html |
| preview | boolean | – | fast draft: <= 720p, quick encode. Default false (final quality). |
| project | string | yes | project folder (contains showtime.json) |
| scale | number | – | output scale, e.g. 0.5 (default 1) |
| to | number | – | end time in seconds (partial render) |
| workers | integer | – | parallel browsers 1-3 (default: automatic) |
No output schema declared.
No examples provided.
status Where a job or a task stands ~151
Where the newest job (or the given one) stands: stage, review mode (quality or lean) and critic round, what is verified vs assumed, and the next command. With task (the id a long tool such as render or transcribe answered with when it ran past the call's time limit): whether it still runs and its latest progress; once it has finished, its full result. Each task call waits up to about 20 s.
| Name | Type | Req | Description |
|---|---|---|---|
| job | string | – | job folder or job name (default: the newest job under showtime-out/) |
| task | string | – | a task id from a long tool call, e.g. render-20260928-141500-a1b2 |
No output schema declared.
No examples provided.
How do I install the showtime MCP server?
showtime runs locally as an npm package, launched with npx -y @faviovazquez/showtime-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 · @faviovazquez/showtime-mcp
claude mcp add faviovazquez-showtime -- npx -y @faviovazquez/showtime-mcp
What is the showtime MCP server?
showtime is an MCP server listed in the public MCP registry as io.github.FavioVazquez/showtime. Local video studio for your coding agent: scenes, voice, music and captions, on your machine. This page covers its npm package (@faviovazquez/showtime-mcp).
Is the showtime MCP server safe to use?
showtime scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. 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 showtime MCP server expose?
showtime exposes 10 tools: doctor, guide, status, receipt, new_project, and 5 more. Their descriptions and schemas cost roughly 2,503 tokens of context every time the server is loaded.
Is the showtime MCP server still maintained?
showtime is still listed as active in the MCP registry. We last reached this channel on 23 October 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 showtime MCP server under?
showtime declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.