Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DEEPBOM

NPM · DEEPBOM · 2 COMPONENTS · SCANNED SEP 21

Browser-local and CLI static evidence for deployed AI model artifacts.

Available components

remote · deepbom.org 74 npm · deepbom 86
+18 this week 86 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to JunHwan-Kwon/deepbom). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1045 tokens (~261/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 96% of tool parameters carry a description.Partial
  • Structured output schemas are declared (75% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the DEEPBOM MCP server?

DEEPBOM runs locally as an npm package, launched with npx -y deepbom. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · deepbom

# add to Claude Code
claude mcp add junhwan-kwon-deepbom -- npx -y deepbom
// .cursor/mcp.json
{
  "mcpServers": {
    "junhwan-kwon-deepbom": {
      "command": "npx",
      "args": [
        "-y",
        "deepbom"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "junhwan-kwon-deepbom": {
      "command": "npx",
      "args": [
        "-y",
        "deepbom"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add junhwan-kwon-deepbom -- npx -y deepbom
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "junhwan-kwon-deepbom": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "deepbom"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add junhwan-kwon-deepbom --command npx --arg -y --arg deepbom
# ~/.hermes/config.yaml
mcp_servers:
  junhwan-kwon-deepbom:
    command: "npx"
    args: ["-y", "deepbom"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "junhwan-kwon-deepbom": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "deepbom"
      ]
    }
  }
}
# add to Vellum
assistant mcp add junhwan-kwon-deepbom -t stdio -c npx -a -y deepbom
// mcp.json
{
  "mcpServers": {
    "junhwan-kwon-deepbom": {
      "command": "npx",
      "args": [
        "-y",
        "deepbom"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 18 Sept 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 17 Sept 26 +16
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
    • Package version: 1.101.0 → 1.103.0 functional
    • Package version: 1.101.0 → 1.102.0 functional
  • 16 Sept 26 −26
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: pass → unverified ▼ functional
    • Package version: 1.99.1 → 1.101.0 functional
  • 15 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 14 Sept 26 +12
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
    • Package version: 1.97.4 → 1.99.1 functional
  • 13 Sept 26 −25
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: pass → unverified ▼ security
    • Schema quality: 225 → 252 ▼ functional
    • Dependency health: pass → unverified ▼ functional
    • Package version: 1.96.15 → 1.97.4 functional
    • Package version: 1.96.15 → 1.97.3 functional
    • Package version: 1.96.15 → 1.97.0 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed npm/deepbom@1.103.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo JunHwan-Kwon/deepbom
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/JunHwan-Kwon/deepbom/.github/workflows/release-channels.yml@refs/tags/channels-v1.103.0
Rekor log index 2875436345
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:a438d42c6d3bbc47815e84703d60dc5e64474aa30bbcd5f3d8a8b7d6c192effd446a1e2bec3af5943c30878dfadbf4ab70676ba12b3e12d730c3c4db3

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~939 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
deepbom_audit ~583

Audit one local or immutable remote model artifact and return local static evidence. Request section=model_summary for the common operation/storage table derived from Model IR; it does not infer framework trainability or runtime order. Supported remote identities are hf:// with a full commit, gs:// with an object generation, and HTTPS with SHA-256. Remote bytes may be downloaded into a content-addressed local cache but are never uploaded by DEEPBOM. Findings distinguish artifact_defect, caution, and evidence_gap; an evidence_gap is not a defect. The result never establishes executed accelerator assignment, latency, energy, accuracy, or device fit.

NameTypeReqDescription
cache_dirstring–Content-addressed cache directory under the allowed roots.
expected_sha256string–Independent expected digest for a local or remote artifact.
external_data_dirstring–Local ONNX external_data or ExecuTorch .ptd sidecar directory under the allowed roots.
gatestring–Return a policy-blocked status when an artifact_defect is present. Nothing is gated by default.
list_sectionsboolean–List selectable analysis sections instead of auditing.
max_download_gibinteger–Upper bound for one remote download in GiB.
offlineboolean–Refuse network access and require a verified cache receipt.
output_formatstring–summary is the bounded human-readable default. Request envelope for the canonical cross-format contract, json/json-compact for format-specific evidence, CycloneDX 1.7, or SARIF explicitly.
pathstringyesLocal artifact/package path under DEEPBOM_MCP_ALLOWED_ROOTS, or an immutable hf://, gs://, or hash-pinned HTTPS source.
pointerstring–Emit one RFC 6901 JSON Pointer result, such as /operator_count.
policystring–Built-in gate profile. Engineering blocks artifact defects; regulatory also requires evidence gaps to be resolved but does not determine legal compliance.
scanstring–Bounded scan policy. structure avoids payload integrity work; integrity streams supported payload checks; full requests all supported static analysis.
sectionstring–Emit only these analysis sections, comma-separated. Use list_sections first. model_summary returns deepbom.model_summary.v1. Applies to json formats.
targetstring–TFLite target profile id for cost-model binding; it is not host detection.
tensor_limitinteger–Maximum tensor rows to return; requires tensors=true. The result includes next_offset when more rows exist.
tensor_offsetinteger–Zero-based tensor row offset for a bounded tensor page; requires tensors=true.
tensorsboolean–For a GGUF artifact, return the bounded structure-only deepbom.tensor_table.v1 projection instead of the full tensor/numerical ledgers.

No output schema declared.

No examples provided.

deepbom_capabilities ~44

Return deepbom.cli_capabilities.v1: supported artifact formats, output contracts, scan policies, target profiles, and exit codes. Call this before assuming an option exists.

Input schema present but exposes no named parameters.

NameTypeReqDescription
schema–yes–

No examples provided.

deepbom_diff ~238

Compare two artifacts of the same supported format and return deepbom.semantic_artifact_diff.v1. TFLite results also retain the target-bound deployment delta. The comparison does not prove lineage, runtime behaviour, task quality, or regulatory significance.

NameTypeReqDescription
baselinestringyesLocal or immutable remote baseline artifact or package.
cache_dirstring–Content-addressed cache directory under the allowed roots.
candidatestringyesLocal or immutable remote candidate artifact or package of the same format.
expected_sha256string–Expected digest for the baseline source. Use independently pinned remote URLs for both artifacts when possible.
max_download_gibinteger––
offlineboolean–Refuse network access and require verified cache receipts.
targetstring–Optional TFLite target profile id for the embedded pinned cost model.
tensor_limitinteger–Maximum changed-tensor rows to return; requires tensors=true.
tensor_offsetinteger–Zero-based changed-tensor row offset; requires tensors=true.
tensorsboolean–Return the tensor-encoding transition projection instead of the full semantic diff.
NameTypeReqDescription
schema–yes–

No examples provided.

deepbom_explain_rule ~74

Return the machine-readable meaning, evidence boundary, source binding, and verification status of one DEEPBOM rule or analysis term. Use deepbom_capabilities or the CLI rule index to discover identifiers instead of guessing their meaning.

NameTypeReqDescription
rulestringyesRule or analysis-term identifier accepted by deepbom explain-rule.
NameTypeReqDescription
schema–yes–

No examples provided.

Common questions

What is the DEEPBOM MCP server?

DEEPBOM is an MCP server listed in the public MCP registry as io.github.JunHwan-Kwon/deepbom. Browser-local and CLI static evidence for deployed AI model artifacts. This page covers its npm package (deepbom).

Is the DEEPBOM MCP server safe to use?

DEEPBOM scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 DEEPBOM MCP server expose?

DEEPBOM exposes 4 tools: deepbom_capabilities, deepbom_audit, deepbom_diff, deepbom_explain_rule. Their descriptions and schemas cost roughly 939 tokens of context every time the server is loaded.

Is the DEEPBOM MCP server still maintained?

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

What licence is the DEEPBOM MCP server under?

DEEPBOM declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.