Dembrandt vs IAMF Sentinel
A side-by-side look at the Dembrandt and IAMF Sentinel MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Dembrandt for developer tools work as a local process; choose IAMF Sentinel for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Dembrandt when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Choose IAMF Sentinel when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
iamf_validate, iamf_inspect, loom_compile.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 53/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3,778 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Dembrandt | View IAMF Sentinel |
Tools & capabilities
Dembrandt tools
No tool names declared yet. Check the project README from the listing page.
IAMF Sentinel tools 5
iamf_validateFull conformance report on a `.iamf` / IAMF-in-MP4 file: S-code findings with severities, summary, stream facts. `strict` promotes WARN to failing.iamf_inspectStructure orientation: profiles, codec configs (incl. Opus pre-skip), element/presentation/frame counts, OBU trim totals, MP4 edts/elst presence.loom_compileCompile a Loom manifest (YAML/JSON) to its packaging plan — validate-only. Per-target backend/muxer routing with rationale, or M-code diagnostics.loom_explainloom explain` as text: the compiled plan as its own justification.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`.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Dembrandt
{
"mcpServers": {
"dembrandt": {
"command": "npx",
"args": [
"-y",
"dembrandt"
]
}
}
}
IAMF Sentinel
{
"mcpServers": {
"iamf-sentinel": {
"command": "uvx",
"args": [
"iamf-sentinel-mcp"
]
}
}
}
Frequently asked questions
Dembrandt is categorized under Developer Tools and uses a local stdio subprocess. IAMF Sentinel belongs to Developer Tools and uses a local stdio subprocess. Pick Dembrandt for developer tools work and IAMF Sentinel for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Dembrandt has no declared pricing — check the project's own site. IAMF Sentinel has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add dembrandt and iamf-sentinel as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dembrandt has a quality signal of 53/100 (Good) with 1 views, 0 installs and 3,778 GitHub stars. IAMF Sentinel has 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars.