- Reliability 9/20
- Static evidence: the README claims a CI workflow (.github/workflows/ci.yml) running lint→test→build, claims 1170+ Vitest cases plus Playwright E2E, and documents pnpm pack/dist desktop packaging; the manifest is internally consistent (stdio transport, npm package [email protected], matching versions, all env vars optional with stated defaults) and shows no contradictions. However, this review only has README/manifest text: no committed CI definition, no test files, no tool list or handler source for the MCP server beyond mcp/server.json. Tool declarations cannot be verified against real behavior, the init/tool-list handshake cannot be confirmed, and error/dependency controllability is unproven. Capped at 12 per the static calibration and reduced further for missing verifiable key-path evidence (initialization, failure modes, retry/timeout semantics).
- Security and permissions 10/20
- No red line is tripped: no malware, credential theft, covert exfiltration, or unconfirmed irreversible delete/pay/deploy/remote-command defaults. Credential handling is relatively restrained: CLIPFORGE_LLM_API_KEY is marked isSecret=true and is optional, and CLIPFORGE_BASE_URL defaults to localhost:3000, indicating a local-only default; the README emphasizes self-hosting and data staying on-device. Deductions: the server drives a pipeline with paid model calls, FFmpeg composition, external stock/TTS endpoints, and product-link fetching, so the capability surface includes meaningful external network access and side effects, while the materials provide only README prose (no source) for per-tool scope restrictions, pre-spend confirmation, SSRF protections, and download/write boundaries. Fetching product URLs and downloading third-party media to local disk are concrete data flows and write side effects that the manifest does not constrain.
- Maintenance 14/20
- Evidence: not archived, 0 open issues, semantic version 0.1.4 with a clear per-release note trail, README documenting a v0.8.9x–v0.9.4 iteration history including specific fixes for issues #24 and #28, indicating ongoing defect response and release cadence; AGPL-3.0 license is explicit, the author and sibling projects (Dramake, HotClip) are traceable, and automated image builds via GitHub Packages/CI are claimed. Deductions: stars/popularity are discovery signals only and add nothing; despite the issue-fix narrative there is no visible security-response channel, contributor governance, dependency-update policy, or release-verification artifact; the manifest version (0.1.4) conflicts with the feature versions cited in the README (v0.9.4), indicating muddled version governance.
- Documentation 13/20
- Documentation is large and layered: bilingual README, TUTORIAL.md/TUTORIAL.en.md step-by-step guides, a CLI command list with per-command parameters, a cost section giving concrete model pricing and the resolution cost multiplier (1080p ≈ 4.5x baseline), a compliance section covering AIGC labeling and ad-law terms, FAQ on the free path and watermarking/commercial use, plus mcp/README.md and skills/README setup prompts. Deductions: server-side MCP documentation in this material is thin — the manifest lists only environment variables, with no tool names, parameters, response shapes, or timeout/failure semantics; installation instructions lean heavily on external links and skill files; the assumption that a ClipForge instance must already be running (default localhost:3000) is stated but buried deep in the main document, so limits on standalone server usability are under-disclosed.
- Setup experience 12/20
- The install path is clear and short: a single docker run brings the service up on port 3000 with a keyless first video, and the clipforge-mcp npm package uses stdio with no auth and all-optional env vars carrying defaults, so client wiring only needs CLIPFORGE_BASE_URL pointing at the local instance. Deductions: usability depends on the app being started first (pnpm dev / pnpm start or Docker), so the MCP server is not self-contained — an implicit prerequisite; local development mandates pnpm (README states npm install errors out) and a user-installed FFmpeg; no per-client config snippet (Claude Desktop / Cursor, etc.) is provided. Per the calibration rule setup is capped at 15 absent verifiable execution evidence, and is further reduced for the hidden prerequisite and the missing client configuration examples.