Divoom LAN Watchface
NPM · MCP-DIVOOM-LAN · SCANNED SEP 30
MCP server for Divoom LAN watchface APIs; read-before-write safe. V2 editor linked in README.
Available components
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 Security98
- 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
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 135 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1099 tokens (~68/item across 16 items; 14 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 46% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
How do I install the Divoom LAN Watchface MCP server?
Divoom LAN Watchface runs locally as an npm package, launched with npx -y mcp-divoom-lan. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-divoom-lan
claude mcp add divoomdevelop-mcp-divoom-lan -- npx -y mcp-divoom-lan
{
"mcpServers": {
"divoomdevelop-mcp-divoom-lan": {
"command": "npx",
"args": [
"-y",
"mcp-divoom-lan"
]
}
}
} {
"servers": {
"divoomdevelop-mcp-divoom-lan": {
"command": "npx",
"args": [
"-y",
"mcp-divoom-lan"
]
}
}
} codex mcp add divoomdevelop-mcp-divoom-lan -- npx -y mcp-divoom-lan
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"divoomdevelop-mcp-divoom-lan": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-divoom-lan"
],
"enabled": true
}
}
} openclaw mcp add divoomdevelop-mcp-divoom-lan --command npx --arg -y --arg mcp-divoom-lan
mcp_servers:
divoomdevelop-mcp-divoom-lan:
command: "npx"
args: ["-y", "mcp-divoom-lan"] {
"McpServers": {
"divoomdevelop-mcp-divoom-lan": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-divoom-lan"
]
}
}
} assistant mcp add divoomdevelop-mcp-divoom-lan -t stdio -c npx -a -y mcp-divoom-lan
{
"mcpServers": {
"divoomdevelop-mcp-divoom-lan": {
"command": "npx",
"args": [
"-y",
"mcp-divoom-lan"
]
}
}
} 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.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 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
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
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 30 Sept 2026 · Analysed npm/mcp-divoom-lan@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
watchface_create_local_clock ~122
POST /create_local_clock with multipart. Explicit operation only; never auto-triggered by patch flow.
| Name | Type | Req | Description |
|---|---|---|---|
| fileName | string | – | Filename in multipart header. Defaults to basename(imagePath). |
| filePartName | string | – | Second multipart part name. Default is current UTC ms timestamp. |
| imagePath | string | yes | – |
| metadata | object | yes | First multipart JSON body. Include ClockName and ItemList. Tool will minify JSON automatically. |
| target | object | – | Optional per-call target override. If omitted, environment variables are used. |
No output schema declared.
No examples provided.
watchface_get_brightness ~36
Call Sys/GetBrightness.
| Name | Type | Req | Description |
|---|---|---|---|
| target | object | – | Optional per-call target override. If omitted, environment variables are used. |
No output schema declared.
No examples provided.
watchface_get_fonts_local ~38
Call Device/GetLocalFontList.
| Name | Type | Req | Description |
|---|---|---|---|
| target | object | – | Optional per-call target override. If omitted, environment variables are used. |
No output schema declared.
No examples provided.
watchface_get_local ~79
Call Device/GetLocalClockInfo for current or explicit clock id.
| Name | Type | Req | Description |
|---|---|---|---|
| clockId | integer | – | – |
| parentClockId | integer | – | – |
| parentItemId | integer | – | – |
| target | object | – | Optional per-call target override. If omitted, environment variables are used. |
| useCurrentDisplayClock | boolean | – | – |
No output schema declared.
No examples provided.
watchface_get_store_market_list ~50
Call Device/GetStoreClockMarketList after device prefetch has populated in-memory store data.
| Name | Type | Req | Description |
|---|---|---|---|
| target | object | – | Optional per-call target override. If omitted, environment variables are used. |
No output schema declared.
No examples provided.
watchface_onoff_screen ~69
Call Channel/OnOffScreen with OnOff (1=on, 0=off).
| Name | Type | Req | Description |
|---|---|---|---|
| onOff | integer | yes | 1 turns screen on, 0 turns screen off. |
| target | object | – | Optional per-call target override. If omitted, environment variables are used. |
No output schema declared.
No examples provided.
watchface_patch_local ~148
Call Device/PatchLocalClockInfo with precheck. Stops when current ItemList is empty to avoid unsafe patch flow.
| Name | Type | Req | Description |
|---|---|---|---|
| clockId | integer | – | – |
| deviceImageUrl | string | – | – |
| devicePreviewImageUrl | string | – | – |
| devicePreviewImageUrl2 | string | – | – |
| itemIdList | array | – | – |
| itemList | array | – | – |
| itemPatchByRoleList | array | – | – |
| itemPatchList | array | – | – |
| setColorList | array | – | – |
| target | object | – | Optional per-call target override. If omitted, environment variables are used. |
| useCurrentDisplayClock | boolean | – | – |
No output schema declared.
No examples provided.
watchface_protocol_quick_reference ~24
Return concise operational constraints extracted from the public guide and skill.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
watchface_raw_command ~68
Raw POST /divoom_api command wrapper. Command is required; payload object is merged with enforced ReturnCode=0.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | – |
| payload | object | – | – |
| target | object | – | Optional per-call target override. If omitted, environment variables are used. |
No output schema declared.
No examples provided.
watchface_replace_dial_bg_file ~139
POST /replace_clock_dial_bg using multipart (Device/ReplaceClockDialBgFile). Does not modify DeviceImageUrl.
| Name | Type | Req | Description |
|---|---|---|---|
| clockId | integer | – | – |
| fileName | string | – | Filename in multipart header. Defaults to basename(imagePath). |
| filePartName | string | – | Second multipart part name. Default is current UTC ms timestamp. |
| imagePath | string | yes | Absolute or relative image file path (JPEG/WebP, 800x1280 recommended). |
| target | object | – | Optional per-call target override. If omitted, environment variables are used. |
| useCurrentDisplayClock | boolean | – | – |
No output schema declared.
No examples provided.
watchface_reset_local_then_cloud ~78
Call Device/ResetLocalClockFromServer. This deletes local sys-side files before optional cloud refresh.
| Name | Type | Req | Description |
|---|---|---|---|
| clockId | integer | yes | – |
| parentClockId | integer | – | – |
| parentItemId | integer | – | – |
| target | object | – | Optional per-call target override. If omitted, environment variables are used. |
No output schema declared.
No examples provided.
watchface_set_brightness ~47
Call Channel/SetBrightness with Brightness.
| Name | Type | Req | Description |
|---|---|---|---|
| brightness | integer | yes | – |
| target | object | – | Optional per-call target override. If omitted, environment variables are used. |
No output schema declared.
No examples provided.
watchface_set_clock_select ~50
Call Channel/SetClockSelectId with ClockId.
| Name | Type | Req | Description |
|---|---|---|---|
| clockId | integer | yes | – |
| target | object | – | Optional per-call target override. If omitted, environment variables are used. |
No output schema declared.
No examples provided.
watchface_upload_file ~102
POST /upload with multipart. First JSON part is caller-provided metadata (product-specific Command).
| Name | Type | Req | Description |
|---|---|---|---|
| fileName | string | – | Filename in multipart header. Defaults to basename(filePath). |
| filePartName | string | – | Second multipart part name. Default is current UTC ms timestamp. |
| filePath | string | yes | – |
| metadata | object | yes | – |
| target | object | – | Optional per-call target override. If omitted, environment variables are used. |
No output schema declared.
No examples provided.
What is the Divoom LAN Watchface MCP server?
Divoom LAN Watchface is an MCP server listed in the public MCP registry as io.github.DivoomDevelop/mcp-divoom-lan. MCP server for Divoom LAN watchface APIs; read-before-write safe. V2 editor linked in README. This page covers its npm package (mcp-divoom-lan).
Is the Divoom LAN Watchface MCP server safe to use?
Divoom LAN Watchface scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 30 September 2026. It declares no install or post-install scripts. 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 Divoom LAN Watchface MCP server expose?
Divoom LAN Watchface exposes 14 tools: watchface_get_local, watchface_patch_local, watchface_get_fonts_local, watchface_get_store_market_list, watchface_set_clock_select, and 9 more. Their descriptions and schemas cost roughly 1,050 tokens of context every time the server is loaded.
Is the Divoom LAN Watchface MCP server still maintained?
Divoom LAN Watchface is still listed as active in the MCP registry. We last reached this channel on 30 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 Divoom LAN Watchface MCP server under?
Divoom LAN Watchface declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.