Skip to main content
ClaudeWave

Local static analysis and evidence generation for deployed AI model artifacts

MCP ServersRegistry oficial2 estrellas0 forksJavaScriptApache-2.0Actualizado today
ClaudeWave Trust Score
95/100
Verified
Passed
  • Open-source license (Apache-2.0)
  • Actively maintained (<30d)
  • Clear description
  • Topics declared
  • Documented (README)
Last scanned: 9/9/2026
Install in Claude Code / Claude Desktop
Method: NPX · deepbom
Claude Code CLI
claude mcp add deepbom -- npx -y deepbom
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "deepbom": {
      "command": "npx",
      "args": ["-y", "deepbom"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Casos de uso

Resumen de MCP Servers

# DEEPBOM

DEEPBOM is a local static analyzer for deployed AI model artifacts. It audits
serialized graph, tensor, quantization, memory, compatibility, and ML-BOM
evidence without uploading model bytes.

The public source distribution covers TFLite, ONNX, GGUF, SafeTensors, Core ML,
and bounded ExecuTorch artifacts. Findings distinguish observed and derived
artifact facts from predicted compatibility, imported runtime evidence, and
values that cannot be assessed statically.

## Quick start

Run the published CLI without cloning the repository (Node.js 20 or newer):

```bash
npx deepbom audit "https://raw.githubusercontent.com/JunHwan-Kwon/deepbom/main/web/samples/gpu_partition_probe.onnx#sha256=82a2feef00eb6ab03d82f2b30cd17f4d826e2d8307cb059eccd6a0f3120059b2"
```

The pinned expected values and independent verifier are in
[`examples/expected-output`](examples/expected-output/README.md). Source builds
require Rust and, for the Python channel, Python 3.9 or newer; maintainer setup
is documented separately below.

## Assistant integration

Run the same local analyzer as an MCP server over stdio:

```bash
npx deepbom mcp
```

It exposes `deepbom_capabilities`, `deepbom_audit`, `deepbom_diff`, and
`deepbom_explain_rule` without uploading artifact bytes or using a hosted
analysis endpoint. Audit calls default to a bounded human summary; detailed
formats and large-model scan depth are explicit. Local paths are restricted to
the launch directory unless `DEEPBOM_MCP_ALLOWED_ROOTS` is configured.
Agent-facing usage guidance is in [the DEEPBOM skill](skills/deepbom/SKILL.md).

Verified release channels expose the same analysis implementation:

```bash
npx deepbom audit model.onnx --format cyclonedx
npx deepbom audit model.onnx --format sarif --output deepbom.sarif --gate defects
deepbom capabilities --compact
deepbom self-test
deepbom audit model.onnx --list-sections --compact
deepbom audit model.onnx --section quantization,memory --compact
deepbom explain-rule onnx.conv.output-shape
python -m pip install deepbom
cargo install deepbom
deepbom audit model.gguf --compact
deepbom verify model.tflite --contract production-interface.json
deepbom diff baseline.tflite candidate.tflite
deepbom explore model.tflite
deepbom placement model.tflite --profiles xnnpack_cpu,tflite_coreml_delegate,litert_qualcomm_qnn
deepbom graph model.onnx --format json --output artifact-graph.json
deepbom audit model.onnx --conversion-receipt conversion-receipt.json --format cyclonedx
```

The default is a terminal-sized evidence summary. `--json` and `--compact`
expose complete format evidence; `--format envelope` provides the canonical
cross-format contract; CycloneDX 1.7 and OASIS SARIF 2.1.0 are standard
projections. `--policy-output` records a hash-bound gate result when `--fail-on`
is selected. `--review-policy` adds identity-scoped, expiring exceptions and
keeps execution, coverage, and finding-policy states independent. See
[`docs/CLI_AUTOMATION.md`](docs/CLI_AUTOMATION.md). The complete
option inventory is generated from the executable in
[`docs/CLI_REFERENCE.md`](docs/CLI_REFERENCE.md).

The graph JSON output includes the evidence-preserving
`deepbom.artifact_ir.v2` ledger and a deterministic `deepbom.graph_ir.v1`
visualization compatibility projection. Serialized graph, storage topology,
architecture grouping, scoped quantization, static placement, and imported
runtime evidence remain separate. Method `2.2.0` also preserves an optional,
output-bound conversion receipt without promoting declared converter execution
to observed evidence. It materializes exactly decoded
TFLite subgraphs, ONNX nested graphs/local functions, and ExecuTorch primary
plans without flattening conditional scopes. Runtime-node fusion is reconciled
only from artifact-bound subject references or primary native op indices;
names are never guessed. `graph_ir.v1` remains primary-scope-only for legacy
consumers. The v2 JSON Schema is published at
[`docs/schemas/deepbom-artifact-ir-v2.schema.json`](docs/schemas/deepbom-artifact-ir-v2.schema.json)
and at `https://deepbom.org/schemas/deepbom-artifact-ir-v2.schema.json`.
The conversion receipt schema is published at
[`docs/schemas/deepbom-conversion-receipt-v1.schema.json`](docs/schemas/deepbom-conversion-receipt-v1.schema.json).

Public product output uses CycloneDX 1.7. Experimental standards work is not
included in the website, CLI commands, or release artifacts.

`verify` compares the serialized external tensor ABI with a supplied,
artifact-bound production declaration. `diff` uses the canonical deterministic
multi-target TFLite deployment-delta ledger, and `explore` exposes the existing
WASM redesign Pareto search without claiming trained-model accuracy. A strict
custom TFLite target can be bound with `--target-profile profile.json`; the CLI
records both the source-file SHA-256 and the resolved Rust profile SHA-256.
Accelerator evidence is separate from that CPU cost profile. Source-pinned
TFLite Core ML and LiteRT Qualcomm QNN profiles, Core ML MLComputePlan, Edge TPU
and Qualcomm compiler reports, TensorRT parser/engine evidence, and NVIDIA host
profiles use a shared staged binding without promoting static or compiled
evidence to observed execution. `placement` compares any available profiles
over one conserved graph ledger without inventing backend priority.

The Cargo launcher downloads only the engine matching its exact package version
and platform from the corresponding immutable GitHub Release. It validates the
release matrix, byte lengths, and SHA-256 digests before caching or execution.

Build the npm, standalone, Python, and Cargo launcher channels:

```bash
npm run build:channels
npm run check:public-package-boundary
npm run check:channels -- --no-build
```

Run the public correctness gates:

```bash
npm run check:cli
npm run check:cli-docs
npm run check:cli-automation
npm run check:formats
npm run check:rust
```

The browser workbench is available at [deepbom.org](https://deepbom.org/).

## Evidence scope

| Format | Public static evidence |
| --- | --- |
| TFLite | FlatBuffer graph and tensor contracts, quantization arithmetic, weight integrity, memory projections, accumulator proofs, redesign candidates, and source-bounded delegation predictions |
| ONNX | Protobuf graph, initializer and external-data contracts, symbolic shape inference, operation cost, Q/DQ and affine quantization, and provider-compatible evidence envelopes |
| GGUF | Container and tensor-directory integrity, quantization encoding inventory, architecture metadata, and bounded LLM memory scenarios |
| SafeTensors | Tensor-directory and sharding integrity, configuration-bound architecture contracts, AWQ/GPTQ/HQQ/compressed-tensors metadata, and bounded LLM memory scenarios |
| Core ML | NeuralNetwork and ML Program serialized graphs, tensor/weight encodings, deployment floor, and imported compute-plan evidence boundaries |
| ExecuTorch | Bounded ET12/FT01 plans, source-bound portable calls and processed payload identities, plus optional selected-build/backend/operator/binary attestation; execution remains external |

Static compatibility does not establish observed execution-provider assignment,
device latency, task accuracy, clinical validity, or release readiness. Runtime
claims require an identity-bound runtime capture.

The detailed format and accelerator boundary is maintained in
[`docs/SUPPORT_MATRIX.md`](docs/SUPPORT_MATRIX.md). Bugs can be reported without
sharing model bytes using
[`docs/MODEL_FREE_BUG_REPORTING.md`](docs/MODEL_FREE_BUG_REPORTING.md).

## Distribution boundary

This repository is generated from an exact reviewed allowlist. Private
rulepack generators, hosted-service infrastructure, and unreleased research
modules are not included. The enforceable boundary and export verification
method are documented in
[`docs/PUBLIC_PRIVATE_BOUNDARY.md`](docs/PUBLIC_PRIVATE_BOUNDARY.md).

## License and citation

The public source and release-channel packages are licensed under the Apache
License 2.0. Third-party model artifacts retain their declared licenses.

Please cite:

> Kwon, J. (2026). DEEPBOM: Browser-Native Static Analysis of On-Device Neural
> Network Deployment Artifacts [Computer software]. Zenodo.
> https://doi.org/10.5281/zenodo.21834508
mcpml-bommodel-context-protocolon-device-aionnxsbomtflite

Lo que la gente pregunta sobre deepbom

¿Qué es JunHwan-Kwon/deepbom?

+

JunHwan-Kwon/deepbom es mcp servers para el ecosistema de Claude AI. Local static analysis and evidence generation for deployed AI model artifacts Tiene 2 estrellas en GitHub y su última actualización registrada es del 2026-09-09.

¿Cómo se instala deepbom?

+

Puedes instalar deepbom clonando el repositorio (https://github.com/JunHwan-Kwon/deepbom) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar JunHwan-Kwon/deepbom?

+

Nuestro agente de seguridad ha analizado JunHwan-Kwon/deepbom y le ha asignado un Trust Score de 95/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene JunHwan-Kwon/deepbom?

+

JunHwan-Kwon/deepbom es mantenido por JunHwan-Kwon. La última actividad registrada en GitHub es del 2026-09-09, con 0 issues abiertos.

¿Hay alternativas a deepbom?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega deepbom en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: JunHwan-Kwon/deepbom
[![Featured on ClaudeWave](https://claudewave.com/api/badge/junhwan-kwon-deepbom)](https://claudewave.com/repo/junhwan-kwon-deepbom)
<a href="https://claudewave.com/repo/junhwan-kwon-deepbom"><img src="https://claudewave.com/api/badge/junhwan-kwon-deepbom" alt="Featured on ClaudeWave: JunHwan-Kwon/deepbom" width="320" height="64" /></a>

Más MCP Servers

Alternativas a deepbom