iamf-sentinel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| iamf_validateA | Validate an IAMF file (raw .iamf or IAMF-in-MP4) with iamf-sentinel. Runs the structural (L1) and semantic (L2) conformance checks — including
the container trim-carriage checks S-407/S-408/S-409 — and returns the
full report: a summary (PASS/FAIL/ERROR, finding counts, stream facts)
and every finding with its S-code, severity, message, and offsets.
|
| iamf_inspectA | Summarize an IAMF file's structure without judging conformance. Returns the container kind, IA sequence header profiles, codec configs (codec, samples/frame, sample rate, Opus pre-skip), element and presentation counts, audio-frame count, and start/end trim totals as parsed from the OBUs — plus, for MP4, whether edts/elst is present. Use iamf_validate for conformance findings; this tool is for orientation. |
| loom_compileA | Compile an iamf-loom manifest (YAML/JSON) to its packaging plan. Validate-only: nothing is executed and no files are written. Returns
ok=true with a plan summary — per-target backend/muxer routing with the
ADR-grounded rationale, and each step's id/kind/tool — or ok=false with
the M-code diagnostics exactly as |
| loom_explainA | Render The output walks every target: why it routed to its backend/muxer (ADR grounding, F-number references), what every step does and why it exists, and which values resolve only at execution time. Returns ok=true with the text, or ok=false with M-code diagnostics. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| checks_catalog | The S-code check catalogue: every check iamf-sentinel can emit, with severity, layer, title, description, and related F-register entries. |
| mcodes_catalog | The M-code catalogue: every compile-time diagnostic iamf-loom can report, with its stable summary. Codes marked retired are kept for the stable-contract record and are no longer emitted. |
| f_register | The failure-mode register (F_TO_CHECK.md): the WP1/WP3 failure catalogue mapped to Sentinel checks — what each F-number means, whether a check fires for it, and its disposition. Markdown. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jlivingston-Cipher/iamf-sentinel-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server