Skip to main content
Glama

Related Servers

Alternatives to loudcheck

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to compare a processed audio file against its reference and report how much perceptual quality was lost, using PEAQ ODG, ViSQOL MOS-LQO and an optional licensed POLQA binary, plus waveform, loudness and Bark-band spectral metrics. Runs headless over stdio, installs itself with uv, and returns rankings across codecs or bitrates.
      GPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Measures audio files and stems, then returns DAW-neutral mixing and mastering action plans with typed answers and ordered recipes. Enables automated analysis of loudness, true peak, phase, masking, and spectral balance to decide corrective EQ, dynamics, limiting, and loudness targets.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Turns silent defects in AI-generated video and audio — wrong speaking pace, mismatched loudness, truncation, dead air, late captions, broken layout — into hard assertion failures inside tests and CI. Enables agents to check individual files or whole output directories against platform presets, returning pass/fail exit codes and human-readable bug reports instead of raw measurements.
      23 PyPI
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to measure a track's loudness and peak levels, strip artifacts left by AI generators, compare mastering presets, and master single tracks or batches to streaming targets via a hosted remote server or a local stdio bridge. Tracks are supplied as public HTTPS links, with analysis, cleanup and previews free and full masters limited by a daily free quota or credits.
      9
      MIT

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one checks loudness against a standard, the other lists available standards. No overlap in functionality.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern: check_loudness and list_standards. The naming is predictable and clear.

    Tool Count3/5

    With only 2 tools, the server is on the low end of the typical range. While the tools cover the core functionality, a batch processing tool or a tool to preview raw measurements would round out the set.

    Completeness4/5

    The server covers the main use case of loudness checking and provides standards listing. Minor gaps exist, such as batch processing or the ability to update standards, but the core workflow is complete.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive