Ext Ops Panel
Open dashboard
Comparison

app.uploadcheck/uploadcheck vs rendercheck

app.uploadcheck/uploadcheck is an MCP server published by uploadcheck.app. Marketplaces we read that list it: 1 (Official MCP Registry). rendercheck is an MCP server published by rogermsc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceapp.uploadcheck/uploadcheckrendercheck
Official MCP Registry Listed
Version: 0.1.1
Downloads/month (npm): 183
Downloads/week (npm): 36
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.4.1
Downloads/month (PyPI): 110
Downloads/week (PyPI): 44
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

app.uploadcheck/uploadcheck vs rendercheck
Factapp.uploadcheck/uploadcheckrendercheck
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@drantoniou/uploadcheck-mcp)On your machine (rendercheck)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/ajantoniou/uploadcheck-mcpgithub.com/rogermsc/rendercheck
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

app.uploadcheck/uploadcheck

In its own words, on Official MCP Registry:

QC videos, podcasts, and clips before upload — timestamped flags with agent-ready repair prompts.

rendercheck

In its own words, on Official MCP Registry:

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

How to run each

app.uploadcheck/uploadcheck As a local MCP server: npm package

Claude Code
claude mcp add --env "UPLOADCHECK_API_BASE_URL=<YOUR_UPLOADCHECK_API_BASE_URL>" --env "UPLOADCHECK_API_KEY=<YOUR_UPLOADCHECK_API_KEY>" --transport stdio uploadcheck -- npx -y @drantoniou/uploadcheck-mcp

Requires: UPLOADCHECK_API_BASE_URL, UPLOADCHECK_API_KEY (secret)

rendercheck As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --transport stdio rendercheck -- uvx rendercheck mcp

Requires: ANTHROPIC_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only app.uploadcheck/uploadcheck asks for

  • UPLOADCHECK_API_BASE_URL
  • UPLOADCHECK_API_KEY (secret)

Only rendercheck asks for

  • ANTHROPIC_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: app.uploadcheck/uploadcheck · What it can do: rendercheck · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built