snapcn
NPM · @SNAPCN/MCP
Search hand-tuned Remotion components, read their props, and plan a video from a one-line brief.
Available components
Last scanned (7 hours ago)
Scores higher than 36% 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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 2 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1715 tokens (~285/item across 6 items; 6 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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 +15
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 46
First indexed and scored.
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 24 Oct 2026 · Analysed npm/@snapcn/mcp@0.1.5
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
snapcn_analyze_recording Analyze a screen recording ~571
MEASURE a screen recording so content.recording is filled from data, not guessed. Returns crop, beatFrames and focus already in snapcn_plan_video's shape, plus one frame per beat cropped and fitted exactly as the composition will show it. Call it BEFORE snapcn_plan_video whenever the user has a recording: these are the three fields the contract says not to guess, and omitting them is not neutral — the default beat walk (0/139/278) only reaches 9.3s into a take of any length, so a 37s demo ships with its payoff never on screen.
| Name | Type | Req | Description |
|---|---|---|---|
| at_seconds | array | – | VERIFY MODE. Skip the analysis and just return these moments of the take, cropped exactly as the composition will show them. Use it after moving a beat: pass the new opening times and look, instead o… |
| beat_frames | integer | – | Frames one screen beat runs. 139 is what screen-recording ships at and what the screen-demo recipe bills. It is load-bearing here: a beat opening later than duration - beat_frames/fps runs past the e… |
| beats | integer | – | Screen beats to propose, one source frame each. 3 for product-demo's screen-demo (reveal / the moment / interaction), 2 for cli-tool-demo. Drop to 1 if you only want the reveal. |
| composition_aspect | number | – | width/height of the composition the shot lands in (1280x720 = 1.7778). Everything x/y is normalized to. A source of a different aspect is centre-cropped to this before crop applies, and points outsid… |
| file | string | yes | Path to the recording (.mp4/.mov/.webm/.m4v). Absolute, or relative to project_dir. Paste the name exactly as the filesystem has it — macOS writes a NARROW NO-BREAK SPACE (U+202F) before "PM" in a sc… |
| fps | integer | – | The COMPOSITION's fps, not the file's. trimBefore is a Sequence offset, so beatFrames are composition frames. At 30fps a 120fps source's own 1754 frames are not numbers you can pass. |
| project_dir | string | – | Root of the user's Remotion project — the folder with package.json and node_modules. Its @remotion/cli is where ffmpeg and ffprobe come from; there is nothing else to install. Default: the directory… |
No output schema declared.
No examples provided.
snapcn_component Get a snapcn component ~72
Everything needed to use one snapcn component: install command, full prop table with defaults and ranges, a working example, when not to use it, and its frame budget.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Registry name, e.g. 'text-reveal'. Accepts a legacy name and tells you the replacement. |
No output schema declared.
No examples provided.
snapcn_plan_video Plan a video ~386
Turn a one-line video brief into a beat-by-beat plan: archetype, duration, one registry component per beat with frame budgets, a single install command, and a ready TransitionSeries skeleton.
| Name | Type | Req | Description |
|---|---|---|---|
| accent_color | string | – | One hex accent, e.g. '#F2D200'. One accent only. |
| allow_placeholders | boolean | – | ESCAPE HATCH. Only when the user is genuinely unreachable: emits the skeleton with honest English placeholders ("<the problem your users have today>") and a REPLACE list, instead of questions. Never… |
| archetype | string | – | Force a recipe. Omit to let the brief pick. |
| brief | string | yes | One line: what the video is for, the product, and the surface to show. e.g. 'launch video for Acme, an AI CLI that fixes flaky tests'. |
| content | object | – | The user's REAL copy. Without the required fields this tool returns questions and no skeleton — a skeleton pre-filled with component defaults is how a video ends up saying "Scene A". Infer what you c… |
| duration_seconds | integer | – | Target length; selects the short/standard variant. Default: the archetype's own. |
| mode | string | – | Frame background. "dark" sets mode="dark" on every component in the skeleton. |
| vibe | string | – | How it should FEEL. Not decoration: several beats offer more than one component for the same job, and this is what chooses between them — premium opens on a swell and closes on the logo, tech opens o… |
No output schema declared.
No examples provided.
snapcn_preview Preview a frame ~391
Render a frame of the video you just wrote and LOOK at it. Shells the user's own Remotion CLI (`remotion still`) and returns the frame as an image. Call it after writing a composition and after every fix: a snapcn scene missing mode="dark" on a dark frame renders BLACK, and that is invisible from the code. Requires the user's Remotion project — snapcn does not bootstrap it.
| Name | Type | Req | Description |
|---|---|---|---|
| composition | string | yes | The <Composition id="..."> to render, exactly as registered in the Root file. Required: with no id the Remotion CLI opens an interactive picker and this call would hang. |
| entry | string | – | Remotion entry point, e.g. 'src/index.ts'. Omit unless the render says it cannot find one: the CLI already resolves remotion.config.ts, src/index.ts(x), remotion/index.ts(x) and src/remotion/index.ts… |
| frames | array | – | Frames to render, one image back per frame (max 4). Default [30] — 1s in, after the entrance. Pick the frame where each beat has LANDED; at frame 0 most snapcn components have not started and you wil… |
| project_dir | string | – | Root of the user's Remotion project — the folder with package.json and node_modules. Default: the directory this server was started in. |
| scale | number | – | Render scale. 0.5 of a 1280×720 composition is enough to judge layout, colour and a black frame. Raise to 1 only when you need to read small type. |
| timeout_seconds | integer | – | Budget for the WHOLE call, all frames. The first render of a session also builds a webpack bundle and may download Chromium; later ones take seconds. |
No output schema declared.
No examples provided.
snapcn_rules snapcn motion rules ~48
The snapcn motion, design and anti-slop rules. Read before writing any scene chrome of your own — backdrops, cards, lower-thirds, easing.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | – |
No output schema declared.
No examples provided.
snapcn_search_components Search snapcn components ~179
Find snapcn Remotion components for a scene by describing the beat in plain English. Returns ranked candidates with natural length, vibe and use/avoid notes. Use this instead of writing animation code.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| max_frames | integer | – | Drop candidates longer than this frame budget (30fps). |
| query | string | yes | What the shot must DO, not a component name. e.g. 'swap one pricing number for another', 'show our CLI install command', 'burned-in captions over a talking head'. Pass an empty string with a category… |
| tier | string | – | Which half of the catalogue. Pro components install with the user's key and are the premium scenes; free ones install with no key at all. |
| vibe | string | – | – |
No output schema declared.
No examples provided.
How do I install the snapcn MCP server?
snapcn runs locally as an npm package, launched with npx -y @snapcn/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 · @snapcn/mcp
claude mcp add dev-snapcn-mcp -- npx -y @snapcn/mcp
What is the snapcn MCP server?
snapcn is an MCP server listed in the public MCP registry as dev.snapcn/mcp. Search hand-tuned Remotion components, read their props, and plan a video from a one-line brief. This page covers its npm package (@snapcn/mcp).
Is the snapcn MCP server safe to use?
snapcn scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 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 snapcn MCP server expose?
snapcn exposes 6 tools: snapcn_search_components, snapcn_component, snapcn_plan_video, snapcn_preview, snapcn_analyze_recording, snapcn_rules. Their descriptions and schemas cost roughly 1,647 tokens of context every time the server is loaded.
Is the snapcn MCP server still maintained?
snapcn is still listed as active in the MCP registry. We last reached this channel on 24 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 snapcn MCP server under?
snapcn declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.