DEEPBOM
REMOTE · DEEPBOM.ORG · 2 COMPONENTS · SCANNED SEP 21
Browser-local and CLI static evidence for deployed AI model artifacts.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 519 tokens (~103/item across 5 items; 4 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 25% 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 2 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 6 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
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'
{
"mcpServers": {
"junhwan-kwon-deepbom": {
"url": "https://deepbom.org/mcp"
}
}
} {
"servers": {
"junhwan-kwon-deepbom": {
"type": "http",
"url": "https://deepbom.org/mcp"
}
}
} [mcp_servers.junhwan-kwon-deepbom] url = "https://deepbom.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"junhwan-kwon-deepbom": {
"type": "remote",
"url": "https://deepbom.org/mcp",
"enabled": true
}
}
} openclaw mcp add junhwan-kwon-deepbom --url 'https://deepbom.org/mcp' --transport streamable-http
mcp_servers:
junhwan-kwon-deepbom:
url: "https://deepbom.org/mcp" {
"McpServers": {
"junhwan-kwon-deepbom": {
"Transport": "http",
"Url": "https://deepbom.org/mcp"
}
}
} assistant mcp add junhwan-kwon-deepbom -t streamable-http -u 'https://deepbom.org/mcp'
{
"mcpServers": {
"junhwan-kwon-deepbom": {
"type": "http",
"url": "https://deepbom.org/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
- Server version: 1.102.0 → 1.103.0 functional
- Server version: 1.101.0 → 1.102.0 functional
- 16 Sept 26 0
- Resource “DEEPBOM browser-local artifact analyzer” now points somewhere else: ui://deepbom/analyzer.html → ui://deepbom/analyzer-v2.html security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “deepbom_analyze_file” rewrote its description, which is the text the model reads security
- Schema quality: 81 → 103 ▼ functional
- Schema quality: good → excellent functional
- Server version: 1.99.2 → 1.101.0 functional
- 15 Sept 26 +1
- Server version: 1.99.1 → 1.99.2 functional
- 14 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.97.4 → 1.99.1 functional
- 13 Sept 26 70
First indexed and scored.
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 · 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 | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | c8b95d363ba620b313319d61781f5eb8 |
| 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. | present | 26974 | 8 | Verified |
| deepbom.org. | absent | 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 | – |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_location | string | yes | – |
| analyzer_version | string | yes | – |
| artifact | object | yes | – |
| evidence_boundary | string | yes | – |
| findings | object | yes | – |
| graph | object | yes | – |
| model_summary | object | yes | – |
| quantization | object | yes | – |
| reproduction | object|null | yes | – |
| schema | string | yes | – |
| storage | object|null | yes | – |
| transfer_boundary | string | yes | – |
| verdict | object | yes | – |
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.
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 74 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 4 tools: deepbom_analyze_file, deepbom_capabilities, deepbom_publish_analysis, deepbom_publish_error. Their descriptions and schemas cost roughly 283 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 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.