DEEPBOM
REMOTE · DEEPBOM.ORG · 2 COMPONENTS
Browser-local and CLI static evidence for deployed AI model artifacts.
Available components
Last scanned (16 hours ago)
Scores higher than 83% of remote servers
Reachable. Last reached 21 Nov 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1156 tokens (~144/item across 8 items; 7 tools + 1 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 27% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deepbom_publish_analysis" implies "publish" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 9 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
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 8 Nov 26 0
- Stability: 0.97 → pass security
- 7 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Server version: 2.4.0 → 2.5.0 functional
- 13 Oct 26 0
- Stability: 0.97 → pass security
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 Nov 2026 · Probed https://deepbom.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=deepbom.org | CN=WE1,O=Google Trust Services,C=US | 8 Nov 2026 | 6 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | e324f2725fbc52fe1360000dc1d6bbc4 |
| SANs: deepbom.org, *.deepbom.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of deepbom.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| org. | DS published | 725 | 8 | Verified |
| deepbom.org. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://deepbom.org/mcp | Verified | 200 | |
| http (plaintext) | http://deepbom.org/mcp | HTTPS enforced | 301 | https://deepbom.org/mcp |
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 →
deepbom_analyze_file Analyze an AI model artifact ~138
Use when the user asks to inspect, summarize, or visualize an attached TFLite, ONNX, GGUF, SafeTensors, Core ML, or ExecuTorch deployment artifact. Opens a browser-local analyzer, returns a hash-bound format-neutral Model IR table and static evidence summary, and provides deterministic document views without executing model code. Do not use for training checkpoints, measured latency, task accuracy, clinical validity, regulatory compliance, or actual runtime placement.
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_depth | string | – | Use structure unless the user explicitly asks to inspect serialized tensor payload values. Payload integrity can require reading the complete attachment. |
| file | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_depth | string | yes | – |
| analyzer_version | string | yes | – |
| file | object | yes | – |
| privacy | string | yes | – |
| status | string | yes | – |
No examples provided.
deepbom_capabilities Check DEEPBOM capabilities ~48
Use before analysis when format support, privacy boundaries, or the difference between the ChatGPT and local DEEPBOM paths is unclear. Returns capability metadata only and does not inspect a file.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| chatgpt_path | object | yes | – |
| evidence_boundary | string | yes | – |
| local_path | object | yes | – |
| schema | string | yes | – |
| supported_formats | array | yes | – |
| version | string | yes | – |
No examples provided.
deepbom_publish_analysis Return a DEEPBOM analysis to chat ~50
Receives one bounded browser-produced DEEPBOM result, validates its structure, and returns it to the conversation. This tool accepts analysis results, never model bytes.
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
deepbom_publish_error Return a DEEPBOM analysis error to chat ~47
Receives one bounded browser-produced DEEPBOM error and returns a recovery action to the conversation. This tool accepts diagnostic text, never model bytes.
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_location | string | yes | – |
| analyzer_version | string | yes | – |
| code | string | yes | – |
| file_name | string|null | yes | – |
| message | string | yes | – |
| schema | string | yes | – |
| suggested_action | string | yes | – |
| transfer_boundary | string | yes | – |
No examples provided.
deepbom_publish_query Return requested model evidence to chat ~57
Component-only: validates and returns a bounded Evidence IR query projection for the same attachment. No model bytes, state persistence, or runtime execution. Result digests establish consistency, not independent server attestation.
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_location | string | yes | – |
| analyzer_version | string | yes | – |
| artifact | object | yes | – |
| context | object | yes | – |
| coverage | object | yes | – |
| evidence_boundary | string | yes | – |
| model_ir_sha256 | string | yes | – |
| query | object | yes | – |
| query_sha256 | string | yes | – |
| result_sha256 | string | yes | – |
| rows | array | yes | – |
| schema | string | yes | – |
| status | string | yes | – |
| transfer_boundary | string | yes | – |
No examples provided.
deepbom_query_file Inspect specific model evidence ~252
Use for follow-up questions about an already identified attachment: inspect a layer by subject_ref, search or page through all operations, inspect findings, rank improvement investigations, inspect encoded activation fusion, compare source-pinned static delegate eligibility, or explicitly analyze weight distributions, channels, similarity, singular spectra, sparsity and quantization with section=weights and optional weight_view. Weight analysis reads payloads on demand with explicit decoder/budget coverage (128 MiB widget limit). Reuse the ChatGPT-authorized file and the exact SHA-256 from its previous DEEPBOM result. section=profiles lists available backend profiles; query.target selects only a TFLite CPU planning profile from capabilities. The browser computes the query from the shared Evidence IR and returns a bounded result; model bytes are not sent to DEEPBOM. Static candidate eligibility is not observed placement, speed, accuracy, or runtime fusion. Do not invent findings while browser_query_started is pending.
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_depth | string | – | Use structure unless the user explicitly asks to inspect serialized tensor payload values. Payload integrity can require reading the complete attachment. |
| expected_sha256 | string | yes | – |
| file | – | yes | – |
| query | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_depth | string | yes | Use structure unless the user explicitly asks to inspect serialized tensor payload values. Payload integrity can require reading the complete attachment. |
| analyzer_version | string | yes | – |
| expected_sha256 | string | yes | – |
| query | object | yes | – |
| status | string | yes | – |
No examples provided.
deepbom_workflow_guide Choose a DEEPBOM analysis workflow ~168
Use to discover how to answer a model-analysis question across ChatGPT, the interactive deepbom.org workspace and the local CLI. Returns real query sections, visualization/export actions, explicit web continuation links, required inputs, CLI argument templates and evidence limits for weights, pruning investigation, comparison, BOM verification, metadata/OMOP, activation evidence, runtime, batch/CI and integrations. No attachment is required. This is guidance, not a completed analysis or local command execution. Prefer answering from existing evidence; inspect supported follow-ups with deepbom_query_file before offering web continuation for richer interaction. Website links transfer only a workflow ID, never model data.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Optional known artifact format; filters applicable workflows, not per-file analysis coverage. |
| workflow | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| boundary | string | yes | – |
| catalog_version | string | yes | – |
| format | string|null | yes | – |
| schema | string | yes | – |
| status | string | yes | – |
| workflows | array | yes | – |
No examples provided.
How do I install the DEEPBOM MCP server?
DEEPBOM is a hosted endpoint at https://deepbom.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · deepbom.org
claude mcp add --transport http junhwan-kwon-deepbom 'https://deepbom.org/mcp'
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 hosted endpoint (https://deepbom.org/mcp).
Is the DEEPBOM MCP server safe to use?
DEEPBOM scores 83 out of 100 on VerifyMCP. 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 7 tools: deepbom_analyze_file, deepbom_capabilities, deepbom_publish_analysis, deepbom_publish_error, deepbom_query_file, and 2 more. Their descriptions and schemas cost roughly 760 tokens of context every time the server is loaded.
Does the DEEPBOM MCP server require authentication?
No. We connected to DEEPBOM without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DEEPBOM MCP server still maintained?
DEEPBOM is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the DEEPBOM MCP server?
VerifyMCP ran 14 checks on DEEPBOM, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.