Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.mishaovcharenko/uiscanner

NPM · UISCANNER-MCP

Design tokens + a build prompt from any URL, right inside Claude Code, Cursor, and Codex.

Available components

0 this week 75 Trust /100

Last scanned (22 hours ago)

Scores higher than 51% of npm servers

Category Design and Media

Trust breakdown (7 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 → 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 zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 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 11 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 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
  • 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
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 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.

  • 10 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 4 Nov 26 0
    • Stability: 0.97 → pass security
  • 3 Nov 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.

  • 2 Nov 26 −1
    • Stability: pass → 0.93 functional
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 21 Nov 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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~493 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. 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 →

Tool Tokens
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.

NameTypeReqDescription
idstringyesA teardown id, or a uiscanner.com/t/<id> link.
include_screenshotboolean–Also return the rendered page as an image. Default false.
NameTypeReqDescription
anti_slop–––
brand–––
completeness–––
created_atstring|null––
design_mdstring|null––
dimensions–––
domainstring––
freshness–––
full_screenshot_urlstring|null––
idstring––
promptstring|null––
scorenumber|null––
score_bandstring|null––
sections–––
source_urlstring––
targetstring––
tokens–––
urlstring––

No examples provided.

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.

NameTypeReqDescription
idstringyesA teardown id, or a uiscanner.com/t/<id> link.
targetstringyesThe archetype to re-tailor the build prompt for.
NameTypeReqDescription
anti_slop–––
brand–––
completeness–––
created_atstring|null––
design_mdstring|null––
dimensions–––
domainstring––
freshness–––
full_screenshot_urlstring|null––
idstring––
promptstring|null––
scorenumber|null––
score_bandstring|null––
sections–––
source_urlstring––
targetstring––
tokens–––
urlstring––

No examples provided.

ui_probe ~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.

NameTypeReqDescription
urlstringyesPublic URL to check, e.g. https://stripe.com
NameTypeReqDescription
cached–––
reasonstring|null––
scannableboolean––
urlstring––

No examples provided.

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.

NameTypeReqDescription
include_screenshotboolean–Also return the rendered page as an image. Larger payload; default false.
targetstring–What you're building, to tailor the prompt. Default: general.
urlstringyesPublic URL of the page to scan, e.g. https://stripe.com
NameTypeReqDescription
anti_slop–––
brand–––
completeness–––
created_atstring|null––
design_mdstring|null––
dimensions–––
domainstring––
freshness–––
full_screenshot_urlstring|null––
idstring––
promptstring|null––
scorenumber|null––
score_bandstring|null––
sections–––
source_urlstring––
targetstring––
tokens–––
urlstring––

No examples provided.

whoami ~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.

NameTypeReqDescription
authenticatedboolean––
creditsnumber––
planstring––
quota–––

No examples provided.

Install

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

# add to Claude Code
claude mcp add mishaovcharenko-uiscanner -- npx -y uiscanner-mcp
Common questions

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 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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 21 November 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.

What did VerifyMCP test on the io.github.mishaovcharenko/uiscanner MCP server?

VerifyMCP ran 15 checks on io.github.mishaovcharenko/uiscanner, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.mishaovcharenko/uiscanner: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.