io.github.pudge-studio/pudge-ui
NPM · @PUDGE-UI/MCP-SERVER · SCANNED SEP 21
Query pudge-ui — 93 skeuomorphic 2000s-era UI component specs — for coding-agent context.
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 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
- 31 of 97 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 74 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 674 tokens (~112/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 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 io.github.pudge-studio/pudge-ui MCP server?
io.github.pudge-studio/pudge-ui runs locally as an npm package, launched with npx -y @pudge-ui/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pudge-ui/mcp-server
claude mcp add pudge-studio-pudge-ui -- npx -y @pudge-ui/mcp-server
{
"mcpServers": {
"pudge-studio-pudge-ui": {
"command": "npx",
"args": [
"-y",
"@pudge-ui/mcp-server"
]
}
}
} {
"servers": {
"pudge-studio-pudge-ui": {
"command": "npx",
"args": [
"-y",
"@pudge-ui/mcp-server"
]
}
}
} codex mcp add pudge-studio-pudge-ui -- npx -y @pudge-ui/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pudge-studio-pudge-ui": {
"type": "local",
"command": [
"npx",
"-y",
"@pudge-ui/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add pudge-studio-pudge-ui --command npx --arg -y --arg @pudge-ui/mcp-server
mcp_servers:
pudge-studio-pudge-ui:
command: "npx"
args: ["-y", "@pudge-ui/mcp-server"] {
"McpServers": {
"pudge-studio-pudge-ui": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@pudge-ui/mcp-server"
]
}
}
} assistant mcp add pudge-studio-pudge-ui -t stdio -c npx -a -y @pudge-ui/mcp-server
{
"mcpServers": {
"pudge-studio-pudge-ui": {
"command": "npx",
"args": [
"-y",
"@pudge-ui/mcp-server"
]
}
}
} 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
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
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 21 Sept 2026 · Analysed npm/@pudge-ui/mcp-server@0.2.0
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 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| 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_component ~129
Get the full spec for one pudge-ui component: its physical analog (the real 2000s hardware it imitates), mechanism, exact CSS recipe, and constraints — with the foundation prepended so the result is self-contained. This is the spec you hand to a coding agent to build the component in any stack (CSS, React Native, SwiftUI, Compose, Flutter). Accepts a component id or display name (e.g. 'push-button' or 'Push Button').
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Component id or name, e.g. 'push-button' or 'Push Button' |
No output schema declared.
No examples provided.
get_components ~83
Get full specs for several pudge-ui components at once, with the shared foundation included a single time (deduplicated) to save context. Use when building a screen that needs multiple components — pass an array of component ids or names.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | Array of component ids or names, e.g. ['volume-slider', 'vu-meter', 'lcd'] |
No output schema declared.
No examples provided.
get_composition ~83
Get a pudge-ui composition — a pre-assembled multi-component layout (e.g. 'audio-mixer-strip') — with every referenced component spec inlined and the foundation included once. Use to build a complete, cohesive interface in one shot rather than wiring components together yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Composition name, e.g. 'audio-mixer-strip' |
No output schema declared.
No examples provided.
get_foundation ~110
Get the pudge-ui foundation: the design-system rules every component depends on. Core (default) returns 5 docs — philosophy, tokens, materials, depth-model, naming. Set extended=true for all 9 (adds theme, accessibility, layout, canvas). Load this once at the start of a build so the agent applies the depth model, material recipes, and warm-neutral palette correctly.
| Name | Type | Req | Description |
|---|---|---|---|
| extended | boolean | – | Include all 9 foundation docs (default: false → core 5 docs) |
No output schema declared.
No examples provided.
list_components ~153
List pudge-ui components — 93 skeuomorphic UI specs across 11 categories (buttons, toggles, dials, sliders, readouts, meters, navigation, forms, overlays, indicators, data). Returns each component's id, name, category, and one-line description. Optionally filter by category id. Use this first to discover what exists, then call get_component for full specs.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category id to filter by, e.g. 'buttons', 'toggles', 'dials', 'sliders', 'readouts', 'meters', 'navigation', 'forms', 'overlays', 'indicators', 'data'. Omit to list all 93 components. |
No output schema declared.
No examples provided.
search_components ~116
Fuzzy-search pudge-ui components by name, description, or tag (e.g. 'volume', 'knob', 'LCD', 'walkman'). Returns ranked matches with id, name, category, and description. Use this when you know what the user wants but not the exact component id; then call get_component with the best match.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results, 1–50 (default 10) |
| query | string | yes | Free-text search query (matched against name, description, and tags) |
No output schema declared.
No examples provided.
What is the io.github.pudge-studio/pudge-ui MCP server?
io.github.pudge-studio/pudge-ui is an MCP server listed in the public MCP registry as io.github.pudge-studio/pudge-ui. Query pudge-ui, 93 skeuomorphic 2000s-era UI component specs, for coding-agent context. This page covers its npm package (@pudge-ui/mcp-server).
Is the io.github.pudge-studio/pudge-ui MCP server safe to use?
io.github.pudge-studio/pudge-ui scores 85 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. 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 io.github.pudge-studio/pudge-ui MCP server expose?
io.github.pudge-studio/pudge-ui exposes 6 tools: list_components, search_components, get_foundation, get_component, get_components, get_composition. Their descriptions and schemas cost roughly 674 tokens of context every time the server is loaded.
Is the io.github.pudge-studio/pudge-ui MCP server still maintained?
io.github.pudge-studio/pudge-ui 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 io.github.pudge-studio/pudge-ui MCP server under?
io.github.pudge-studio/pudge-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.