技能潮 SkillTide 提交收录
官方说明7 个来源MCP 服务8 天前
chaoz23/loudcheck

chaoz23/loudcheck

Check media file loudness against EBU R12
在 GitHub 查看 ↗直链 · 无中转页
配置模板(请按你的客户端调整)
claude mcp add loudcheck -- npx -y loudcheck
这是根据仓库名生成的可粘贴骨架,命令行参数与包名请以该项目 README 为准。
★ 数取值
1 ★ · chaoz23/loudcheck · 取自 GitHub 搜索 API · (2026-10-16 20:00:20 核对)
来源明细
收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
收录与活跃
收录于 2026-10-09 · 最近见到 2026-10-16 · 共见到 32 次 · 被 7 个来源列出
评分构成
综合分 703 · 1 ★ · 7 个来源 · mcp
常见问题(答案都来自我们的记录)
怎么安装?
我们【没有】从该仓库取到安装命令(我们的 install 覆盖率只有约 4%)。请看它的 README 或 releases 页。
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库 chaoz23/loudcheck;我们收录于 2026-10-09;最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
第三方质量标记

loudcheck

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

A **loudness compliance verdict**, not raw meter output. loudcheck measures
a media file with ffmpeg and answers the question that actually matters —
*does this file pass the spec?* — against formal published standards:
**Agents start here → SKILL.md** — when to call this, worked examples, MUST/MUST NOTs. Family contract: FAMILY.md.
- **EBU R 128** (European broadcast: −23.0 LUFS ±0.5 LU, max −1 dBTP)
- **ATSC A/85** (US television: −24 LKFS ±2 dB, true peak below −2 dBTP)
- **BS.1770** (measure-only: BS.1770 defines no compliance target, so this
mode returns verdict measured with the numbers and no judgment)
Ships as a CLI and an MCP tool over one engine, so agents and humans get the
identical verdict.
Why this exists
An agent (or an engineer) can run ffmpeg's ebur128 filter and get numbers.
What it can't get from a shell is the *verdict* — that requires knowing the
standard's target, tolerance, and gating, and interpreting integrated
loudness vs. LRA vs. true peak against them. Loudness is one of the most
common causes of delivery rejection, and the gap is not measurement — it's
the standards-aware answer. That's the whole tool.
Install
Requires Python 3.10+ and ffmpeg 5.0+ on PATH.
From a clone: pip install -e ".[mcp,dev]".
CLI
Batch mode prints one line per file (plus remediation for fails) and a
summary; --json in batch emits an array. Exit code is 1 if *any* file
fails.
For agents
- **Exit codes carry the verdict:** 0 = pass, 1 = fail (non-compliant),
2 = error (missing file, no audio stream, no ffmpeg). Gate a delivery on
the exit code alone.
- **--json is the full contract:** overall verdict, per-metric
measured/target/tolerance/delta/pass with the spec citation attached to
every gated metric, failures in plain English, and remediation with the
**exact correction** — a fail 2.3 LU over target tells you to apply
−2.3 LU gain and hands you the ffmpeg incantation. This tool never applies
the fix (measurement and verdict only); the agent one-shots it with
loudnorm using the delta provided.
- **MCP:** register loudcheck-mcp (stdio; or loudcheck --mcp, or
python -m loudcheck.mcp_server). Zero-install:
uvx --from 'loudcheck[mcp]' loudcheck --mcp. Tools:
check_loudness(path, standard) → same JSON as the CLI, and
list_standards() → the catalog with citations. Verified against
mcp==1.28.1.
- **tool.json** at the repo root describes the surface machine-readably —
or fetch it live from any install with loudcheck --schema (the file ships
inside the package; a test keeps the two copies in sync).
- **ffmpeg version is part of the contract:** every verdict includes
measurement_context.ffmpeg_version. Minimum supported: 5.0. Developed and
verified against 8.1.
The scope guardrail (read before contributing)
**Only formal, stable standards live in this repo; per-platform delivery
templates (Netflix, DPP, Apple TV+, Amazon, broadcaster specs) never do.**
Platform specs change unilaterally and cover far more than loudness — the
来源
awesome · https://github.com/chaoz23/loudcheck
按领域浏览
MCP 服务
Traction
1 ★
收录于
昨天

更多MCP 服务

查看MCP 服务全部 5,525 条 →

所属领域与标签

每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。

浏览全部领域 →

← 返回索引