io.github.marcimastro98/xenon-widgets
NPM · XENON-MCP
Build widgets for the Xenon dashboard: SDK reference, install, runtime errors, tile screenshots.
Available components
Last scanned (4 hours ago)
Scores higher than 34% of npm servers
Category Developer Tools
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 & Transparency32
- 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
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 904 tokens (~100/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 52
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 5 Nov 2026 · Analysed npm/xenon-mcp@1.0.0
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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
check_widget ~104
Run the checks Xenon runs before installing, without installing: the package rules, what the sandbox will refuse (inline scripts, remote code, hosts) and the Store's review notes.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | yes | Absolute path of the widget folder (the one holding manifest.json). Its name is the widget id unless `id` is given. |
| id | string | – | Widget id: 2 to 41 characters, a-z, 0-9 and dashes. |
No output schema declared.
No examples provided.
install_widget ~122
Install or update the widget from its folder put it on the dashboard and show its page (a new page when the one in view is full). Permissions it asks for still wait for the person to approve them on the dashboard. Then call widget_issues and widget_screenshot.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | yes | Absolute path of the widget folder (the one holding manifest.json). Its name is the widget id unless `id` is given. |
| id | string | – | Widget id: 2 to 41 characters, a-z, 0-9 and dashes. |
No output schema declared.
No examples provided.
my_widgets ~107
List the widgets the person made (not Store downloads). With an id and a folder, write that widget's files into the folder to keep working on it.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | With id: a new or empty folder to write the widget into. |
| id | string | – | Widget id: 2 to 41 characters, a-z, 0-9 and dashes. |
| overwrite | boolean | – | Replace files with the same names in a folder that is not empty. |
No output schema declared.
No examples provided.
new_widget ~151
Write a working starter widget (manifest, HTML, CSS, JS showing live CPU and memory) into a new or empty folder. Edit it from there, then install_widget.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | yes | Absolute path of the widget folder (the one holding manifest.json). Its name is the widget id unless `id` is given. |
| id | string | – | Widget id: 2 to 41 characters, a-z, 0-9 and dashes. |
| name | string | – | The name people see. Defaults to the id. |
| overwrite | boolean | – | Replace files with the same names in a folder that is not empty. |
| size | string | – | Tile size. Defaults to medium. |
No output schema declared.
No examples provided.
sdk_reference ~68
Read the Xenon Widget SDK reference: the manifest, the message protocol, data streams, actions, storage, sizing and the sandbox rules. With no section you get the table of contents. Read it before writing a widget.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | A section name from the table of contents. |
No output schema declared.
No examples provided.
share_widget ~78
A share code for one of the person's own widgets, which anyone can paste into Xenon, plus the Store review notes. To put it in the Store the person sends it from xenon-app.com/submit.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Widget id: 2 to 41 characters, a-z, 0-9 and dashes. |
No output schema declared.
No examples provided.
widget_issues ~101
What went wrong in an installed widget while it ran: errors and console.error lines, requests the sandbox blocked, whether its permissions are approved, and how heavy it is. Errors thrown in widget code show as "Script error." because of the sandbox: wrap code in try/catch and console.error the message to see it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Widget id: 2 to 41 characters, a-z, 0-9 and dashes. |
No output schema declared.
No examples provided.
widget_screenshot ~67
A picture of the widget's tile as it is on screen now. Anything on top of the dashboard shows too. Not available on Linux under Wayland.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Widget id: 2 to 41 characters, a-z, 0-9 and dashes. |
No output schema declared.
No examples provided.
xenon_status ~47
Check that Xenon is running on this computer and ready for widgets: its version, the Widget SDK version, whether community widgets are on and whether a dashboard is open. Call it first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.marcimastro98/xenon-widgets MCP server?
io.github.marcimastro98/xenon-widgets runs locally as an npm package, launched with npx -y xenon-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · xenon-mcp
claude mcp add marcimastro98-xenon-widgets -- npx -y xenon-mcp
What is the io.github.marcimastro98/xenon-widgets MCP server?
io.github.marcimastro98/xenon-widgets is an MCP server listed in the public MCP registry as io.github.marcimastro98/xenon-widgets. Build widgets for the Xenon dashboard: SDK reference, install, runtime errors, tile screenshots. This page covers its npm package (xenon-mcp).
Is the io.github.marcimastro98/xenon-widgets MCP server safe to use?
io.github.marcimastro98/xenon-widgets scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 io.github.marcimastro98/xenon-widgets MCP server expose?
io.github.marcimastro98/xenon-widgets exposes 9 tools: xenon_status, sdk_reference, new_widget, check_widget, install_widget, and 4 more. Their descriptions and schemas cost roughly 845 tokens of context every time the server is loaded.
Is the io.github.marcimastro98/xenon-widgets MCP server still maintained?
io.github.marcimastro98/xenon-widgets is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.