# io.github.soo-kate/framingui (npm · @framingui/mcp)

FramingUI design-system tools for coding agents: validate screens, check wiring, browse the catalog.

- Trust score: 83/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- npm · `@framingui/mcp`: 83/100 (this document), [markdown](https://verifymcp.io/servers/soo-kate-framingui/framingui-mcp.md), [page](https://verifymcp.io/servers/soo-kate-framingui/framingui-mcp)

## Channel facts

- Registry: `npm`
- Package: `@framingui/mcp`
- Version: `0.1.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-09-22.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **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 34 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 555 tokens (~138/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.soo-kate/framingui MCP server?

io.github.soo-kate/framingui runs locally as an npm package, launched with npx -y @framingui/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add soo-kate-framingui -- npx -y @framingui/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "soo-kate-framingui": {
      "command": "npx",
      "args": [
        "-y",
        "@framingui/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "soo-kate-framingui": {
      "command": "npx",
      "args": [
        "-y",
        "@framingui/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add soo-kate-framingui -- npx -y @framingui/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "soo-kate-framingui": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@framingui/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add soo-kate-framingui --command npx --arg -y --arg @framingui/mcp
```

### Hermes

```yaml
mcp_servers:
  soo-kate-framingui:
    command: "npx"
    args: ["-y", "@framingui/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "soo-kate-framingui": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@framingui/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add soo-kate-framingui -t stdio -c npx -a -y @framingui/mcp
```

### Other

```json
{
  "mcpServers": {
    "soo-kate-framingui": {
      "command": "npx",
      "args": [
        "-y",
        "@framingui/mcp"
      ]
    }
  }
}
```

## 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-09-21 (score 83, +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.

### 2026-09-19 (score 82, +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.

### 2026-09-18 (score 81, −3)

- [functional] Stability: pass → 0.80

### 2026-09-17 (score 84, 0)

- [security] Stability: 0.97 → pass

### 2026-09-16 (score 84, +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.

### 2026-09-14 (score 83, +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.

### 2026-09-12 (score 82, +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.

### 2026-09-10 (score 81, +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.

## MCP tools (4)

### `framingui_doctor` (~97 tokens)

FramingUI doctor

Verify FramingUI wiring in a project. Runs the skill's doctor script against projectPath and reports pass/warn/fail checks on the setup (theme CSS variables, component availability, project config). Covers the free scope of FramingUI (editorial-tech theme + 30 components). Exit code 0 = healthy, 1 = problems found.

Input parameters:

- `projectPath` (string, required): Absolute path to the project directory to check.

### `framingui_validate_screen` (~167 tokens)

Validate FramingUI screen

Validate a FramingUI screen definition (JSON object) against the design-system contract: shell/page/section tokens, component vocabulary, props, and theme. Returns the validator report verbatim. The free scope is the editorial-tech theme + 30 components; vocabulary outside it produces LICENSE_REQUIRED errors, which must be surfaced to the user unchanged. Pass projectPath to validate against that project's FramingUI configuration (enabled packs, local recipes). Exit code 0 = valid, 1 = invalid, 2 = could not validate.

Input parameters:

- `projectPath` (string): Optional absolute path to the project whose FramingUI configuration (enabled packs, local recipes) the screen should be validated against.
- `screenJson` (object, required): The screen definition as a JSON object (not a string).

### `framingui_catalog` (~103 tokens)

FramingUI catalog reference

Return a FramingUI reference document as markdown: 'components' (the 30 free-scope components with props and variants), 'themes' (the free editorial-tech theme), 'tokens' (the token vocabulary), or 'recipes' (approved screen recipes). These references cover the free scope of FramingUI; the full catalog is at https://framingui.com?ref=mcp-official.

Input parameters:

- `kind` (string, required): Which reference document to return.

### `framingui_recipe_show` (~103 tokens)

Show FramingUI recipe

Show one FramingUI screen recipe as JSON (anatomy, hierarchy, capabilities, states, responsive rules, accessibility requirements, acceptance criteria). Runs the skill's recipe script: `recipe show <id> --json`. Use framingui_catalog with kind 'recipes' to list available recipe ids. Recipes ship with the free scope of FramingUI.

Input parameters:

- `id` (string, required): Recipe id, e.g. 'dashboard-overview' or 'conversation-thread'.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/soo-kate-framingui/framingui-mcp#diagnostics

## Score history

- 2026-09-22: 83
- 2026-09-21: 83
- 2026-09-20: 82
- 2026-09-19: 82
- 2026-09-18: 81
- 2026-09-17: 84
- 2026-09-16: 84
- 2026-09-15: 83
- 2026-09-14: 83
- 2026-09-13: 82
- 2026-09-12: 82
- 2026-09-11: 81
- 2026-09-10: 81
- 2026-09-09: 80
- 2026-09-08: 80
- 2026-09-07: 80
- 2026-09-06: 79
- 2026-09-05: 79
- 2026-09-04: 78
- 2026-09-03: 78
- 2026-09-02: 77
- 2026-09-01: 77
- 2026-08-31: 76
- 2026-08-30: 76
- 2026-08-29: 75
- 2026-08-28: 75
- 2026-08-27: 74
- 2026-08-26: 74
- 2026-08-25: 69
- 2026-08-24: 69

## Common questions

### What is the io.github.soo-kate/framingui MCP server?

io.github.soo-kate/framingui is an MCP server listed in the public MCP registry as io.github.soo-kate/framingui. FramingUI design-system tools for coding agents: validate screens, check wiring, browse the catalog. This page covers its npm package (@framingui/mcp).

### Is the io.github.soo-kate/framingui MCP server safe to use?

io.github.soo-kate/framingui scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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.soo-kate/framingui MCP server expose?

io.github.soo-kate/framingui exposes 4 tools: framingui_doctor, framingui_validate_screen, framingui_catalog, framingui_recipe_show. Their descriptions and schemas cost roughly 470 tokens of context every time the server is loaded.

### Is the io.github.soo-kate/framingui MCP server still maintained?

io.github.soo-kate/framingui is still listed as active in the MCP registry. We last reached this channel on 22 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.soo-kate/framingui MCP server under?

io.github.soo-kate/framingui declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@framingui/mcp
- Socket report: https://socket.dev/npm/package/@framingui/mcp
- Repository: https://github.com/soo-kate/framingui-skill
- Website: https://framingui.com/
- Changelog RSS feed: https://verifymcp.io/servers/soo-kate-framingui/framingui-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/soo-kate-framingui/framingui-mcp.json
- HTML version of this page: https://verifymcp.io/servers/soo-kate-framingui/framingui-mcp