io.github.pudge-studio/pudge-ui

NPM · @PUDGE-UI/MCP-SERVER · SCANNED AUG 3

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

Available components

+46 this week 70 70 Trust /100

Trust breakdown (6 categories)

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 →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency45

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 25 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability83

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 Management23

Stability observed for 7 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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @pudge-ui/mcp-server

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# add to Codex CLI

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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.json

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

Changelog

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.

2 Aug 26 +63
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Stability: unverified → 0.20 ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
1 Aug 26 −14
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
31 Jul 26 +15
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −40
- Malware scan: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
28 Jul 26 +22
- 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 functional
27 Jul 26 24

First indexed and scored.

Show 4 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Analysed npm/@pudge-ui/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 96 packages

96 packages in the resolved dependency tree · 96 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 6 exposed · ~674 tokens

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.

Tool Tokens

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

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug