MCP.Market

loudcheck MCP server

by chaoz23·io.github.chaoz23/loudcheck·v0.3.1·1 stars

Loudness compliance verdicts (EBU R128, ATSC A/85): pass/fail with exact ffmpeg remediation.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

1 stars29 downloads/wk

Reviews

Write one

Nobody has reviewed loudcheck yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

loudcheck tools (2)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • check_loudness

    Loudness compliance verdict for a media file against a formal published standard. Measures integrated loudness, loudness range, and true peak (via ffmpeg), then evaluates them against the named standard's targets and tolerances.

  • list_standards

    List the standards this tool can verdict against, with their targets, tolerances, and spec citations.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan8 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 48 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How loudcheck compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Tools
2
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
29
more than 16% of 12,191 servers with a package

What its tools let an agent do: 2 read

Install loudcheck in Claude Code, Cursor or VS Code

claude mcp add loudcheck -- uvx loudcheck
Add to Cursor

What the publisher says

From the loudcheck repository's README, as published. We do not edit it. Read it on GitHub

loudcheck

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.

mode returns verdict measured with the numbers and no judgment)

  • 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
$ loudcheck master.wav --standard EBU_R128
FAIL — EBU R 128
  ✗ integrated -19.4 LUFS (target -23.0 ±0.5, delta +3.6)
  ✓ true peak -16.3 dBTP (max -1.0)
  · LRA 0.0 LU (informational)
  → apply -3.6 LU gain to reach -23.0 LUFS (e.g. ffmpeg -af volume=-3.6dB, or loudnorm I=-23)

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.

uvx loudcheck file.wav          # zero-install run (requires ffmpeg >= 5.0 on PATH)
pip install loudcheck           # CLI
pip install "loudcheck[mcp]"    # + MCP server

From a clone: pip install -e ".[mcp,dev]".

CLI

loudcheck file.wav                          # EBU R128 by default
loudcheck file.mp4 --standard ATSC_A85      # first audio stream of a video
loudcheck file.wav --json                   # full structured verdict
loudcheck file.wav --standard BS_1770       # measurement only, no gates
loudcheck file.mov --all-streams            # verdict every audio track
loudcheck file.mov --stream 1               # a specific audio track
loudcheck file.wav --detailed               # + max momentary / short-term
loudcheck masters/ --standard EBU_R128      # batch a directory -> table
loudcheck a.wav b.wav c.wav                 # batch multiple files
loudcheck --schema                          # print the tool definition

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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

loudcheck: common questions

Is loudcheck MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the loudcheck safety report
How do I install loudcheck?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does loudcheck need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is loudcheck maintained?
The last commit was 87 days ago (2026-08-09). The latest release is v0.3.1.
How does loudcheck compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from chaoz23 →