rendercheck
PYPI · RENDERCHECK
Check generated audio, video and stills for defects. Returns a verdict, not more media.
Available components
Last scanned (4 hours ago)
Scores higher than 96% of PyPI servers
Category Testing and QA
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to rogermsc/rendercheck). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 91 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 481 tokens (~240/item across 2 items; 2 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 0
- Stability: pass → 0.97 functional
- 18 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
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 5 Nov 2026 · Analysed pypi/rendercheck@0.4.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | rogermsc/rendercheck |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/rogermsc/rendercheck/.github/workflows/release.yml@refs/tags/v0.4.1 |
| Rekor log index | 2351978518 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:30ae30a01504c23e171e15791a575f1d2b202e7494f390ee723a179ea9c55406 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
check_media ~444
Check a generated audio or video file for the defects that do not raise an error: narration pace, loudness, true peak, dead air, truncated endings, clipping, black or frozen video, sound and picture that do not line up, and captions that do not match the audio. Returns one verdict per check with the measured value. Run this after any step that produces media -- a render that failed silently is indistinguishable from one that worked until something measures it.
| Name | Type | Req | Description |
|---|---|---|---|
| captions | string | – | A .vtt or .srt to check against the audio. Found automatically if it sits beside the media under the same name. |
| expect_channels | number | – | Channel count the delivery spec asks for: 1 mono, 2 stereo. |
| expect_fps | number | – | Frame rate the render was asked for. Also catches variable frame rate, a standard cause of audio drifting against picture. |
| expect_height | number | – | Picture height the render was asked for, in pixels. |
| expect_sample_rate | number | – | Audio sample rate the delivery spec asks for, in Hz. |
| expect_width | number | – | Picture width the render was asked for, in pixels. |
| expected_seconds | number | – | How long the render was supposed to be. |
| known_names | array | – | Every presenter who could really have been cast. Required alongside presenter: without it a character in a scenario saying 'I'm Rosa' trips the check on every script that tells a story. |
| path | string | yes | Media file to check. A directory checks what is inside it. |
| presenter | string | – | Who is supposed to be narrating. Enables the speaker check, which needs known_names as well. |
| preset | string | – | Loudness target for wherever this file is going. |
| rubric | array | – | Statements a still must satisfy, e.g. 'the title fits on one line'. Enables the vision check, which needs an API key. |
| script | string | – | Narration text, or a path to a transcript/.vtt/.srt. Enables the pace check. |
| strict | boolean | – | Count a check that could not run as a failure. |
No output schema declared.
No examples provided.
list_checks ~37
What check_media can look for, what each one costs, and the loudness presets available. Call this to decide which arguments are worth supplying.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the rendercheck MCP server?
rendercheck runs locally as a PyPI package, launched with uvx rendercheck. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · rendercheck
claude mcp add rogermsc-rendercheck -- uvx rendercheck
What is the rendercheck MCP server?
rendercheck is an MCP server listed in the public MCP registry as io.github.rogermsc/rendercheck. Check generated audio, video and stills for defects. Returns a verdict, not more media. This page covers its PyPI package (rendercheck).
Is the rendercheck MCP server safe to use?
rendercheck scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 rendercheck MCP server expose?
rendercheck exposes 2 tools: check_media, list_checks. Their descriptions and schemas cost roughly 481 tokens of context every time the server is loaded.
Is the rendercheck MCP server still maintained?
rendercheck is still listed as active in the MCP registry. We last reached this channel on 5 November 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 rendercheck MCP server under?
rendercheck declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.