# IAMF Sentinel (pypi · iamf-sentinel-mcp)

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

- Trust score: 78/100 (medium)
- Change this week: −1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `iamf-sentinel-mcp`: 78/100 (this document), [markdown](https://verifymcp.io/servers/jlivingston-cipher-iamf-sentinel-mcp/iamf-sentinel-mcp.md), [page](https://verifymcp.io/servers/jlivingston-cipher-iamf-sentinel-mcp/iamf-sentinel-mcp)

## Channel facts

- Registry: `pypi`
- Package: `iamf-sentinel-mcp`
- Version: `0.2.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it.
  - 3 of 32 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 35/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 37 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 749 tokens (~107/item across 7 items; 4 tools + 3 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the IAMF Sentinel MCP server?

IAMF Sentinel runs locally as a PyPI package, launched with uvx iamf-sentinel-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add jlivingston-cipher-iamf-sentinel-mcp -- uvx iamf-sentinel-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "jlivingston-cipher-iamf-sentinel-mcp": {
      "command": "uvx",
      "args": [
        "iamf-sentinel-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jlivingston-cipher-iamf-sentinel-mcp": {
      "command": "uvx",
      "args": [
        "iamf-sentinel-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add jlivingston-cipher-iamf-sentinel-mcp -- uvx iamf-sentinel-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jlivingston-cipher-iamf-sentinel-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "iamf-sentinel-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jlivingston-cipher-iamf-sentinel-mcp --command uvx --arg iamf-sentinel-mcp
```

### Hermes

```yaml
mcp_servers:
  jlivingston-cipher-iamf-sentinel-mcp:
    command: "uvx"
    args: ["iamf-sentinel-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "jlivingston-cipher-iamf-sentinel-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "iamf-sentinel-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add jlivingston-cipher-iamf-sentinel-mcp -t stdio -c uvx -a iamf-sentinel-mcp
```

### Other

```json
{
  "mcpServers": {
    "jlivingston-cipher-iamf-sentinel-mcp": {
      "command": "uvx",
      "args": [
        "iamf-sentinel-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 78, −4)

- [functional] Stability: pass → 0.77

### 2026-09-19 (score 82, +1)

- [security] Stability: 0.97 → pass

### 2026-09-17 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 80, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 64, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-13 (score 79, −3)

- [functional] Stability: pass → 0.80

### 2026-09-12 (score 82, +1)

- [security] Stability: 0.97 → pass

### 2026-09-10 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `iamf_validate` (~170 tokens)

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.
\`strict` treats WARN findings as failing. `profile` selects a validation
profile (default "generic"). L3 rendered-loudness QC needs the decoder
toolchain and is not exposed by this server version.

Input parameters:

- `path` (string, required)
- `profile` (string)
- `strict` (boolean)

### `iamf_inspect` (~110 tokens)

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.

Input parameters:

- `path` (string, required)

### `loom_compile` (~118 tokens)

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 compile` would report them.
\`variables` fills `{variable}` placeholders (the CLI's --var).

Input parameters:

- `manifest_path` (string, required)
- `variables`

### `loom_explain` (~104 tokens)

Render `loom explain` for a manifest: the compiled plan as its own
justification, in plain text.

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.

Input parameters:

- `manifest_path` (string, required)
- `variables`

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/jlivingston-cipher-iamf-sentinel-mcp/iamf-sentinel-mcp#diagnostics

## Score history

- 2026-09-20: 78
- 2026-09-19: 82
- 2026-09-18: 81
- 2026-09-17: 81
- 2026-09-16: 80
- 2026-09-15: 80
- 2026-09-14: 64
- 2026-09-13: 79
- 2026-09-12: 82
- 2026-09-11: 81
- 2026-09-10: 81
- 2026-09-09: 80
- 2026-09-08: 80
- 2026-09-07: 79
- 2026-09-06: 79
- 2026-09-05: 79
- 2026-09-04: 78
- 2026-09-03: 78
- 2026-09-02: 77
- 2026-09-01: 77
- 2026-08-31: 76
- 2026-08-30: 76
- 2026-08-29: 75
- 2026-08-28: 75
- 2026-08-27: 74
- 2026-08-26: 74
- 2026-08-25: 72
- 2026-08-24: 71
- 2026-08-23: 71
- 2026-08-22: 70

## Common questions

### What is the IAMF Sentinel MCP server?

IAMF Sentinel is an MCP server listed in the public MCP registry as io.github.jlivingston-Cipher/iamf-sentinel-mcp. MCP server for the iamf-sentinel IAMF conformance validator and the iamf-loom packager. This page covers its PyPI package (iamf-sentinel-mcp).

### Is the IAMF Sentinel MCP server safe to use?

IAMF Sentinel scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the IAMF Sentinel MCP server expose?

IAMF Sentinel exposes 4 tools: iamf_validate, iamf_inspect, loom_compile, loom_explain. Their descriptions and schemas cost roughly 502 tokens of context every time the server is loaded.

### Is the IAMF Sentinel MCP server still maintained?

IAMF Sentinel is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/iamf-sentinel-mcp/
- Socket report: https://socket.dev/pypi/package/iamf-sentinel-mcp
- Repository: https://github.com/jlivingston-Cipher/iamf-sentinel-mcp
- Changelog RSS feed: https://verifymcp.io/servers/jlivingston-cipher-iamf-sentinel-mcp/iamf-sentinel-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/jlivingston-cipher-iamf-sentinel-mcp/iamf-sentinel-mcp.json
- HTML version of this page: https://verifymcp.io/servers/jlivingston-cipher-iamf-sentinel-mcp/iamf-sentinel-mcp