io.github.soo-kate/framingui
NPM · @FRAMINGUI/MCP · SCANNED SEP 22
FramingUI design-system tools for coding agents: validate screens, check wiring, browse the catalog.
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 96 dependencies flagged as unhealthy. 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 34 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.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.
npm · @framingui/mcp
claude mcp add soo-kate-framingui -- npx -y @framingui/mcp
{
"mcpServers": {
"soo-kate-framingui": {
"command": "npx",
"args": [
"-y",
"@framingui/mcp"
]
}
}
} {
"servers": {
"soo-kate-framingui": {
"command": "npx",
"args": [
"-y",
"@framingui/mcp"
]
}
}
} codex mcp add soo-kate-framingui -- npx -y @framingui/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"soo-kate-framingui": {
"type": "local",
"command": [
"npx",
"-y",
"@framingui/mcp"
],
"enabled": true
}
}
} openclaw mcp add soo-kate-framingui --command npx --arg -y --arg @framingui/mcp
mcp_servers:
soo-kate-framingui:
command: "npx"
args: ["-y", "@framingui/mcp"] {
"McpServers": {
"soo-kate-framingui": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@framingui/mcp"
]
}
}
} assistant mcp add soo-kate-framingui -t stdio -c npx -a -y @framingui/mcp
{
"mcpServers": {
"soo-kate-framingui": {
"command": "npx",
"args": [
"-y",
"@framingui/mcp"
]
}
}
} 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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
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 22 Sept 2026 · Analysed npm/@framingui/mcp@0.1.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 96 packages
| Packages resolved | 96 |
|---|---|
| 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 →
framingui_catalog FramingUI catalog reference ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Which reference document to return. |
No output schema declared.
No examples provided.
framingui_doctor FramingUI doctor ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | yes | Absolute path to the project directory to check. |
No output schema declared.
No examples provided.
framingui_recipe_show Show FramingUI recipe ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Recipe id, e.g. 'dashboard-overview' or 'conversation-thread'. |
No output schema declared.
No examples provided.
framingui_validate_screen Validate FramingUI screen ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | – | Optional absolute path to the project whose FramingUI configuration (enabled packs, local recipes) the screen should be validated against. |
| screenJson | object | yes | The screen definition as a JSON object (not a string). |
No output schema declared.
No examples provided.
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.