onsystem
NPM · ONSYSTEM
Catches palette colors, native elements and APIs your design system lacks in agent-written React.
Available components
Last scanned (2 hours ago)
Scores higher than 95% 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 Security99
- 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
- 2 of 15 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to dgesteves/onsystem). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- 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 1450 tokens (~241/item across 6 items; 5 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 Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.94 ▲ functional
- 31 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.93 ▲ functional
- Package version: 0.11.1 → 0.12.1 functional
- Package version: 0.11.1 → 0.12.0 functional
- Package version: 0.11.1 → 0.11.2 functional
- 29 Oct 26 +5
- Known CVEs: pass → unverified ▼ security
- Stability: 0.50 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: 0.93 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.10.3 → 0.11.1 functional
- Package version: 0.10.3 → 0.11.0 functional
- 28 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 0.10.1 → 0.10.3 functional
- Package version: 0.10.1 → 0.10.2 functional
- 27 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.10.0 → 0.10.1 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 6 Nov 2026 · Analysed npm/onsystem@0.12.1
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 | dgesteves/onsystem |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/dgesteves/onsystem/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3602827774 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6d7b027f929d18aee39f2aed2973874d9c80b727e778d4048d6438ef6baa9af1cb08555850a29925fab68ad390a6a6182b3d7f9c109f2f1a8cc3f7ec0 |
Background: How many MCP packages publish verified provenance →
Dependencies 15 packages
| Packages resolved | 15 |
|---|---|
| Stale | 2 |
| 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_ui Check UI code against the design system ~333
Lint TSX/JSX against the design system. Reports hardcoded colors, spacing and radius (with the nearest token), native elements that have a design-system component, unknown components, props and variant values, and icon-only buttons without an accessible name. Each diagnostic has line/column, a rule id, a message and a suggested fix. Run it on every snippet or file you write and fix all errors. Pass `path` for a file in the project, or `code` for unsaved code, with `path` (or `filename`) naming the file it is for or its project folder.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | TSX/JSX source to check (up to 1,000,000 characters). |
| filename | string | – | Name to report `code` under; a .jsx extension parses it as JSX. At a monorepo root, the path the code will be saved under, which picks the project whose design system checks it. When the server was s… |
| limit | integer | – | Most diagnostics to return, errors first (default 50). The counts and byRule cover all of them. |
| path | string | – | Path of a .tsx, .jsx, .ts or .js file, relative to the project root (the monorepo root, when served from there) or absolute: the file to check, or, with `code`, the file the code is for, as `filename… |
| Name | Type | Req | Description |
|---|---|---|---|
| byRule | object | yes | Every finding per rule, shown or not. |
| diagnostics | array | yes | Up to `limit` diagnostics, errors first; `omitted` says how many more there are. |
| errorCount | integer | yes | – |
| file | string | yes | – |
| notice | string | – | Set when no components or no color tokens were found, so rules did not run, when components came from modules the model does not include, when the project depends on a component library onsystem does… |
| ok | boolean | yes | True when there are no errors. |
| omitted | integer | yes | Diagnostics left out by `limit`. |
| skipped | string | – | Why the file was not checked: it renders an image (next/og) or an email, or the config's `exclude` leaves it out. |
| unchecked | object | – | Components imported from modules the model does not include, not checked. |
| warningCount | integer | yes | – |
No examples provided.
get_component Get a component contract ~196
Get the full contract of one component: import, props with types and defaults, cva variants and the classes each applies, parts (sub-components), design tokens it uses, usage guidelines and examples from its docs. Call it before using a component. Accepts "Button", "CardHeader" or "Card.Header". At a monorepo root, pass `path` (the file you are editing) to get the component its project uses.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Component name, e.g. "Button" or "CardHeader". |
| path | string | – | In a monorepo served from its root: the file you are editing, or a project folder, relative to the root, to answer from that project. Without it, every project is listed together. Ignored in a single… |
| Name | Type | Req | Description |
|---|---|---|---|
| aliases | array | yes | – |
| classNames | array | yes | – |
| compoundVariants | array | yes | – |
| cssVars | array | yes | – |
| defaultImport | string | – | Another module that exports it as its default: "@mui/material/Button". |
| deprecated | – | – | – |
| description | string | – | – |
| docs | object | – | – |
| element | string | – | The native element it renders or wraps. |
| examples | array | yes | – |
| exportName | string | yes | – |
| import | string | yes | The import statement to use. |
| importPath | string | yes | – |
| inherits | array | yes | – |
| labelsChild | object | – | A prop whose text is its child element's accessible name (MUI Tooltip's title), unless `unless` is set. |
| library | string | – | The published package it is read from, by its type declarations: "@mui/material". |
| name | string | yes | How the component is written in JSX: Button, CardHeader, Tabs.List. |
| openProps | boolean | yes | Part of the props type did not resolve; extra props may be accepted. |
| package | string | – | At a workspace root: the package its source belongs to, e.g. "@acme/ui". |
| parent | string | – | – |
| polymorphic | string | – | A prop that renders another element or component in its place, with its props: "component". |
| projects | array | – | At a workspace root: the folders of the projects that use it. |
| props | array | yes | – |
| source | object | yes | – |
| subcomponents | array | yes | – |
| tokens | array | yes | Names of the design tokens its classes use. |
| variants | array | yes | – |
No examples provided.
get_tokens Get design tokens ~198
List design tokens with resolved values, dark-mode values and how to use each (Tailwind class or CSS variable). Filter by category (color, spacing, radius, typography, shadow, other) or a substring. Use these instead of hex codes, px values or Tailwind default palette classes. Chart and sidebar colors are listed under their own headings: they are for charts and the sidebar, not for status colors.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only tokens of this category. |
| path | string | – | In a monorepo served from its root: the file you are editing, or a project folder, relative to the root, to answer from that project. Without it, every project is listed together. Ignored in a single… |
| query | string | – | Substring to match in names, usages or descriptions. |
| Name | Type | Req | Description |
|---|---|---|---|
| tokens | array | yes | – |
No examples provided.
list_components List design-system components ~275
List every component in the project design system with a one-line description, the native element it renders, its variant values, its parts and its import. Icons (components that render an <svg>) are named on one line per import, or per folder for icons with a module each, five or more to a line. Call this before writing UI in this project. `query`, `kind` and `limit` narrow a long list. At a monorepo root, pass `path` for the project of the file you are editing; without it, every project is listed, each component with its package.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | "icon": only the components that render an <svg>, one by one. "component": all the others. |
| limit | integer | – | Most components to list one by one. |
| path | string | – | In a monorepo served from its root: the file you are editing, or a project folder, relative to the root, to answer from that project. Without it, every project is listed together. Ignored in a single… |
| query | string | – | Only components with this text in their name, their parts' names or their description. |
| Name | Type | Req | Description |
|---|---|---|---|
| components | array | yes | The components listed one by one, after `query`, `kind` and `limit`. |
| icons | array | – | Without `kind`: icons, the components that render an <svg>, by name, five or more per module, or per folder for icons with a module each. |
| omitted | integer | – | Matching components left out by `limit`. |
No examples provided.
search_components Search components by intent ~190
Find components by what you want to build, e.g. "confirm a destructive action", "status label", "text field with validation". Ranks names, descriptions, docs, props and variant values with BM25 (local, no API key). When no component clearly matches, it says so and lists the nearest, marked `weak`. Use it when you do not know which component fits.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results. |
| path | string | – | In a monorepo served from its root: the file you are editing, or a project folder, relative to the root, to answer from that project. Without it, every project is listed together. Ignored in a single… |
| query | string | yes | What the UI should do, in plain words. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
How do I install the onsystem MCP server?
onsystem runs locally as an npm package, launched with npx -y onsystem. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · onsystem
claude mcp add dgesteves-onsystem -- npx -y onsystem
What is the onsystem MCP server?
onsystem is an MCP server listed in the public MCP registry as io.github.dgesteves/onsystem. Catches palette colors, native elements and APIs your design system lacks in agent-written React. This page covers its npm package (onsystem).
Is the onsystem MCP server safe to use?
onsystem scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 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 onsystem MCP server expose?
onsystem exposes 5 tools: list_components, get_component, search_components, get_tokens, check_ui. Their descriptions and schemas cost roughly 1,192 tokens of context every time the server is loaded.
Is the onsystem MCP server still maintained?
onsystem is still listed as active in the MCP registry. We last reached this channel on 6 November 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 onsystem MCP server under?
onsystem declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the onsystem MCP server?
VerifyMCP ran 16 checks on onsystem, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.