# 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.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@uxuiprinciples/mcp-server`: 75/100 (this document), [markdown](https://verifymcp.io/servers/joselhurtado-uxui-principles/uxuiprinciples-mcp-server.md), [page](https://verifymcp.io/servers/joselhurtado-uxui-principles/uxuiprinciples-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@uxuiprinciples/mcp-server`
- Version: `1.3.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 13 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add joselhurtado-uxui-principles -- npx -y @uxuiprinciples/mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "joselhurtado-uxui-principles": {
      "command": "npx",
      "args": [
        "-y",
        "@uxuiprinciples/mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "joselhurtado-uxui-principles": {
      "command": "npx",
      "args": [
        "-y",
        "@uxuiprinciples/mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add joselhurtado-uxui-principles -- npx -y @uxuiprinciples/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "joselhurtado-uxui-principles": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@uxuiprinciples/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add joselhurtado-uxui-principles --command npx --arg -y --arg @uxuiprinciples/mcp-server
```

### Hermes

```yaml
mcp_servers:
  joselhurtado-uxui-principles:
    command: "npx"
    args: ["-y", "@uxuiprinciples/mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "joselhurtado-uxui-principles": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@uxuiprinciples/mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add joselhurtado-uxui-principles -t stdio -c npx -a -y @uxuiprinciples/mcp-server
```

### Other

```json
{
  "mcpServers": {
    "joselhurtado-uxui-principles": {
      "command": "npx",
      "args": [
        "-y",
        "@uxuiprinciples/mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 75, +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.

### 2026-11-18 (score 74, +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.

### 2026-11-15 (score 73, +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.

### 2026-11-13 (score 72, +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.

### 2026-11-11 (score 71, +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.

### 2026-11-09 (score 70, +1)

- [security regression] 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.
- [functional regression] Schema quality: 2293 → 2693
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.07
- [functional] First check of Schema quality: unverified
- [functional] Package version: 1.2.1 → 1.3.0

### 2026-11-08 (score 69, +10)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

### 2026-11-07 (score 59)

First indexed and scored.

## MCP tools (14)

### `get_principle` (~173 tokens)

Get a principle

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.

Input parameters:

- `locale` (string): Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".
- `slug` (string, required): The principle slug as returned by search_principles or list_principles (e.g., "cognitive-load", "hicks-law", "fitts-law").

### `search_principles` (~228 tokens)

Search principles

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.

Input parameters:

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

### `list_principles` (~152 tokens)

List principles

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.

Input parameters:

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

### `get_principle_prompts` (~142 tokens)

Get the AI prompts of a principle

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.

Input parameters:

- `locale` (string): Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".
- `slug` (string, required): The principle slug (e.g., "cognitive-load").

### `get_smell` (~148 tokens)

Get a UX smell

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.

Input parameters:

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

### `list_smells` (~144 tokens)

List UX smells

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.

Input parameters:

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

### `detect_smell` (~147 tokens)

Detect UX smells from a description

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.

Input parameters:

- `description` (string, required): What 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").
- `locale` (string): Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".

### `suggest_fix` (~162 tokens)

Suggest a fix for a UX issue

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.

Input parameters:

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

### `get_flow` (~158 tokens)

Get a user flow

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.

Input parameters:

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

### `list_flows` (~123 tokens)

List user flows

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.

Input parameters:

- `locale` (string): Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".

### `generate_checklist` (~189 tokens)

Generate a flow checklist

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.

Input parameters:

- `flow_id` (string, required): The flow id. One of: "onboarding", "forms", "pricing", "dashboard", "empty-states", "checkout", "settings", "navigation", "search", "authentication", "notifications", "data-tables". Call list_flows f…
- `locale` (string): Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".
- `phase` (string, required): Which checklist to generate: "preflight" (before design) or "postflight" (before ship).

### `get_flow_principles` (~149 tokens)

Get the principles behind a flow

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.

Input parameters:

- `flow_id` (string, required): The flow id. One of: "onboarding", "forms", "pricing", "dashboard", "empty-states", "checkout", "settings", "navigation", "search", "authentication", "notifications", "data-tables".
- `locale` (string): Language of the returned content: "en" (English) or "es" (Spanish). Defaults to "en".

### `audit_interface` (~205 tokens)

Audit an interface

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.

Input parameters:

- `context` (string): Where the interface lives. Echoed in the result; does not change the rules.
- `depth` (string): "quick": the top 5 findings. "full": every finding. Defaults to "full".
- `description` (string, required): What 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).
- `locale` (string): Language of the findings: "en" or "es". Defaults to "en".

### `check_requirements` (~346 tokens)

Check a screen against the required-state rules

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.

Input parameters:

- `actions` (array): The actions the screen offers, with their flags.
- `components` (array): 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…
- `flow` (string): The flow the screen belongs to. One of: "onboarding", "forms", "pricing", "dashboard", "empty-states", "checkout", "settings", "navigation", "search", "authentication", "notifications", "data-tables"…
- `locale` (string): Language of the verdicts and the summary: "en" or "es". Defaults to "en".
- `states_implemented` (array): The states the implementation has: loading, empty, error, success, confirmation, undo, edit, sources, recovery, consent. Only list what is built.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/joselhurtado-uxui-principles/uxuiprinciples-mcp-server#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 75
- 2026-11-19: 74
- 2026-11-18: 74
- 2026-11-17: 73
- 2026-11-16: 73
- 2026-11-15: 73
- 2026-11-14: 72
- 2026-11-13: 72
- 2026-11-12: 71
- 2026-11-11: 71
- 2026-11-10: 70
- 2026-11-09: 70
- 2026-11-08: 69
- 2026-11-07: 59

## 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.

## Links

- npm package: https://www.npmjs.com/package/@uxuiprinciples/mcp-server
- Socket report: https://socket.dev/npm/package/@uxuiprinciples/mcp-server
- Repository: https://github.com/uxuiprinciples/mcp-server
- Website: https://uxuiprinciples.com/en/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/joselhurtado-uxui-principles/uxuiprinciples-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/joselhurtado-uxui-principles/uxuiprinciples-mcp-server/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/joselhurtado-uxui-principles/uxuiprinciples-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/joselhurtado-uxui-principles/uxuiprinciples-mcp-server
