WunderUI
NPM · WUNDERUI-MCP
The WunderUI design system for coding agents: components, props, tokens, rules and skills.
Available components
Last scanned (18 hours ago)
Scores higher than 92% 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 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 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Kl-webmedia/wunderui-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 889 tokens (~80/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 58% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
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.
- 3 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 +1
- Tool safety: pass → unverified ▼ security
- Stability: 0.57 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 1.1.0 → 1.2.1 functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
- 14 Oct 26 +29
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Tool coverage: 58 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good 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 4 Nov 2026 · Analysed npm/wunderui-mcp@1.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 | Kl-webmedia/wunderui-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Kl-webmedia/wunderui-mcp/.github/workflows/publish.yml@refs/tags/v1.2.1 |
| Rekor log index | 3412588224 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:eec32b0aeb535d3e94f63002ddc5429fefc37dca4d55504f3b3eeafa4ef8e1d45929698ba0faf6bbee57620262e7fdcd0844eff0879d3125d4e809c4f |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| 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 →
get_block_source Get a WunderUI block's source (Pro) ~89
The React source of a UI block (e.g. category 'app', block 'billing'), optionally one screen, plus the shared helpers it imports. Needs a WunderUI Pro key in WUNDERUI_LICENSE_KEY. Use https://wunderui.com/api/registry/index to see every block.
| Name | Type | Req | Description |
|---|---|---|---|
| block | string | yes | – |
| category | string | yes | – |
| screen | string | – | – |
No output schema declared.
No examples provided.
get_component Get a WunderUI component ~127
Everything needed to use one component correctly: its exported names, the TypeScript prop signature straight from the build, a props table per export (type, allowed values, default, required, description), its anatomy (parts and data-slot names), best practices, the CSS variables it reads with their defaults, the import line and a link to its documentation page. Also answers for hooks (signature, parameters, return value, notes), providers and utilities (useToast, ThemeProvider …).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Export name ("DataGrid"), slug ("data-grid") or title ("Data Grid") |
No output schema declared.
No examples provided.
get_design_md Get the WunderUI DESIGN.md ~98
The complete design context as one markdown document: install steps, the rules an agent should follow, every token, the component inventory with props, and starter snippets. Pull this once at the start of a build.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | Return the whole document or just one section. 'tasks' maps an intent to a component, 'donts' holds the do/don't pairs, 'reference' every component with example and props. |
No output schema declared.
No examples provided.
get_instructions Get the short WunderUI rules ~57
The short, always-on rules for building with WunderUI (components, tokens, motion, copy) — the text to keep in CLAUDE.md / AGENTS.md. Read this first; use get_design_md for the full context.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_library_info Get WunderUI package info ~34
Package name and version, install commands, the stack it is built on, and how many components, categories and templates exist.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_skill Get a WunderUI agent skill ~90
Returns one skill's instructions (its SKILL.md) from wunderui.com, so the agent can follow the workflow without installing the skill. Pro skills are sent only with a valid Pro key in WUNDERUI_LICENSE_KEY. Scripts the skill mentions come with the installed skill (wunderui.com/skills).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Skill name, e.g. wunderui-theme or wunderui-screen |
No output schema declared.
No examples provided.
get_starter Get a WunderUI starter snippet ~54
Copy-paste TSX for a common composition, wired with the correct props: an application shell, a dashboard row, a data grid, an AI chat, or the theming pattern.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
No output schema declared.
No examples provided.
get_tokens Get WunderUI design tokens ~65
The design tokens for light and dark, in the format you need. Use these instead of hardcoding colours; overriding them is how WunderUI is themed.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | json, a CSS block, or Tailwind @theme mappings |
| theme | string | – | – |
No output schema declared.
No examples provided.
list_components List WunderUI components ~159
The WunderUI component inventory: name, category, plan (free or pro) and one-line description. Filter by category, plan or a free-text query. Call this first to find out whether a component already exists before building one by hand. On the Free plan use only components with plan "free".
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | One of: Primitives, Overlays, Charts, Data Display, KPI, Navigation, Forms, AI, Agents, Feedback, Layout, Block Parts |
| plan | string | – | Only components of this plan. Free = open source under MIT (github.com/wunder-ui/wunderui); pro needs WunderUI Core or Pro. |
| query | string | – | Free text, matched against name, description and category |
No output schema declared.
No examples provided.
list_skills List WunderUI agent skills ~72
The agent skills that build and check with WunderUI (set up a project, build screens, theme from a brand colour, migrate from shadcn/MUI/Chakra, token check, motion and accessibility audits, Figma). Free skills work for everyone; Pro skills need WUNDERUI_LICENSE_KEY.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_templates List WunderUI page templates ~44
Full pages assembled only from WunderUI components — a dashboard, a settings page, an AI inbox and a sign-in screen. Start from one of these instead of an empty file.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the WunderUI MCP server?
WunderUI runs locally as an npm package, launched with npx -y wunderui-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 · wunderui-mcp
claude mcp add kl-webmedia-wunderui-mcp -- npx -y wunderui-mcp
What is the WunderUI MCP server?
WunderUI is an MCP server listed in the public MCP registry as io.github.Kl-webmedia/wunderui-mcp. The WunderUI design system for coding agents: components, props, tokens, rules and skills. This page covers its npm package (wunderui-mcp).
Is the WunderUI MCP server safe to use?
WunderUI scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 WunderUI MCP server expose?
WunderUI exposes 11 tools: list_components, get_component, get_tokens, get_design_md, list_templates, and 6 more. Their descriptions and schemas cost roughly 889 tokens of context every time the server is loaded.
Is the WunderUI MCP server still maintained?
WunderUI is still listed as active in the MCP registry. We last reached this channel on 4 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 WunderUI MCP server under?
WunderUI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.