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.joselhurtado/uxui-principles

NPM · @UXUIPRINCIPLES/MCP-SERVER

195 UX/UI principles with citations, 12 UX smells, 12 flow checklists, 8 required rules, EN/ES.

+3 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 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 & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2693 tokens (~192/item across 14 items; 14 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 Management47
  • Stability observed for 14 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 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 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 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.

  • 9 Nov 26 +1
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Schema quality: 2293 → 2693 ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.07 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 1.2.1 → 1.3.0 functional
  • 8 Nov 26 +10
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.85 ▲ functional
  • 7 Nov 26 59

    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/@uxuiprinciples/mcp-server@1.3.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 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~2,466 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
audit_interface ~205

Audit a described screen or flow: returns findings mapped to principles and UX smells, each with severity, remediation and business impact, plus a score, the detected interface type, strengths and the three priority fixes. Pro mode only (UXUI_API_KEY set): the audit runs on the uxuiprinciples.com API. Without a key use detect_smell then suggest_fix, which run offline.

NameTypeReqDescription
contextstring–Where the interface lives. Echoed in the result; does not change the rules.
depthstring–"quick": the top 5 findings. "full": every finding. Defaults to "full".
descriptionstringyesWhat the screen shows and what users do or complain about, 20 to 5000 characters. Name the components, the actions and the states you implemented (loading, empty, error, confirmation).
localestring–Language of the findings: "en" or "es". Defaults to "en".

No output schema declared.

No examples provided.

check_requirements ~346

Check a screen you built or designed against eight experience requirements: confirmation before consequential actions, error state, empty state, loading state, undo or edit, sources on AI output, recovery after an AI error, consent before automation. Describe the screen as data (flow, components, actions with flags, states implemented) and get pass, fail or not_applicable per rule, each with the principle it comes from and its citations, plus a markdown summary. Call it after generating or changing a screen and fix every fail. Pro mode only (UXUI_API_KEY set); without a key use generate_checklist for the unevaluated checklist.

NameTypeReqDescription
actionsarray–The actions the screen offers, with their flags.
componentsarray–What is on the screen, one item per component, in plain words (e.g., "search input", "results table", "AI summary panel"). Words such as form, table, list, search, chart, AI, chat or summary decide w…
flowstring–The flow the screen belongs to. One of: "onboarding", "forms", "pricing", "dashboard", "empty-states", "checkout", "settings", "navigation", "search", "authentication", "notifications", "data-tables"…
localestring–Language of the verdicts and the summary: "en" or "es". Defaults to "en".
states_implementedarray–The states the implementation has: loading, empty, error, success, confirmation, undo, edit, sources, recovery, consent. Only list what is built.

No output schema declared.

No examples provided.

detect_smell ~147

Detect which UX smells match a plain-language description of an interface problem or a user complaint, in English or Spanish. Returns the matched smells with a confidence level and the suggested fix for each. Use it as the first step when a UI "feels off" and the cause is not named yet; runs offline.

NameTypeReqDescription
descriptionstringyesWhat is wrong, in the user's or the team's words (e.g., "users say the dashboard is too cluttered and they don't know where to start", "el formulario es demasiado largo").
localestring–Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".

No output schema declared.

No examples provided.

generate_checklist ~189

Generate the pre-flight (before design) or post-flight (before ship) checklist for one user flow. Returns the checklist as structured items (each tied to a principle) and as ready-to-paste markdown. Use it to review a design or a pull request against the flow it implements.

NameTypeReqDescription
flow_idstringyesThe flow id. One of: "onboarding", "forms", "pricing", "dashboard", "empty-states", "checkout", "settings", "navigation", "search", "authentication", "notifications", "data-tables". Call list_flows f…
localestring–Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".
phasestringyesWhich checklist to generate: "preflight" (before design) or "postflight" (before ship).

No output schema declared.

No examples provided.

get_flow ~158

Get one user flow (onboarding, forms, pricing, dashboard, checkout, search, authentication and more) with its target metrics, the pre-flight checklist to run before designing it and the post-flight checklist to run before shipping it. Use it before designing or shipping a known flow.

NameTypeReqDescription
idstringyesThe flow id. One of: "onboarding", "forms", "pricing", "dashboard", "empty-states", "checkout", "settings", "navigation", "search", "authentication", "notifications", "data-tables". Call list_flows f…
localestring–Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".

No output schema declared.

No examples provided.

get_flow_principles ~149

Get the key principles that govern one user flow and the UX smells that most often break it. Returns the principle slugs and the smell ids so you can read them with get_principle and get_smell. Use it to ground a flow review in evidence.

NameTypeReqDescription
flow_idstringyesThe flow id. One of: "onboarding", "forms", "pricing", "dashboard", "empty-states", "checkout", "settings", "navigation", "search", "authentication", "notifications", "data-tables".
localestring–Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".

No output schema declared.

No examples provided.

get_principle ~173

Get one UX/UI principle by slug: title, code, part, difficulty, summary, the bibliographic citations behind it (author, title, year, url) and the link to the full guide on uxuiprinciples.com. With UXUI_API_KEY set (pro mode) the full guide body comes back in `content`. Use it to identify, summarize or cite a specific principle; use search_principles first when you only have a topic.

NameTypeReqDescription
localestring–Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".
slugstringyesThe principle slug as returned by search_principles or list_principles (e.g., "cognitive-load", "hicks-law", "fitts-law").

No output schema declared.

No examples provided.

get_principle_prompts ~142

Get the ready-to-use AI prompts attached to one principle (prompts to apply, audit or refactor an interface against it). With UXUI_API_KEY set (pro mode) the prompt texts come back in `prompts`; without it the prompts belong to the paid Principles Library and the tool returns the count and the URL of the guide. Call get_principle first if you only need the summary.

NameTypeReqDescription
localestring–Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".
slugstringyesThe principle slug (e.g., "cognitive-load").

No output schema declared.

No examples provided.

get_smell ~148

Get one UX smell (interface anti-pattern) by id: name, tagline, symptoms, the Nielsen heuristic it breaks, a step-by-step fix recipe with a time estimate, the related principles and an audit prompt plus a refactoring prompt. Use it once you know the smell id, from list_smells or detect_smell.

NameTypeReqDescription
idstringyesThe smell id (e.g., "overloaded-screen", "form-graveyard", "silent-errors", "ai-gradient-cliche"). Call list_smells for the full set.
localestring–Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".

No output schema declared.

No examples provided.

list_flows ~123

List the 12 user flows covered by the checklists (onboarding, forms, pricing, dashboard, empty states, checkout, settings, navigation, search, authentication, notifications, data tables) with the target metric of each. Returns id, name, description, metric target and the number of checklist items per phase. Use it to pick the id for get_flow, generate_checklist or get_flow_principles.

NameTypeReqDescription
localestring–Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".

No output schema declared.

No examples provided.

list_principles ~152

List the 195 UX/UI principles, optionally one part at a time. Returns principle summaries (slug, title, code, part name, summary), the total count and the list of part ids. Use it to browse the catalogue or to learn the part ids for search_principles.

NameTypeReqDescription
limitnumber–Maximum number of principles to return. Defaults to 20.
localestring–Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".
partstring–Restrict to one part, by id or name (e.g., "part-1", "part-2"). Omit for every part.

No output schema declared.

No examples provided.

list_smells ~144

List the 12 UX smells (interface anti-patterns such as overloaded screens, form graveyards, silent errors or the AI-aesthetic cliches), optionally filtered by category. Returns id, name, short name, tagline, category and Nielsen heuristic for each. Use it to browse the catalogue before get_smell.

NameTypeReqDescription
categorystring–Restrict to one category (e.g., "efficiency", "feedback", "error-prevention", "accessibility", "ai-aesthetic"). Omit for every smell.
localestring–Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".

No output schema declared.

No examples provided.

search_principles ~228

Search the 195 UX/UI principles by free text, part, difficulty or tags. Returns the matching principles with slug, title, code, part name and summary, plus the total count. Use it to find which principles apply to a design question before calling get_principle.

NameTypeReqDescription
difficultystring–Restrict to one difficulty level.
limitnumber–Maximum number of principles to return. Defaults to 10.
localestring–Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".
partstring–Restrict to one part of the catalogue, by id or name (e.g., "part-1", "Foundations"). Call list_principles to see the parts.
querystring–Free-text query matched against title, slug, summary and tags (e.g., "form validation", "loading states", "choice overload").
tagsarray–Restrict to principles carrying every listed tag (e.g., ["forms", "errors"]).

No output schema declared.

No examples provided.

suggest_fix ~162

Get a fix for a described UX issue: detects the most likely smell (or uses the one you pass), then returns its step-by-step fix recipe, the principles to apply and a refactoring prompt you can hand to a coding agent. Use it when you want an actionable remedy rather than a diagnosis; runs offline.

NameTypeReqDescription
issuestringyesThe UX issue to fix, in plain language (e.g., "the checkout asks for account creation before showing the price").
localestring–Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".
smell_idstring–Optional smell id to skip detection when the smell is already known (e.g., "dead-end-states").

No output schema declared.

No examples provided.

Install

How do I install the io.github.joselhurtado/uxui-principles MCP server?

io.github.joselhurtado/uxui-principles runs locally as an npm package, launched with npx -y @uxuiprinciples/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @uxuiprinciples/mcp-server

# add to Claude Code
claude mcp add joselhurtado-uxui-principles -- npx -y @uxuiprinciples/mcp-server
Common questions

What is the io.github.joselhurtado/uxui-principles MCP server?

io.github.joselhurtado/uxui-principles is an MCP server listed in the public MCP registry as io.github.joselhurtado/uxui-principles. 195 UX/UI principles with citations, 12 UX smells, 12 flow checklists, 8 required rules, EN/ES. This page covers its npm package (@uxuiprinciples/mcp-server).

Is the io.github.joselhurtado/uxui-principles MCP server safe to use?

io.github.joselhurtado/uxui-principles scores 75 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. 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.joselhurtado/uxui-principles MCP server expose?

io.github.joselhurtado/uxui-principles exposes 14 tools: get_principle, search_principles, list_principles, get_principle_prompts, get_smell, and 9 more. Their descriptions and schemas cost roughly 2,466 tokens of context every time the server is loaded.

Is the io.github.joselhurtado/uxui-principles MCP server still maintained?

io.github.joselhurtado/uxui-principles 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.joselhurtado/uxui-principles MCP server under?

io.github.joselhurtado/uxui-principles 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.joselhurtado/uxui-principles MCP server?

VerifyMCP ran 16 checks on io.github.joselhurtado/uxui-principles, 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.