melta UI
NPM · MELTA-DS-MCP
AI-Ready design system MCP: melta UI tokens, component contracts, 107 rules, check_html self-verify
Available components
Last scanned (1 hour ago)
Scores higher than 90% of npm servers
Category Design and Media
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
- 30 of 103 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 26 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- 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
- Tool/resource definitions use about 860 tokens (~78/item across 11 items; 6 tools + 5 resources), lean.Pass
- 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 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 24 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 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/melta-ds-mcp@1.9.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 103 packages
| Packages resolved | 103 |
|---|---|
| Stale | 30 |
| 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_html ~131
Lint a full HTML/JSX source against melta-ui rules — the same checks as CI and the PostToolUse hook (class rules + html-attr rules + composition rules for HTML). Use this AFTER generating UI code to self-verify before presenting it. Response always includes coverage info (manual rules cannot be auto-checked).
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | Full source code to lint (HTML / JSX / Vue template) |
| sourceType | string | – | Source type. "html" (default) also runs composition lint (nested modal etc.); "jsx" runs class + attr lint only |
No output schema declared.
No examples provided.
check_rule ~54
Check class strings against this design system's prohibition rules. Returns violations with reasons and alternatives.
| Name | Type | Req | Description |
|---|---|---|---|
| classes | string | yes | Space-separated class string to check (e.g. "text-black shadow-2xl bg-green-500") |
No output schema declared.
No examples provided.
get_component ~98
Get component metadata including variants, sizes, accessibility requirements, HTML sample, per-state specs (stateSpecs: disabled/loading/open/empty etc. — each with delta class strings + aria changes), and anatomy parts (overlay/container/th etc. with element/roles/class). Prefer these structured fields over inferring states from the HTML sample.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Component ID (e.g. "button", "card", "table", "sidebar") |
No output schema declared.
No examples provided.
get_rules ~97
Get melta-ui prohibition rules from rules.json (107 total). Use this to retrieve manual/contextual rules that check_rule cannot auto-detect. Supports filtering by category, severity, or detector.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category (e.g. "color", "spacing", "accessibility", "button", "modal") |
| detector | string | – | Filter by detector type |
| severity | string | – | Filter by severity |
No output schema declared.
No examples provided.
get_token ~66
Get a design token by dot-path. Returns the token object with its value and class mapping.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Dot-separated path to the token (e.g. "color.primary.600", "spacing.4", "radius.lg", "typography.fontSize.base") |
No output schema declared.
No examples provided.
search ~62
Search across tokens and components by keyword. Matches against names, values, class strings, and descriptions. Returns up to 20 results (truncated flag when more matched).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search keyword (e.g. "card", "primary", "shadow") |
No output schema declared.
No examples provided.
How do I install the melta UI MCP server?
melta UI runs locally as an npm package, launched with npx -y melta-ds-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 · melta-ds-mcp
claude mcp add tsubotax-melta-ui -- npx -y melta-ds-mcp
What is the melta UI MCP server?
melta UI is an MCP server listed in the public MCP registry as io.github.tsubotax/melta-ui. AI-Ready design system MCP: melta UI tokens, component contracts, 107 rules, check_html self-verify. This page covers its npm package (melta-ds-mcp).
Is the melta UI MCP server safe to use?
melta UI scores 86 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. 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 melta UI MCP server expose?
melta UI exposes 6 tools: get_token, get_component, check_rule, check_html, search, get_rules. Their descriptions and schemas cost roughly 508 tokens of context every time the server is loaded.
Is the melta UI MCP server still maintained?
melta UI 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 melta UI MCP server under?
melta UI 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 melta UI MCP server?
VerifyMCP ran 16 checks on melta UI, 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.