io.github.mishaovcharenko/uiscanner
NPM · UISCANNER-MCP · SCANNED SEP 25
Design tokens + a build prompt from any URL, right inside Claude Code, Cursor, and Codex.
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 & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 86 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 807 tokens (~134/item across 6 items; 5 tools + 1 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 Management83
- Stability observed for 25 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 7 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.mishaovcharenko/uiscanner MCP server?
io.github.mishaovcharenko/uiscanner runs locally as an npm package, launched with npx -y uiscanner-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 · uiscanner-mcp
claude mcp add mishaovcharenko-uiscanner -- npx -y uiscanner-mcp
{
"mcpServers": {
"mishaovcharenko-uiscanner": {
"command": "npx",
"args": [
"-y",
"uiscanner-mcp"
]
}
}
} {
"servers": {
"mishaovcharenko-uiscanner": {
"command": "npx",
"args": [
"-y",
"uiscanner-mcp"
]
}
}
} codex mcp add mishaovcharenko-uiscanner -- npx -y uiscanner-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mishaovcharenko-uiscanner": {
"type": "local",
"command": [
"npx",
"-y",
"uiscanner-mcp"
],
"enabled": true
}
}
} openclaw mcp add mishaovcharenko-uiscanner --command npx --arg -y --arg uiscanner-mcp
mcp_servers:
mishaovcharenko-uiscanner:
command: "npx"
args: ["-y", "uiscanner-mcp"] {
"McpServers": {
"mishaovcharenko-uiscanner": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"uiscanner-mcp"
]
}
}
} assistant mcp add mishaovcharenko-uiscanner -t stdio -c npx -a -y uiscanner-mcp
{
"mcpServers": {
"mishaovcharenko-uiscanner": {
"command": "npx",
"args": [
"-y",
"uiscanner-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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −2
- Stability: pass → 0.80 functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 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.
- 19 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.
- 17 Sept 26 −2
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 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.
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 25 Sept 2026 · Analysed npm/uiscanner-mcp@0.3.1
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 →
get_teardown Get teardown ~92
Fetch a finished teardown by its id or its uiscanner.com/t/<id> link. Returns the same tokens, sections, brand, and build prompt as ui_teardown, without re-scanning.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A teardown id, or a uiscanner.com/t/<id> link. |
| include_screenshot | boolean | – | Also return the rendered page as an image. Default false. |
| Name | Type | Req | Description |
|---|---|---|---|
| anti_slop | – | – | – |
| brand | – | – | – |
| completeness | – | – | – |
| created_at | string|null | – | – |
| design_md | string|null | – | – |
| dimensions | – | – | – |
| domain | string | – | – |
| freshness | – | – | – |
| full_screenshot_url | string|null | – | – |
| id | string | – | – |
| prompt | string|null | – | – |
| score | number|null | – | – |
| score_band | string|null | – | – |
| sections | – | – | – |
| source_url | string | – | – |
| target | string | – | – |
| tokens | – | – | – |
| url | string | – | – |
No examples provided.
retarget_teardown Retarget teardown ~90
Re-tailor a finished teardown's build prompt to a different archetype WITHOUT re-scanning (cheaper and faster than a new scan). Pass the teardown id or its link and the new target.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A teardown id, or a uiscanner.com/t/<id> link. |
| target | string | yes | The archetype to re-tailor the build prompt for. |
| Name | Type | Req | Description |
|---|---|---|---|
| anti_slop | – | – | – |
| brand | – | – | – |
| completeness | – | – | – |
| created_at | string|null | – | – |
| design_md | string|null | – | – |
| dimensions | – | – | – |
| domain | string | – | – |
| freshness | – | – | – |
| full_screenshot_url | string|null | – | – |
| id | string | – | – |
| prompt | string|null | – | – |
| score | number|null | – | – |
| score_band | string|null | – | – |
| sections | – | – | – |
| source_url | string | – | – |
| target | string | – | – |
| tokens | – | – | – |
| url | string | – | – |
No examples provided.
ui_probe Probe URL ~87
Cheap pre-flight before a scan: is a URL syntactically valid and public (not localhost / a private or blocked target), and is there a recent cached teardown to reuse? Spends no scan. Call it before ui_teardown to avoid wasting a scan on an unscannable URL.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public URL to check, e.g. https://stripe.com |
| Name | Type | Req | Description |
|---|---|---|---|
| cached | – | – | – |
| reason | string|null | – | – |
| scannable | boolean | – | – |
| url | string | – | – |
No examples provided.
ui_teardown UI teardown ~186
Scan any public website and get a design teardown: design tokens (colors, fonts, type scale, radii, spacing, shadows, motion), section structure, and a Claude-tailored build prompt to recreate the look. Describes and tokenizes, never copies asset bytes. Returns an id and a shareable uiscanner.com/t/<id> link. Takes up to ~3 minutes. Each scan spends one unit of your plan quota; prefer retarget_teardown over a second scan, and ui_probe first to avoid spending a scan on a blocked URL.
| Name | Type | Req | Description |
|---|---|---|---|
| include_screenshot | boolean | – | Also return the rendered page as an image. Larger payload; default false. |
| target | string | – | What you're building, to tailor the prompt. Default: general. |
| url | string | yes | Public URL of the page to scan, e.g. https://stripe.com |
| Name | Type | Req | Description |
|---|---|---|---|
| anti_slop | – | – | – |
| brand | – | – | – |
| completeness | – | – | – |
| created_at | string|null | – | – |
| design_md | string|null | – | – |
| dimensions | – | – | – |
| domain | string | – | – |
| freshness | – | – | – |
| full_screenshot_url | string|null | – | – |
| id | string | – | – |
| prompt | string|null | – | – |
| score | number|null | – | – |
| score_band | string|null | – | – |
| sections | – | – | – |
| source_url | string | – | – |
| target | string | – | – |
| tokens | – | – | – |
| url | string | – | – |
No examples provided.
whoami Account status ~38
Show the signed-in plan and scans remaining in the current window. Read-only; spends no scan. Worth calling before a batch of teardowns.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| authenticated | boolean | – | – |
| credits | number | – | – |
| plan | string | – | – |
| quota | – | – | – |
No examples provided.
What is the io.github.mishaovcharenko/uiscanner MCP server?
io.github.mishaovcharenko/uiscanner is an MCP server listed in the public MCP registry as io.github.mishaovcharenko/uiscanner. Design tokens + a build prompt from any URL, right inside Claude Code, Cursor, and Codex. This page covers its npm package (uiscanner-mcp).
Is the io.github.mishaovcharenko/uiscanner MCP server safe to use?
io.github.mishaovcharenko/uiscanner scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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.mishaovcharenko/uiscanner MCP server expose?
io.github.mishaovcharenko/uiscanner exposes 5 tools: ui_teardown, ui_probe, get_teardown, retarget_teardown, whoami. Their descriptions and schemas cost roughly 493 tokens of context every time the server is loaded.
Is the io.github.mishaovcharenko/uiscanner MCP server still maintained?
io.github.mishaovcharenko/uiscanner is still listed as active in the MCP registry. We last reached this channel on 25 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.mishaovcharenko/uiscanner MCP server under?
io.github.mishaovcharenko/uiscanner declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.