LeClap
NPM · @LECLAP/MCP · SCANNED SEP 22
Compose and render video from one JSON template. Deterministic, runs locally, no generative model.
Available components
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
- 23 of 73 dependencies flagged as unhealthy. View diagnostics → Partial
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 28 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 301 tokens (~60/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (60% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the LeClap MCP server?
LeClap runs locally as an npm package, launched with npx -y @leclap/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 · @leclap/mcp
claude mcp add dev-leclap-video -- npx -y @leclap/mcp
{
"mcpServers": {
"dev-leclap-video": {
"command": "npx",
"args": [
"-y",
"@leclap/mcp"
]
}
}
} {
"servers": {
"dev-leclap-video": {
"command": "npx",
"args": [
"-y",
"@leclap/mcp"
]
}
}
} codex mcp add dev-leclap-video -- npx -y @leclap/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-leclap-video": {
"type": "local",
"command": [
"npx",
"-y",
"@leclap/mcp"
],
"enabled": true
}
}
} openclaw mcp add dev-leclap-video --command npx --arg -y --arg @leclap/mcp
mcp_servers:
dev-leclap-video:
command: "npx"
args: ["-y", "@leclap/mcp"] {
"McpServers": {
"dev-leclap-video": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@leclap/mcp"
]
}
}
} assistant mcp add dev-leclap-video -t stdio -c npx -a -y @leclap/mcp
{
"mcpServers": {
"dev-leclap-video": {
"command": "npx",
"args": [
"-y",
"@leclap/mcp"
]
}
}
} 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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 2026 · Analysed npm/@leclap/mcp@0.3.4
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 73 packages
| Packages resolved | 73 |
|---|---|
| Stale | 23 |
| 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 →
compose_video Compose Video ~111
Render a video from an inline template descriptor (`template`). Supply user clips via userVideoPaths (absolute paths under the configured media dir) for each project_video section, optional form `fields`, and an optional `locale`. Renders in a forked worker and returns the output mp4 path plus duration/codec metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | – |
| locale | string | – | – |
| outputBaseName | string | – | – |
| template | object | yes | – |
| userVideoPaths | object | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| audioCodec | string|null | yes | – |
| durationSeconds | number|null | yes | – |
| outputPath | string | yes | – |
| renderId | string | yes | – |
| sizeBytes | number | yes | – |
| videoCodec | string|null | yes | – |
No examples provided.
get_template_schema Get Template Schema ~43
Return the JSON Schema for a template descriptor plus a short authoring guide. Use this to understand the full set of fields when building or editing a template for compose_video.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ping Ping ~16
Health check — returns a fixed readiness string.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
probe_media Probe Media ~59
Inspect a local media file (absolute path under the configured media dir) and return its duration, video/audio codecs, audio sample rate, and byte size. Probes via ffprobe directly so it never writes to stdout.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| audioCodec | string|null | yes | – |
| durationSeconds | number|null | yes | – |
| sampleRate | number|null | yes | – |
| sizeBytes | number | yes | – |
| videoCodec | string|null | yes | – |
No examples provided.
validate_template Validate Template ~72
Dry-run an inline `template` descriptor against the core schema WITHOUT rendering — returns instantly. Get back whether it is valid plus what compose_video will require: the project_video clip sections and the form fields. Use this to iterate on a descriptor in milliseconds before the slower compose_video render.
| Name | Type | Req | Description |
|---|---|---|---|
| template | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| formFields | array | yes | – |
| orientation | string|null | yes | – |
| requiredClips | array | yes | – |
| sectionCount | number | yes | – |
| valid | boolean | yes | – |
No examples provided.
What is the LeClap MCP server?
LeClap is an MCP server listed in the public MCP registry as dev.leclap/video. Compose and render video from one JSON template. Deterministic, runs locally, no generative model. This page covers its npm package (@leclap/mcp).
Is the LeClap MCP server safe to use?
LeClap scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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 LeClap MCP server expose?
LeClap exposes 5 tools: ping, get_template_schema, validate_template, compose_video, probe_media. Their descriptions and schemas cost roughly 301 tokens of context every time the server is loaded.
Is the LeClap MCP server still maintained?
LeClap is still listed as active in the MCP registry. We last reached this channel on 22 September 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 LeClap MCP server under?
LeClap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.