melta-ds-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 1 tool tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y -p melta-ds-mcp@1.9.1 melta-ds-mcp
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
1 tool that takes no input and looks read-only was called once with nothing. 1 returned a result.
get_rules | Returned a result under 0.1 s · 37,925 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
get_token path
Get a design token by dot-path. Returns the token object with its value and class mapping.
get_component id
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.
check_rule classes
Check class strings against this design system's prohibition rules. Returns violations with reasons and alternatives.
check_html source, sourceType
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).
search query
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).
get_rules category, severity, detector
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.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=22 |
| Source | github.com/tsubotax/melta-ui |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-1yMnf6YYwgqPxJf5uN7TJzVcQNTJxYNSb17r6O2j0SltXPNIzlzhVyIv4yaRBN3AYoQGzOFVO7QFanJ7o2bMmQ== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/melta-ds-mcp)
New version out? Ask for a fresh report.