# Roast My Design System (npm · roast-my-design-system) Audit your Design System and serve your Agent the rules that keep AI-written UI on-system. - Trust score: 93/100 (high trust) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-21 ## Components - npm · `roast-my-design-system`: 93/100 (this document), [markdown](https://verifymcp.io/servers/pencilrebel-roast-my-design-system/roast-my-design-system.md), [page](https://verifymcp.io/servers/pencilrebel-roast-my-design-system/roast-my-design-system) ## Channel facts - Registry: `npm` - Package: `roast-my-design-system` - Version: `5.2.1` - Transport: `stdio` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-09-21. - **Supply Chain Security**: 100/100 - No malware found by supply-chain analysis. - No known CVEs affecting this package version or its production dependencies. - No install/post-install scripts declared. - No production dependencies, so there is no dependency health to assess. - **Provenance & Transparency**: 74/100 - Repository check failed: the declared repository URL redirects; it must resolve directly. - Cryptographically verified build provenance (signed, bound to pencilrebel/roast-my-design-system). - Clear OSI-approved license (MIT). - Actively maintained (last published 0 days ago). - Publishes a security disclosure policy (SECURITY.md). - **Schema Quality & AI Usability**: 88/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (excellent). - Tool/resource definitions use about 365 tokens (~45/item across 8 items; 5 tools + 3 resources), lean. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 100/100 - No destabilizing schema changes in the last 30 days. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### How do I install the Roast My Design System MCP server? Roast My Design System runs locally as an npm package, launched with npx -y roast-my-design-system. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add pencilrebel-roast-my-design-system -- npx -y roast-my-design-system ``` ### Cursor ```json { "mcpServers": { "pencilrebel-roast-my-design-system": { "command": "npx", "args": [ "-y", "roast-my-design-system" ] } } } ``` ### VS Code ```json { "servers": { "pencilrebel-roast-my-design-system": { "command": "npx", "args": [ "-y", "roast-my-design-system" ] } } } ``` ### Codex ```bash codex mcp add pencilrebel-roast-my-design-system -- npx -y roast-my-design-system ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "pencilrebel-roast-my-design-system": { "type": "local", "command": [ "npx", "-y", "roast-my-design-system" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add pencilrebel-roast-my-design-system --command npx --arg -y --arg roast-my-design-system ``` ### Hermes ```yaml mcp_servers: pencilrebel-roast-my-design-system: command: "npx" args: ["-y", "roast-my-design-system"] ``` ### Netclaw ```json { "McpServers": { "pencilrebel-roast-my-design-system": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "roast-my-design-system" ] } } } ``` ### Vellum ```bash assistant mcp add pencilrebel-roast-my-design-system -t stdio -c npx -a -y roast-my-design-system ``` ### Other ```json { "mcpServers": { "pencilrebel-roast-my-design-system": { "command": "npx", "args": [ "-y", "roast-my-design-system" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-09-20 (score 93, +1) - [functional improvement] Security disclosure: fail → pass ### 2026-09-19 (score 92, 0) - [security] Stability: 0.97 → pass ### 2026-09-18 (score 92, +1) No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-16 (score 91, +1) No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-14 (score 90, +1) No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-12 (score 89, +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. ### 2026-09-10 (score 88, +1) No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-08 (score 87, +1) No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes. ## MCP tools (5) ### `roast_get_context` (~59 tokens) Design-system context before writing UI in this repo: tokens, canonical components, duplicates, spacing and type rules, from a real scan. Optional path ("packages/ui") narrows the slice. Input parameters: - `path` (string): Repo-relative folder (optional) ### `roast_find_component` (~58 tokens) Find the canonical component for a name or intent ("icon button"). Returns import path, usage count and a real usage example, or an honest zero. Ties are reported, never guessed. Input parameters: - `query` (string, required): Component name or intent ### `roast_find_token` (~49 tokens) Snap a raw value (#111111, 13px) to this repo's nearest token or scale step. Says so when no scale exists. Input parameters: - `value` (string, required): Colour or length value ### `roast_validate` (~65 tokens) Check code before saving: hardcoded colours, near-token twins, off-scale spacing, arbitrary brackets, inline styles, !important, duplicate components. Findings name the fix. Input parameters: - `code` (string, required): The code to check - `file` (string): Intended file path (optional) ### `roast_review` (~42 tokens) Review the working tree's changed files (git diff + untracked) against the design system. Reads the diff itself; send no code. Call before finishing UI work. ## Diagnostics Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pencilrebel-roast-my-design-system/roast-my-design-system#diagnostics ## Score history - 2026-09-21: 93 - 2026-09-20: 93 - 2026-09-19: 92 - 2026-09-18: 92 - 2026-09-17: 91 - 2026-09-16: 91 - 2026-09-15: 90 - 2026-09-14: 90 - 2026-09-13: 89 - 2026-09-12: 89 - 2026-09-11: 88 - 2026-09-10: 88 - 2026-09-09: 87 - 2026-09-08: 87 - 2026-09-07: 86 - 2026-09-06: 86 - 2026-09-05: 85 - 2026-09-04: 85 - 2026-09-03: 84 - 2026-09-02: 84 - 2026-09-01: 83 - 2026-08-31: 83 - 2026-08-30: 82 - 2026-08-29: 82 - 2026-08-28: 81 - 2026-08-27: 81 - 2026-08-26: 80 - 2026-08-25: 79 - 2026-08-24: 78 - 2026-08-23: 83 ## Common questions ### What is the Roast My Design System MCP server? Roast My Design System is an MCP server listed in the public MCP registry as io.github.pencilrebel/roast-my-design-system. Audit your Design System and serve your Agent the rules that keep AI-written UI on-system. This page covers its npm package (roast-my-design-system). ### Is the Roast My Design System MCP server safe to use? Roast My Design System scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 Roast My Design System MCP server expose? Roast My Design System exposes 5 tools: roast_get_context, roast_find_component, roast_find_token, roast_validate, roast_review. Their descriptions and schemas cost roughly 273 tokens of context every time the server is loaded. ### Is the Roast My Design System MCP server still maintained? Roast My Design System is still listed as active in the MCP registry. We last reached this channel on 21 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 Roast My Design System MCP server under? Roast My Design System declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ## Links - npm package: https://www.npmjs.com/package/roast-my-design-system - Socket report: https://socket.dev/npm/package/roast-my-design-system - Website: https://pencilrebel.github.io/roast-my-design-system/ - Changelog RSS feed: https://verifymcp.io/servers/pencilrebel-roast-my-design-system/roast-my-design-system.xml - Changelog JSON feed: https://verifymcp.io/servers/pencilrebel-roast-my-design-system/roast-my-design-system.json - HTML version of this page: https://verifymcp.io/servers/pencilrebel-roast-my-design-system/roast-my-design-system