# rendercheck (pypi · rendercheck)

Check generated audio, video and stills for defects. Returns a verdict, not more media.

- Trust score: 80/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `rendercheck`: 80/100 (this document), [markdown](https://verifymcp.io/servers/rogermsc-rendercheck/rendercheck.md), [page](https://verifymcp.io/servers/rogermsc-rendercheck/rendercheck)

## Channel facts

- Registry: `pypi`
- Package: `rendercheck`
- Version: `0.4.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 45 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add rogermsc-rendercheck -- uvx rendercheck
```

### Cursor

```json
{
  "mcpServers": {
    "rogermsc-rendercheck": {
      "command": "uvx",
      "args": [
        "rendercheck"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "rogermsc-rendercheck": {
      "command": "uvx",
      "args": [
        "rendercheck"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add rogermsc-rendercheck -- uvx rendercheck
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rogermsc-rendercheck": {
      "type": "local",
      "command": [
        "uvx",
        "rendercheck"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add rogermsc-rendercheck --command uvx --arg rendercheck
```

### Hermes

```yaml
mcp_servers:
  rogermsc-rendercheck:
    command: "uvx"
    args: ["rendercheck"]
```

### Netclaw

```json
{
  "McpServers": {
    "rogermsc-rendercheck": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "rendercheck"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add rogermsc-rendercheck -t stdio -c uvx -a rendercheck
```

### Other

```json
{
  "mcpServers": {
    "rogermsc-rendercheck": {
      "command": "uvx",
      "args": [
        "rendercheck"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 80, −3)

- [functional] Stability: pass → 0.80

### 2026-09-19 (score 83, +15)

- [security improvement] Malware scan: unverified → pass
- [security] Stability: 0.97 → pass

### 2026-09-18 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 67, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-16 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 66, −14)

- [security regression] Malware scan: pass → unverified

### 2026-09-13 (score 80, −3)

- [functional] Stability: pass → 0.80

## MCP tools (2)

### `check_media` (~444 tokens)

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.

Input parameters:

- `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, required): 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.

### `list_checks` (~37 tokens)

What check_media can look for, what each one costs, and the loudness presets available. Call this to decide which arguments are worth supplying.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/rogermsc-rendercheck/rendercheck#diagnostics

## Score history

- 2026-09-20: 80
- 2026-09-19: 83
- 2026-09-18: 68
- 2026-09-17: 67
- 2026-09-16: 82
- 2026-09-15: 81
- 2026-09-14: 66
- 2026-09-13: 80
- 2026-09-12: 83
- 2026-09-11: 83
- 2026-09-10: 82
- 2026-09-09: 82
- 2026-09-08: 81
- 2026-09-07: 81
- 2026-09-06: 80
- 2026-09-05: 83
- 2026-09-04: 83
- 2026-09-03: 82
- 2026-09-02: 82
- 2026-09-01: 81
- 2026-08-31: 81
- 2026-08-30: 80
- 2026-08-29: 80
- 2026-08-28: 79
- 2026-08-27: 79
- 2026-08-26: 78
- 2026-08-25: 76
- 2026-08-24: 76
- 2026-08-23: 76
- 2026-08-22: 75

## Common questions

### 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 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 20 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 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.

## Links

- PyPI project: https://pypi.org/project/rendercheck/
- Socket report: https://socket.dev/pypi/package/rendercheck
- Repository: https://github.com/rogermsc/rendercheck
- Changelog RSS feed: https://verifymcp.io/servers/rogermsc-rendercheck/rendercheck.xml
- Changelog JSON feed: https://verifymcp.io/servers/rogermsc-rendercheck/rendercheck.json
- HTML version of this page: https://verifymcp.io/servers/rogermsc-rendercheck/rendercheck