Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/cudgk/ffmpeg-mcp/ffmpeg-mcpgit clone --depth 1 https://github.com/cUDGk/ffmpeg-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/cudgk/ffmpeg-mcp/ffmpeg-mcp)<a href="https://agentmods.dev/mcp/cudgk/ffmpeg-mcp/ffmpeg-mcp"><img src="https://agentmods.dev/badge/mcp/cudgk/ffmpeg-mcp/ffmpeg-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ffmpeg-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to ffmpeg-mcp — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{ "ffmpeg-mcp": { "command": "npx", "args": [ "-y", "ffmpeg-mcp" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 9 lines scan A 76594c71b204
ffmpeg-mcp is an MCP server published in the GitHub repository cUDGk/ffmpeg-mcp (0 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It is 100% identical to ffmpeg-mcp, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
video-probe-mcp
MCP server "video-probe-mcp" as configured in dvnc-labs/video-probe-mcp. Runs locally from the video-probe-mcp npm package.
video
Compose and render video from one JSON template. Deterministic, runs locally, no generative model. Runs locally from the @leclap/mcp npm package. Needs 5 environment variables to run.
gemini-audio-mcp
MCP server "gemini-audio-mcp" as configured in jxoesneon/gemini-audio-mcp. Runs in Docker (ghcr.io/jxoesneon/gemini-audio-mcp:0.1.0). Needs 1 environment variable to run.
loudcheck
Loudness compliance verdicts against formal published standards (EBU R128, ATSC A/85) — a pass/fail answer with exact deltas, not raw meter output. Runs locally from the loudcheck Python package.
openmedia-mcp
MCP server "openmedia-mcp" as configured in Builderstar/openmedia-mcp. Runs locally from the openmedia-mcp Python package.
media-context-mcp
Local MCP server to analyze video, audio & images: frames, transcripts, on-screen text. Runs locally from the media-context-mcp npm package.