@faviovazquez/showtime-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 0 of 2 tools tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y -p @faviovazquez/showtime-mcp@0.4.6 showtime-mcp
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
2 tools that take no input and look read-only were called once with nothing. 0 returned a result.
guide | No usable answer tool reported an error: showtime needs Python 3.8+ (or uv) and neither was found. fix: install uv (https://docs.astral.sh/uv/getting-started/installation/) or P |
status | No usable answer tool reported an error: showtime needs Python 3.8+ (or uv) and neither was found. fix: install uv (https://docs.astral.sh/uv/getting-started/installation/) or P |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
doctor full, background
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.
guide topic, section, find, all
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.
status job, task
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.
receipt job
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.
new_project template, dir, duration, aspect, size, title, mode, tone, storyboard, look
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).
5 more tools
render project, preview, job, output, from, to, workers, scale, audio, page, alpha, background
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.
check project, samples, strict, background
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.
qa video, project, platform, strict, background
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.
export_html project, output, audio, target, job, controls, autoplay_muted, loop, folder, background
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).
deliver_exports video, targets, fit, preview, max_mb, max_mb_per_target, lufs, from, to, width, fps, background
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/.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=20 |
| Source | github.com/FavioVazquez/showtime |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-F7JtzzloHG2fWiZpFtn3EkpjT1BgJi2qqAuXRhcxHGUwaOgbipYiJju77b9+IORe3RWscuT+SRGKsMw9PTcHDQ== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40faviovazquez/showtime-mcp)
New version out? Ask for a fresh report.