io.github.TN0123/one-shot-ui
NPM · ONE-SHOT-UI · SCANNED SEP 24
Deterministic UI extraction and screenshot diffing for AI coding agents.
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects sharp 0.34.5, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 38 of 143 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 67 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 877 tokens (~175/item across 5 items; 5 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 5 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.TN0123/one-shot-ui MCP server?
io.github.TN0123/one-shot-ui runs locally as an npm package, launched with npx -y one-shot-ui. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · one-shot-ui
claude mcp add tn0123-one-shot-ui -- npx -y one-shot-ui
{
"mcpServers": {
"tn0123-one-shot-ui": {
"command": "npx",
"args": [
"-y",
"one-shot-ui"
]
}
}
} {
"servers": {
"tn0123-one-shot-ui": {
"command": "npx",
"args": [
"-y",
"one-shot-ui"
]
}
}
} codex mcp add tn0123-one-shot-ui -- npx -y one-shot-ui
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tn0123-one-shot-ui": {
"type": "local",
"command": [
"npx",
"-y",
"one-shot-ui"
],
"enabled": true
}
}
} openclaw mcp add tn0123-one-shot-ui --command npx --arg -y --arg one-shot-ui
mcp_servers:
tn0123-one-shot-ui:
command: "npx"
args: ["-y", "one-shot-ui"] {
"McpServers": {
"tn0123-one-shot-ui": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"one-shot-ui"
]
}
}
} assistant mcp add tn0123-one-shot-ui -t stdio -c npx -a -y one-shot-ui
{
"mcpServers": {
"tn0123-one-shot-ui": {
"command": "npx",
"args": [
"-y",
"one-shot-ui"
]
}
}
} 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.
- 24 Sept 26 +1
- Stability: 0.97 → pass security
- 22 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.
- 20 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.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 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.
- 13 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.
- 12 Sept 26 −3
- Stability: pass → 0.83 functional
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 24 Sept 2026 · Analysed npm/one-shot-ui@0.7.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 →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-f88m-g3jw-g9cj | high | yes | ||
| GHSA-rgj7-g3m4-5g8c | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 143 packages
| Packages resolved | 143 |
|---|---|
| Stale | 38 |
| 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 →
compare Compare a build against a reference screenshot ~264
Deterministically diff an implementation screenshot against a reference screenshot. Returns a pixel-mismatch ratio, width/height deltas, and a ranked list of structural issues (missing/extra elements, position, size, color, shadow, spacing), plus an irreducible-mismatch floor so you know when further pixel-chasing is futile. Inputs are image file paths (PNG/JPG); the same inputs always produce the same numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_resize | boolean | – | Resize the implementation to the reference's dimensions before diffing. |
| disable_ocr | boolean | – | Skip OCR text extraction. OCR runs by default and roughly doubles latency; disable it when you don't need text content or typography (note: extract then returns empty fontSizes). |
| heatmap_path | string | – | If set, write a diff heatmap PNG to this path. |
| implementation_path | string | yes | Path (absolute, or relative to the server's launch directory) to the current build screenshot. |
| reference_path | string | yes | Path (absolute, or relative to the server's launch directory) to the reference (design) screenshot. |
| region | string | – | Limit the diff to a named semantic anchor from the reference. |
| top | integer | – | Maximum number of issues to return (default 20). |
No output schema declared.
No examples provided.
extract Extract structured design data from a screenshot ~168
Analyze a single reference screenshot into structured data an agent can build from: layout regions (position/size), dominant colors, typography, spacing, and a suggested implementation strategy. Returns a compact summary by default; set full=true for the complete report. Input is an image file path.
| Name | Type | Req | Description |
|---|---|---|---|
| disable_ocr | boolean | – | Skip OCR text extraction. OCR runs by default and roughly doubles latency; disable it when you don't need text content or typography (note: extract then returns empty fontSizes). |
| fine | boolean | – | Use fine-grained (4px) layout detection for small details. |
| full | boolean | – | Return the full detailed report instead of the compact summary. |
| image_path | string | yes | Path (absolute, or relative to the server's launch directory) to the screenshot to analyze. |
No output schema declared.
No examples provided.
plan Generate an implementation strategy from a screenshot ~105
Generate a suggested implementation plan (layout strategy, CSS primitives, repeated patterns, typography notes) from a reference screenshot. Input is an image file path.
| Name | Type | Req | Description |
|---|---|---|---|
| disable_ocr | boolean | – | Skip OCR text extraction. OCR runs by default and roughly doubles latency; disable it when you don't need text content or typography (note: extract then returns empty fontSizes). |
| image_path | string | yes | Path (absolute, or relative to the server's launch directory) to the screenshot to analyze. |
No output schema declared.
No examples provided.
suggest_fixes Get ranked fix suggestions from a diff ~240
Diff a build against a reference and return concrete, ranked fix observations (size, color, shadow, spacing) with values measured from the reference. Selectors are only emitted when they resolve from real DOM; for screenshot-only input the fixes are region-anchored observations with capped confidence rather than guessed selectors. Inputs are image file paths.
| Name | Type | Req | Description |
|---|---|---|---|
| disable_ocr | boolean | – | Skip OCR text extraction. OCR runs by default and roughly doubles latency; disable it when you don't need text content or typography (note: extract then returns empty fontSizes). |
| framework | string | – | Output format: react or vanilla (default react). |
| implementation_path | string | yes | Path (absolute, or relative to the server's launch directory) to the current build screenshot. |
| reference_path | string | yes | Path (absolute, or relative to the server's launch directory) to the reference (design) screenshot. |
| region | string | – | Limit fixes to a named semantic anchor from the reference. |
| styling | string | – | Styling output: tailwind or css (default tailwind). |
| top | integer | – | Maximum number of fixes to return (default 20). |
No output schema declared.
No examples provided.
tokens Extract design tokens from a screenshot ~100
Extract design tokens (color palette, spacing scale, radii) from a reference screenshot. Input is an image file path.
| Name | Type | Req | Description |
|---|---|---|---|
| disable_ocr | boolean | – | Skip OCR text extraction. OCR runs by default and roughly doubles latency; disable it when you don't need text content or typography (note: extract then returns empty fontSizes). |
| image_path | string | yes | Path (absolute, or relative to the server's launch directory) to the screenshot to analyze. |
No output schema declared.
No examples provided.
What is the io.github.TN0123/one-shot-ui MCP server?
io.github.TN0123/one-shot-ui is an MCP server listed in the public MCP registry as io.github.TN0123/one-shot-ui. Deterministic UI extraction and screenshot diffing for AI coding agents. This page covers its npm package (one-shot-ui).
Is the io.github.TN0123/one-shot-ui MCP server safe to use?
io.github.TN0123/one-shot-ui scores 79 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 24 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.TN0123/one-shot-ui MCP server expose?
io.github.TN0123/one-shot-ui exposes 5 tools: compare, extract, suggest_fixes, tokens, plan. Their descriptions and schemas cost roughly 877 tokens of context every time the server is loaded.
Is the io.github.TN0123/one-shot-ui MCP server still maintained?
io.github.TN0123/one-shot-ui is still listed as active in the MCP registry. We last reached this channel on 24 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.TN0123/one-shot-ui MCP server under?
io.github.TN0123/one-shot-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.