IAMF Sentinel

io.github.jlivingston-Cipher由 GitHub 帳號 jlivingston-Cipher 發布v0.2.4更新於 Oct 24, 2026

MCP server for the iamf-sentinel IAMF conformance validator and the iamf-loom packager

已驗證STDIO僅桌面開發者工具媒體與設計

概覽

AI 產生的概覽

封裝 iamf-sentinel IAMF 一致性驗證器與 iamf-loom 打包器,讓助理驗證沉浸式音訊檔案並編譯打包方案。

可以做什麼
  • 驗證 IAMF 檔案並檢視其結構、profile、編解碼設定與影格數
  • 依 Dolby 交付規範與 ADM Profile 規則檢查 ADM BWF 母帶與專輯
  • 將 Loom 打包清單編譯為方案,提供後端路由或診斷資訊
  • 以文字形式解釋已編譯的方案
  • 在加上 --enable-run 啟動時端對端執行清單(編碼、封裝、量測、驗證)
  • 讀取驗證項目錄、編譯診斷目錄與故障模式登錄表
適用情境
適合處理 Alliance for Open Media 的 IAMF 沉浸式音訊:判斷檔案是否符合規範、了解其結構、評估 ADM BWF 母帶,或在正式算圖前把 Loom 清單轉成打包方案。
執行需求
需在本機以 pip 安裝 Python 套件 iamf-sentinel-mcp,以 stdio 執行,僅限桌面用戶端。需要可用的驗證器與打包器產品,ADM 檢查還要求 iamf-sentinel 具備 adm-check。執行清單另需編碼工具鏈並以 --enable-run 啟動。
安裝前請注意
預設唯讀,但以 --enable-run 啟動會註冊 loom_run,它會以子程序方式執行編碼工具鏈並寫入檔案,僅在確實要算圖時啟用。此執行路徑未在 CI 中驗證,缺少工具鏈時會報錯。算圖響度 QC 未對外提供。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 IAMF Sentinel,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

iamf-sentinel-mcp

An MCP server exposing iamf-sentinel (IAMF conformance validator) and iamf-loom (IAMF packager) to MCP clients — Claude Desktop, Claude Code, and any other agent runtime that speaks the protocol.

IAMF is the Alliance for Open Media's Immersive Audio Model and Formats (v1.1.0). The validator behind this server also reads IAMF v2.0.0 streams, recognises its six profiles and checks their limits, and reads object-based elements and the v2.0.0 rendering settings and checks them; positions over time and parameter blocks remain unvalidated. This server lets an agent validate IAMF files against the spec's conformance rules and compile packaging manifests into inspectable, deterministic plans — without executing anything (execution is a separate, per-launch opt-in — see below).

Code comments throughout cite an internal numbered design docset (doc NN), ADRs, and pre-registered expectation labels — DESIGN-NOTES.md explains the notation and indexes every cited document.

Tools

ToolWhat it doesNeeds toolchain
iamf_validateFull conformance report on a .iamf / IAMF-in-MP4 file: S-code findings with severities, summary, stream facts. strict promotes WARN to failing.no
iamf_inspectStructure orientation: profiles, codec configs (incl. Opus pre-skip), element/presentation/frame counts, OBU trim totals, MP4 edts/elst presence.no
adm_checkJudge ADM BWF masters (files or folders, albums with album, gapless albums with gapless) against Dolby's Music Master Delivery Specification v2022.07 and ADM Profile v1.1: every rule PASS, FAIL, WARN or UNDETERMINED, with what was measured, what is required and how to fix it. Reads metadata only; needs an iamf-sentinel with adm-check.no
loom_compileCompile a Loom manifest (YAML/JSON) to its packaging plan — validate-only. Per-target backend/muxer routing with rationale, or M-code diagnostics.no
loom_explainloom explain as text: the compiled plan as its own justification.no
loom_runCompile and execute a manifest: encode, mux, measure, and gate every output through the Sentinel validator. Returns per-target outputs (sha256), gate verdicts, measured loudness, and the run-ledger path. Only registered when the server is launched with --enable-run.yes

Resources

  • checks://catalog — every S-code check the validator can emit: severity, layer, title, description, related F-register entries.
  • mcodes://catalog — every M-code compile diagnostic the packager can report, with its stable summary (retired codes kept for the record).
  • fregister://catalog — the failure-mode register (F_TO_CHECK.md): the WP1/WP3 failure catalogue mapped to Sentinel checks, as markdown.

Verified platforms. Every push runs this server's test suite on Linux, macOS, and Windows against Python 3.11 and 3.12 — ci.yml is the claim; the matrix is the evidence. Two boundaries come with it. First, this package is a thin wrapper: a green matrix here says the server behaves on those platforms, not that the conformance logic does — that is gated in iamf-sentinel and iamf-loom by their own matrices. Second, no encoder toolchain is installed in CI, so loom_run's execution path is exercised only through its failure behaviour — that a missing binary yields an actionable error rather than a traceback. Its subprocess half is unverified here by design; iamf-loom owns that claim. The matrix additionally carries a wheel-only leg with no sibling source checkout, which is what pip install iamf-sentinel-mcp actually gives you. Sample-gated tests skip in that environment by design. Nothing here is claimed for a platform that does not have a green leg.

Run

bash
pip install iamf-sentinel-mcpiamf-sentinel-mcp                # stdio transport, read-only (default)iamf-sentinel-mcp --enable-run   # additionally registers loom_run (executes)

Claude Desktop / Code config:

json
{ "mcpServers": { "iamf-sentinel-mcp": { "command": "iamf-sentinel-mcp" } } }

Scope and posture

  • Read-only by default. Without --enable-run, tools parse and compile; nothing is executed, no files are written, no network is touched.
  • Execution is opt-in, per launch. --enable-run registers loom_run, which runs the encoder toolchain as subprocesses and writes files; the Sentinel gate inside loom run stays on by default. A missing toolchain is an actionable error naming the expected binary path. Sentinel L3 rendered-loudness QC remains unexposed.
  • The server is a thin wrapper over the products' public APIs; conformance logic lives in the products, behind their own test gates.

Apache-2.0 (see LICENSE / NOTICE), like everything else in the iamf-sentinel / iamf-loom stack. Support posture: see the core repo's SUPPORT.md.

Related projects

  • Inseglet — the authoring-side companion: a native REAPER MCP extension for immersive authoring (beds, ambisonics, ADM) whose spatial.export_loom_manifest writes manifests this server's loom_compile / loom_run accept. Run both servers in one agent session for an author → package → validate loop.

來源:README.md,提交 5a7c914

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

3
  1. v0.2.4最新Oct 2, 2026
  2. v0.2.3Oct 2, 2026
  3. v0.2.2Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分