IAMF Sentinel logo

IAMF Sentinel

Validates IAMF files and compiles or optionally runs Loom packaging manifests through MCP.

Install IAMF Sentinel

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "iamf-sentinel": {
      "command": "uvx",
      "args": [
        "iamf-sentinel-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

IAMF Sentinel MCP server exposes IAMF conformance validation and Loom packaging workflows through MCP tools. It can inspect `.iamf` or IAMF-in-MP4 files, produce conformance findings, and compile YAML or JSON manifests into deterministic packaging plans. By default, the server is read-only and does not execute commands or write files; launching it with `--enable-run` also registers a tool that runs encoding, muxing, measurement, and validation. Use it when an agent needs IAMF structure checks, packaging diagnostics, or opt-in end-to-end output gating.

Use cases

  • Validate IAMF files against conformance rules
  • Inspect IAMF and MP4 stream structure
  • Compile Loom manifests into packaging plans
  • Review target backend and muxer routing
  • Run and gate packaged outputs with opt-in execution

Key features

  • IAMF conformance reports with S-code findings
  • IAMF and MP4 structural inspection
  • Loom manifest compilation and explanations
  • Optional encoding, muxing, measurement, and gating
  • S-code, M-code, and failure-mode catalogs

Tools5

What IAMF Sentinel lets your agent do. Expand a tool for its parameters.

Self-reported~209 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · iamf-sentinel-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit20d agoMost recent push to the default branch.
Tools exposed5Callable tools this server registers over MCP.

How IAMF Sentinel works

What IAMF Sentinel MCP server does

The IAMF Sentinel MCP server connects MCP clients to two underlying projects: iamf-sentinel, which validates IAMF content, and iamf-loom, which packages IAMF according to a manifest. It is intended for agent workflows that need inspectable validation results or packaging decisions rather than a general-purpose media editor.

Validation accepts .iamf files and IAMF stored in MP4. The server can return S-code findings with severities, a summary, and stream facts. A strict validation option treats warnings as failures. Inspection is separate from conformance checking and reports structural details such as profiles, codec configuration, Opus pre-skip, element and presentation counts, frame counts, OBU trim totals, and MP4 edit-list information.

Loom operations accept YAML or JSON manifests. Compilation is validation-only and reports target-specific backend and muxer routing with its rationale, or M-code diagnostics when the manifest cannot be compiled.

How it works

The IAMF Sentinel MCP server runs as a Python command-line MCP service over stdio. Its default launch exposes parsing, validation, and plan-generation operations without executing an encoder toolchain. loom_explain presents the compiled plan as explanatory text, allowing an agent or developer to review the packaging decisions before any run is attempted.

The optional loom_run operation combines compilation and execution. It encodes and muxes the requested targets, measures them, and sends every output through the Sentinel validator. Results include per-target output paths and SHA-256 values, gate verdicts, measured loudness, and the path to the run ledger. This operation is registered only when the process starts with --enable-run.

Setup and configuration

Install the package with pip, then start the default read-only service:

Terminal
pip install iamf-sentinel-mcp
iamf-sentinel-mcp

To expose execution, start it explicitly with:

bash
iamf-sentinel-mcp --enable-run

An MCP client can launch the command as its server process. For Claude Desktop or Claude Code, the configuration uses the command iamf-sentinel-mcp under an MCP server entry. No environment variables are specified in the provided setup material.

Tools and capabilities

The IAMF Sentinel MCP server provides these tools:

  • iamf_validate: Produces a full conformance report, including S-code findings, severities, summaries, and stream facts. strict promotes warnings to failing results.
  • iamf_inspect: Reports IAMF and MP4 structure for orientation and troubleshooting.
  • loom_compile: Validates a Loom manifest and returns its packaging plan, target routing, or M-code diagnostics.
  • loom_explain: Returns the compiled plan as text with its justification.
  • loom_run: Executes the compiled workflow when enabled at launch, then measures and gates each output.

The server also exposes catalogs for S-code checks, M-code compile diagnostics, and the failure-mode register through checks://catalog, mcodes://catalog, and fregister://catalog.

Limitations and notes

Read-only mode performs no execution, file writes, or network access. Enabling loom_run changes that posture: it invokes encoder subprocesses and writes output files. The required encoder toolchain must be available; a missing binary produces an actionable error. The Sentinel gate remains enabled for runs, while rendered-loudness L3 quality control is not exposed.

The package is a thin MCP wrapper; core conformance and packaging behavior belongs to iamf-sentinel and iamf-loom. IAMF v2.0.0 streams can be read, including object-based elements and v2 rendering settings, but positions over time and parameter blocks remain unvalidated. The package is licensed under Apache-2.0.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about IAMF Sentinel

IAMF Sentinel is an MCP server that connects agents to the iamf-sentinel validator and iamf-loom packager. Its main tools validate and inspect IAMF files, compile and explain Loom manifests, and optionally run packaging workflows with loom_run when launched using --enable-run.

Install it with pip using `pip install iamf-sentinel-mcp`, then launch `iamf-sentinel-mcp`. The default process uses stdio transport and exposes read-only validation, inspection, and manifest-planning tools.

Start the server with `iamf-sentinel-mcp --enable-run`. This registers `loom_run`, which invokes the encoder toolchain, muxes and measures outputs, and gates each result through the Sentinel validator.

Yes, IAMF Sentinel can be configured for Claude Desktop by launching the `iamf-sentinel-mcp` command in the client's MCP server configuration. Claude Code is also named as a supported client in the project documentation.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewIAMF Sentinel AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/iamf-sentinel?style=directory)](https://allmcps.com/mcp/iamf-sentinel)
HTML Embed
<a href="https://allmcps.com/mcp/iamf-sentinel"><img src="https://allmcps.com/api/badge/iamf-sentinel?style=directory" alt="IAMF Sentinel on AllMCPs" /></a>