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.

UI Craft

NPM · UI-CRAFT-MCP

UI quality checks: anti-slop, accessibility, design tokens, scoring and workflow routing.

Available components

82 Trust /100

Last scanned (19 hours ago)

Scores higher than 71% of npm servers

Category Testing and QA

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 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 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to educlopez/ui-craft). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1442 tokens (~180/item across 8 items; 8 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 Management17
  • Stability observed for 5 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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 (16)

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

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 80

    First indexed and scored.

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/ui-craft-mcp@0.9.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo educlopez/ui-craft
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/educlopez/ui-craft/.github/workflows/npm-release.yml@refs/heads/main
Rekor log index 3924463057
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:e5080e8e63ab92b50374bc5a8d3a3b6649f8c1e2533eda81e4119d199859b4b6a5d71dbbc49b09f47cf7d24f4582e55535e98ce990b0d721705299ef1

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~1,442 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
acceptance_bar ~90

Returns the deterministic acceptance checklist for a UI surface. Data is bundled from recipe-dashboard.md, recipe-landing.md, recipe-auth.md, and finish-bar.md. Surfaces: dashboard, landing, auth, generic. Returns DATA only — no scoring or judgment. Scoring uses check_anti_slop + tokens_lint results.

NameTypeReqDescription
surfacestringyesThe UI surface to retrieve the acceptance bar for
NameTypeReqDescription
errorstring––
itemsarrayyes–
surfacestring|nullyes–

No examples provided.

check_anti_slop ~117

Scans source code for anti-slop violations using the deterministic rules from ui-craft-detect. Accepts either a `code` string (inline source) or a `path` string (file or directory). Returns findings with severity, rule ID, file, line, and message. These are the 43 deterministic rules only — no taste or aesthetic judgment.

NameTypeReqDescription
codestring–Inline source code to scan (alternative to path)
pathstring–File or directory path to scan (alternative to code)
NameTypeReqDescription
coverage–––
errorstring––
findingsarrayyes–
scan_errorsarray––
scan_policy–––
summaryobjectyes–
versionstring––

No examples provided.

check_fold ~261

Renders a URL and reports what its fold actually is: a screenshot, the composition class it belongs to, drift from the class you set out to build, three judged invariants, and four measurements reported WITHOUT a verdict. The unjudged four (identification, single dominance, asymmetry, restraint budget) are measured but not scored: calibration against reference landing pages showed those thresholds do not yet discriminate, so they are yours to interpret. Treat the screenshot as the primary output — look at it. Invariant 7 (a costly detail) is unmeasurable by construction: pass what you committed to as `costly_detail`, or it fails. Needs a browser: install puppeteer, or set UI_CRAFT_CHROME to an existing Chrome to skip the download.

NameTypeReqDescription
costly_detailstring–The one element of this fold that could not have come from a template, and what it cost
expected_classstring–The composition class you set out to build, to detect drift
heightinteger–Viewport height (default 900)
urlstringyesURL of the rendered page — a local dev server URL is fine
widthinteger–Viewport width (default 1440)
NameTypeReqDescription
checksarrayyes–
compositionobject––
driftstring|null––
drift_notestring–Why nothing was compared, when that is the case
drift_statusstring–Whether the built class was compared against an intended one at all. 'not-compared' means no expected_class was passed — an absent drift field is not evidence of none.
errorstring––
expected_classstring|null––
measured–––
observationsarray––
summaryobject––
urlstring––

No examples provided.

fold_candidates ~220

Draws composition classes for a landing fold, preferring ones this project has not spent yet. Variety cannot be requested in prose — asking a model to "be different" returns its default every time — so the class is drawn instead — ordered by a per-project seed, then by what this project has already spent. Pass the classes already used in this project as `used`. Classes: type-only, full-bleed-overlay, split, stacked, product-dominant, band. `split` is drawn last on purpose: it is the fold every generator reaches for unprompted. Returns each class with what it demands and what it sacrifices — the sacrifice is what makes a composition distinct.

NameTypeReqDescription
countinteger–How many candidates to draw (default 3)
seedstring–Overrides the per-project seed. Defaults to the working directory, which is what makes two projects draw differently while one project stays stable across runs.
usedarray–Composition class ids already used in this project (deprioritised in the draw)
NameTypeReqDescription
candidatesarrayyes–
errorstring––
instructionstring––
seeded_by––What the order was seeded by, so a caller knows it will repeat. Deliberately not a value derived from the seed: a digest of a guessable path is not redaction.
usedarray––

No examples provided.

route_task ~184

Call this FIRST on any UI request, before reading reference files. Takes the task in natural language and returns the references, commands and MCP tools that cover it, ranked, plus the single first move to make. Deterministic lexical ranking over a synonym map, so a prompt reaches the right entry even when its words do not match our filenames — "analytics panel" finds recipe-dashboard.md, which never says analytics. Recipes are also indexed by what they contain, so "pricing block" finds recipe-landing.md. Returns POINTERS only: every design rule stays in the files it points at. An unmatched prompt is reported as unmatched, not routed to a guess.

NameTypeReqDescription
limitinteger–Max hits per kind (default 5, clamped to 12)
promptstringyesThe task in natural language — e.g. "analytics panel with KPIs"
NameTypeReqDescription
conceptsarrayyes–
errorstring––
first_movestring|nullyes–
instructionstring––
intentstring––
promptstring|nullyes–
resultsobjectyes–

No examples provided.

score_ui ~255

Composite design-quality scorer (UICraftScore). Combines three deterministic dimensions into a single 0-100 score + letter grade (A/B/C/D/F) + per-dimension subscores and findings. Dimensions: anti-slop (38 rules via ui-craft-detect), token-discipline (raw hex / off-scale values), and static a11y (5 checks: img-no-alt, non-semantic-interactive, positive-tabindex, aria-invalid-no-describedby, no-reduced-motion). Accepts either a `code` string (inline source) or a `path` string (file). Formula: score = 100 − (antiSlop_crit×8) − (antiSlop_major×4) − (antiSlop_warn×1) − (token_findings×2) − (a11y_crit×8) − (a11y_major×4), clamped [0,100]. Returns { overall: {score, grade}, dimensions: {anti_slop, token_discipline, a11y}, version }.

NameTypeReqDescription
codestring–Inline source code to score (alternative to path)
pathstring–File path to score (alternative to code)
NameTypeReqDescription
coverage–––
dimensionsobjectyes–
errorstring––
overallobjectyes–
scan_errorsarray––
scan_policy–––
versionstring––

No examples provided.

tokens_lint ~101

Static analysis for off-system token values: raw hex colors, non-scale border-radius px values, non-8pt spacing values, and magic z-index integers. Token scale source of truth: references/tokens.md. Accepts `code` string or `path`. Returns structured findings + summary.

NameTypeReqDescription
codestring–Inline source code to lint (alternative to path)
pathstring–File or directory path to lint (alternative to code)
NameTypeReqDescription
coverage–––
errorstring––
findingsarrayyes–
scan_errorsarray––
scan_policy–––
summaryobjectyes–
versionstring––

No examples provided.

ux_coverage ~214

Returns the parts a screen of a given kind needs in order to be complete, and the contract for reporting them. This is the COMPLETENESS axis — "does this screen have the parts screens of its kind need". It is not the distinction axis: acceptance_bar and score_ui answer "is this designed". Report the two side by side; never fold coverage into a score, a count or a percentage. Report-only — coverage never gates and never fails a build. Archetypes: data-table, settings, search-filter, detail-view, empty-first-run, billing, pricing, docs-page, checkout, onboarding, destructive-confirm, invite-share. Call with no archetype to get the catalogue. dashboard, landing and auth are served by acceptance_bar instead. Returns DATA only — no scoring or judgment.

NameTypeReqDescription
archetypestring–Screen archetype to retrieve coverage parts for. Accepts the key, the label, or a synonym ("table", "plans", "are you sure"). Omit to list the catalogue.
NameTypeReqDescription
archetypestring|nullyes–
cataloguearray––
errorstring––
familystring––
itemsarrayyes–
labelstring––
notestring––
reportingobject––
statesarray––

No examples provided.

Install

How do I install the UI Craft MCP server?

UI Craft runs locally as an npm package, launched with npx -y ui-craft-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 · ui-craft-mcp

# add to Claude Code
claude mcp add educlopez-ui-craft -- npx -y ui-craft-mcp
Common questions

What is the UI Craft MCP server?

UI Craft is an MCP server listed in the public MCP registry as io.github.educlopez/ui-craft. UI quality checks: anti-slop, accessibility, design tokens, scoring and workflow routing. This page covers its npm package (ui-craft-mcp).

Is the UI Craft MCP server safe to use?

UI Craft scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 UI Craft MCP server expose?

UI Craft exposes 8 tools: route_task, check_anti_slop, tokens_lint, acceptance_bar, ux_coverage, and 3 more. Their descriptions and schemas cost roughly 1,442 tokens of context every time the server is loaded.

Is the UI Craft MCP server still maintained?

UI Craft 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 UI Craft MCP server under?

UI Craft 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 UI Craft MCP server?

VerifyMCP ran 16 checks on UI Craft, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.