# io.github.pudge-studio/pudge-ui (npm · @pudge-ui/mcp-server)

Query pudge-ui — 93 skeuomorphic 2000s-era UI component specs — for coding-agent context.

- Trust score: 70/100 (medium)
- Change this week: +46
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@pudge-ui/mcp-server`: 70/100 (this document), [markdown](https://verifymcp.io/servers/pudge-studio-pudge-ui/pudge-ui-mcp-server.md), [page](https://verifymcp.io/servers/pudge-studio-pudge-ui/pudge-ui-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@pudge-ui/mcp-server`
- Version: `0.2.0`
- 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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 25 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 674 tokens (~112/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add pudge-studio-pudge-ui -- npx -y @pudge-ui/mcp-server
```

### Codex

```bash
codex mcp add pudge-studio-pudge-ui -- npx -y @pudge-ui/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pudge-studio-pudge-ui": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pudge-ui/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pudge-studio-pudge-ui --command npx --arg -y --arg @pudge-ui/mcp-server
```

### Hermes

```yaml
mcp_servers:
  pudge-studio-pudge-ui:
    command: "npx"
    args: ["-y", "@pudge-ui/mcp-server"]
```

### Other

```json
{
  "mcpServers": {
    "pudge-studio-pudge-ui": {
      "command": "npx",
      "args": [
        "-y",
        "@pudge-ui/mcp-server"
      ]
    }
  }
}
```

## 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-08-02 (score 70, +63)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: fail → unverified
- [functional regression] Dependency health: partial → unverified
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] License: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → excellent
- [functional] Licence: MIT

### 2026-08-01 (score 7, −14)

- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Dependency health: unverified → partial

### 2026-07-31 (score 21, +15)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 6, −40)

- [security regression] Malware scan: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-28 (score 46, +22)

- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 24)

First indexed and scored.

## MCP tools (6)

### `list_components` (~153 tokens)

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.

Input parameters:

- `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.

### `search_components` (~116 tokens)

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.

Input parameters:

- `limit` (number): Max results, 1–50 (default 10)
- `query` (string, required): Free-text search query (matched against name, description, and tags)

### `get_foundation` (~110 tokens)

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.

Input parameters:

- `extended` (boolean): Include all 9 foundation docs (default: false → core 5 docs)

### `get_component` (~129 tokens)

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').

Input parameters:

- `name` (string, required): Component id or name, e.g. 'push-button' or 'Push Button'

### `get_components` (~83 tokens)

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.

Input parameters:

- `names` (array, required): Array of component ids or names, e.g. ['volume-slider', 'vu-meter', 'lcd']

### `get_composition` (~83 tokens)

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.

Input parameters:

- `name` (string, required): Composition name, e.g. 'audio-mixer-strip'

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pudge-studio-pudge-ui/pudge-ui-mcp-server#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 70
- 2026-08-01: 7
- 2026-07-31: 21
- 2026-07-30: 6
- 2026-07-28: 46
- 2026-07-27: 24

## Links

- npm package: https://www.npmjs.com/package/@pudge-ui/mcp-server
- Socket report: https://socket.dev/npm/package/@pudge-ui/mcp-server
- Repository: https://github.com/pudge-studio/pudge-ui
- Website: https://ui.pudgestudio.com/
- Changelog RSS feed: https://verifymcp.io/servers/pudge-studio-pudge-ui/pudge-ui-mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/pudge-studio-pudge-ui/pudge-ui-mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/pudge-studio-pudge-ui/pudge-ui-mcp-server