Roast My Design System
NPM · ROAST-MY-DESIGN-SYSTEM · SCANNED SEP 20
Audit your Design System and serve your Agent the rules that keep AI-written UI on-system.
Available components
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 & Transparency74
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to pencilrebel/roast-my-design-system). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 365 tokens (~45/item across 8 items; 5 tools + 3 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 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
npm · roast-my-design-system
claude mcp add pencilrebel-roast-my-design-system -- npx -y roast-my-design-system
{
"mcpServers": {
"pencilrebel-roast-my-design-system": {
"command": "npx",
"args": [
"-y",
"roast-my-design-system"
]
}
}
} {
"servers": {
"pencilrebel-roast-my-design-system": {
"command": "npx",
"args": [
"-y",
"roast-my-design-system"
]
}
}
} codex mcp add pencilrebel-roast-my-design-system -- npx -y roast-my-design-system
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pencilrebel-roast-my-design-system": {
"type": "local",
"command": [
"npx",
"-y",
"roast-my-design-system"
],
"enabled": true
}
}
} openclaw mcp add pencilrebel-roast-my-design-system --command npx --arg -y --arg roast-my-design-system
mcp_servers:
pencilrebel-roast-my-design-system:
command: "npx"
args: ["-y", "roast-my-design-system"] {
"McpServers": {
"pencilrebel-roast-my-design-system": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"roast-my-design-system"
]
}
}
} assistant mcp add pencilrebel-roast-my-design-system -t stdio -c npx -a -y roast-my-design-system
{
"mcpServers": {
"pencilrebel-roast-my-design-system": {
"command": "npx",
"args": [
"-y",
"roast-my-design-system"
]
}
}
} 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.
- 20 Sept 26 +1
- Security disclosure: fail → pass ▲ functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 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.
- 10 Sept 26 +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.
- 8 Sept 26 +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.
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 20 Sept 2026 · Analysed npm/roast-my-design-system@5.2.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 | pencilrebel/roast-my-design-system |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pencilrebel/roast-my-design-system/.github/workflows/publish.yml@refs/tags/v5.2.1 |
| Rekor log index | 2568131381 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c550570f58c2f081044be578511ebb770072a677228f0a13d2f1f7f01d28342356e10bf7689629f4171edc3c5973c54fe7c318a9a768de4a01f59171e |
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 →
roast_find_component ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Component name or intent |
No output schema declared.
No examples provided.
roast_find_token ~49
Snap a raw value (#111111, 13px) to this repo's nearest token or scale step. Says so when no scale exists.
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | Colour or length value |
No output schema declared.
No examples provided.
roast_get_context ~59
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Repo-relative folder (optional) |
No output schema declared.
No examples provided.
roast_review ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
roast_validate ~65
Check code before saving: hardcoded colours, near-token twins, off-scale spacing, arbitrary brackets, inline styles, !important, duplicate components. Findings name the fix.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The code to check |
| file | string | – | Intended file path (optional) |
No output schema declared.
No examples provided.
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 20 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 20 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.