VOOPA Render Check
Review generated images and videos against a brief before deciding whether to rerender.
Serveur MCP hébergé
npx add-mcp 'https://voopa-render-check.onrender.com/mcp'S’installe dans Claude Code, Codex, Cursor et plus
Documentation
VOOPA Render Check
Experimental motion checks
check_black_gaps flags almost-black passages lasting at least 0.3 seconds in a selected 1–120 second range, returning timestamps in the original video for human review. Intentional fades and dark scenes can be flagged; brief flashes and partial-frame defects may be missed. It does not determine intent or authorize a rerender. For videos over two minutes, select subsequent ranges explicitly.
For brief suspected gaps, optionally set minimumDurationSeconds from 0.1 to 3 seconds; the default is 0.3. Shorter thresholds can flag intentional transitions, and very short gaps or partial-frame defects may still be missed.
To try it without sharing a private clip, call check_black_gaps with renderVideoUrl set to https://raw.githubusercontent.com/Voopa-Corp/render-check/main/black-gap-demo.mp4. This synthetic example deliberately contains black frames from 3 to 4 seconds. The hosted preview is free and rate limited.
Try the repeated-shot scanner on a reproducible demo. Use the repeated-shot workflow in n8n.
scan_repeated_shots is an experimental opt-in scan for visually similar two-second passages within a selected 4–60 second range. For a longer video, the default is its first 60 seconds; pass fromSeconds and durationSeconds to scan another section. Timestamps refer to the original video, but repeats across different scan sections will be missed. It lists possible low-motion matches separately (at most five, in addition to at most ten other candidates); a match may be intentional, and a clear result does not rule out repeats. Crops, altered speed, color and transitions can be missed. Review suggested ranges in motion. The scanner does not assess audio or intent, and never approves another render.
Agents can use check_full_frame_freeze to flag nearly unchanged full frames, or a caller-selected fixed rectangle, within a selected range of up to 120 seconds. For longer videos, the default is the first 120 seconds; select another range with fromSeconds and durationSeconds. check_repeated_sequence compares two specified 2–8 second ranges for visual similarity. Both return candidates for review, not a creative verdict. Static shots may be intentional; camera motion, cuts, similar scenes, altered crops and occlusion can cause misleading results. The selected rectangle does not track an object. Neither tool verifies steam, audience behavior, sound, lyrics or lip sync, and a clear result does not establish that the video is correct.
compare_reference_audio experimentally compares up to 15 seconds of a video soundtrack with the corresponding part of an approved recording. Set videoFromSeconds and referenceFromSeconds to choose where each section begins; both default to zero. It reports waveform similarity and an approximate offset within a half-second search range for human review. Mixing, cuts, different excerpts or effects may reduce similarity; a high score does not establish that the reference is correct, that no extra sounds are present, or that visible lips are synchronized. The comparison abstains when audio is too quiet and notes inverted polarity. It cannot identify missing car sounds or other events. Supported references are direct WAV, MP3, M4A or FLAC files up to 20 MB; both selected intervals must contain at least two seconds of audio. The result always requires review and never approves another paid render.
Your video is a signal. Render Check is a Signal Labs tool that an agent can call after a generated video misses its brief and before anyone pays for another take. It returns timestamped evidence and recommends whether to edit the take, try one specific change, switch approach, or review the evidence again.
The preview uses the calling host’s visual review or its reviewer’s observations. The same review works with completed videos from fal, Higgsfield, Runway and Replicate, and with local exports from editors such as Tunee.
Connect to the hosted preview
Use https://voopa-render-check.onrender.com/mcp as a Streamable HTTP MCP endpoint. The preview is free and rate limited. The first request after inactivity can take about a minute. The service checks expected audio when supplied and returns frames for the calling agent to interpret against the brief.
Bring it to your workflow. Import the n8n template and run the included example without making a generation. Or add the same server to Claude Code:
claude mcp add --transport http render-check https://voopa-render-check.onrender.com/mcp
Use the workflow guide for the fields to pass after a render, or the MCP Registry listing for the connector details.
Use Render Check after generation
Connect the server and add the pre-retry step to your agent workflow. The guide shows how to pass each provider’s completed result and opt into an audio check.
Run the preview
Requirements are Node.js 22 or later and FFmpeg with ffprobe. Run:
npm ci
npm test
npm run mcp:http
The test generates its own one-second clip. The server listens at http://127.0.0.1:50951/mcp and accepts only local connections. For a process-based MCP host, launch node /absolute/path/to/mcp.mjs instead.
Pass a supported direct HTTPS media URL as renderVideoUrl, or pass the filename of an authorized local clip in the intake folder as file. Existing fal clients can still use falVideoUrl. The service removes temporary downloads after inspection. The check uses no generation credits.
Connect a workflow
| Host | Connection route |
|---|---|
| Claude | The Claude API MCP connector can reach hosted HTTPS servers. For a local coding workflow, configure the server in Claude Code. Claude MCP connector |
| Mistral | Mistral Studio can register a hosted MCP server as a connector for conversations and agents. Mistral connectors |
| Qwen | Qwen-Agent supports Streamable HTTP MCP. Connect through the agent runtime. Qwen-Agent releases |
| Other models | An MCP-capable agent host can list and invoke the tools. A host that exposes model function calling can bridge those calls to MCP. Image review needs a vision-capable model or reviewer. |
The test verifies the MCP protocol with an independent client. The hosted provider integrations above are documented routes and still need live verification.
Tell the agent when to use it
When a paid video take misses the brief, use VOOPA Render Check before proposing another generation. Reuse the existing clip, prompt, and attempt history. Show the timestamp and one actionable recommendation in chat. Hold spending if the evidence is unclear.
Start with review_completed_render. Give it the clip or the video.url from the fal result, the must-haves, and prior attempts. A compatible process-based host can use model sampling. Over the local HTTP preview the host receives frames and calls decide_render_retry with its observations. Text-only hosts can use trusted observations supplied by a reviewer or separate vision component.
What this preview proves
The same tool interface works over local process and Streamable HTTP connections. The included smoke test exercises an inspect-and-decide flow without credentials or generation costs. The policy and evidence can be tested independently of a specific model. Nothing in the tool starts a render or authorizes spending.