# Mlola UI (npm · mlola-ui)

Mlola UI components, tokens and design rules for coding agents, with a markup checker

- Trust score: 95/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `ui.mlola.com`: 85/100, [markdown](https://verifymcp.io/servers/mlolahq-mlola-ui/ui.md), [page](https://verifymcp.io/servers/mlolahq-mlola-ui/ui)
- npm · `mlola-ui`: 95/100 (this document), [markdown](https://verifymcp.io/servers/mlolahq-mlola-ui/mlola-ui.md), [page](https://verifymcp.io/servers/mlolahq-mlola-ui/mlola-ui)

## Channel facts

- Registry: `npm`
- Package: `mlola-ui`
- Version: `1.14.3`
- 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-05.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to mlolahq/mlola-ui).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 14 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1110 tokens (~92/item across 12 items; 10 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 33% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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.
  - Supports UI / widget rendering.

## Install

### How do I install the Mlola UI MCP server?

Mlola UI runs locally as an npm package, launched with npx -y mlola-ui. 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 mlolahq-mlola-ui -- npx -y mlola-ui
```

### Cursor

```json
{
  "mcpServers": {
    "mlolahq-mlola-ui": {
      "command": "npx",
      "args": [
        "-y",
        "mlola-ui"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mlolahq-mlola-ui": {
      "command": "npx",
      "args": [
        "-y",
        "mlola-ui"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mlolahq-mlola-ui -- npx -y mlola-ui
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mlolahq-mlola-ui": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mlola-ui"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mlolahq-mlola-ui --command npx --arg -y --arg mlola-ui
```

### Hermes

```yaml
mcp_servers:
  mlolahq-mlola-ui:
    command: "npx"
    args: ["-y", "mlola-ui"]
```

### Netclaw

```json
{
  "McpServers": {
    "mlolahq-mlola-ui": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mlola-ui"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mlolahq-mlola-ui -t stdio -c npx -a -y mlola-ui
```

### Other

```json
{
  "mcpServers": {
    "mlolahq-mlola-ui": {
      "command": "npx",
      "args": [
        "-y",
        "mlola-ui"
      ]
    }
  }
}
```

## 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-10-27 (score 95, 0)

- [security] Stability: 0.97 → pass

### 2026-10-26 (score 95, +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.

### 2026-10-24 (score 94, +1)

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

### 2026-10-22 (score 93, +1)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.80 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] Package version: 1.14.2 → 1.14.3

### 2026-10-20 (score 92, +1)

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

### 2026-10-18 (score 91, +12)

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

### 2026-10-17 (score 79, +4)

- [security regression] Known CVEs: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.63 → unverified
- [security improvement] Malware scan: unverified → pass
- [functional regression] Dependency health: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional] Package version: 1.14.0 → 1.14.2
- [functional] Package version: 1.14.0 → 1.14.1

### 2026-10-16 (score 75, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 1.13.2 → 1.14.0

## MCP tools (10)

### `get_design_rules` (~44 tokens)

Mlola design rules

The rules for building UI with Mlola: compose first, color by role, measure with the scales, shared state words, touch and focus. Read once before writing UI.

### `search_components` (~81 tokens)

Search Mlola components

Find components, blocks, pages and templates by what they do (for example 'date range', 'chat input', 'pricing'). Returns name, tier (free or Mlola Pro) and a one-line description.

Input parameters:

- `kind` (string)
- `query` (string): Words describing what you need. Empty lists everything.
- `tier` (string)

### `get_component` (~80 tokens)

How to use a Mlola component

Everything needed to use one item: import, every prop with fixed values (variant, tone, size, side…) and its default, the classes it styles and the data-* values each reacts to, dependencies and the install command. Set include_source to read a free component's source.

Input parameters:

- `include_source` (boolean)
- `name` (string, required)

### `get_tokens` (~70 tokens)

Mlola design tokens

The --ml-* tokens grouped by purpose (planes and ink, color roles, spacing, type, density, shape, depth, motion, layers…). Filter with a group name or part of a token name.

Input parameters:

- `group` (string): For example 'spacing', 'color', 'shadow', 'radius'.

### `check_markup` (~135 tokens)

Check markup against the Mlola contract

Checks HTML or JSX: classes that do not exist, variant classes, data-* values a class does not react to, utility classes, misuse of data-theme or data-mode, and in style attributes, <style> blocks and utility classes (bg-[#fafafa]) hand-written colors, spacing written by hand instead of the --ml-space-* scale, overridden theme tokens and text faded with opacity. Each issue names its line. Run it on markup you wrote before finishing: pass the whole page or file, <style> blocks included, not an excerpt, since it only checks what it is given.

Input parameters:

- `markup` (string, required)

### `get_render_catalog` (~83 tokens)

Mlola Render catalog

The components an agent may compose at runtime with Mlola Render, as A2UI v0.9 messages: each component's props and allowed values, how surfaces, data binding and actions work, and complete examples. Read once before composing a surface. format "schema" returns the A2UI catalog (JSON Schema) instead.

Input parameters:

- `format` (string)

### `check_render` (~148 tokens)

Check Mlola Render messages

Checks A2UI messages (createSurface, updateComponents, updateDataModel, deleteSurface) against the Mlola Render catalog before they render: components and props that do not exist, values a component does not offer, colors or styles set by hand, fields and controls without a name, a missing root, children that do not exist or form a loop, headings that skip a level, values outside a range. Each error names its JSON Pointer path and the fix. Pass every message of the surface: one object, an array, or JSON Lines.

Input parameters:

- `messages` (required): The A2UI messages: an array of message objects, one message, or their JSON text (JSON Lines works too).

### `render_ui` (~122 tokens)

Show Mlola Render UI

Shows an interface in the conversation: a form, a status card, a table of results. Pass A2UI messages composed from the Mlola Render catalog (read get_render_catalog first); they are checked, and drawn with Mlola components where the host shows MCP Apps. When the person presses a button, their next message carries the A2UI action with what they entered. Where the host shows no apps, this answers with the check's report.

Input parameters:

- `messages` (required): The A2UI messages of the surface: createSurface, updateComponents, updateDataModel.

### `add_components` (~61 tokens)

Install Mlola components

Copies components into the project with the Mlola CLI (npx mlola-ui add), with their dependencies and styles, and installs the npm packages they import. Pro items need a login first.

Input parameters:

- `names` (array, required)
- `overwrite` (boolean)

### `init_project` (~50 tokens)

Set a project up for Mlola

Runs npx mlola-ui init: writes mlola.config.json, the stylesheet entry and the agent instructions (AGENTS.md, the design guide, MCP config), and installs @mlola-ui/engine.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mlolahq-mlola-ui/mlola-ui#diagnostics

## Score history

- 2026-11-05: 95
- 2026-11-04: 95
- 2026-11-03: 95
- 2026-11-02: 95
- 2026-11-01: 95
- 2026-10-31: 95
- 2026-10-30: 95
- 2026-10-29: 95
- 2026-10-28: 95
- 2026-10-27: 95
- 2026-10-26: 95
- 2026-10-25: 94
- 2026-10-24: 94
- 2026-10-23: 93
- 2026-10-22: 93
- 2026-10-21: 92
- 2026-10-20: 92
- 2026-10-19: 91
- 2026-10-18: 91
- 2026-10-17: 79
- 2026-10-16: 75
- 2026-10-15: 90
- 2026-10-14: 89
- 2026-10-13: 39
- 2026-10-12: 50
- 2026-10-11: 49
- 2026-10-04: 85
- 2026-10-03: 69
- 2026-10-02: 69
- 2026-10-01: 68

## Common questions

### What is the Mlola UI MCP server?

Mlola UI is an MCP server listed in the public MCP registry as io.github.mlolahq/mlola-ui. Mlola UI components, tokens and design rules for coding agents, with a markup checker. This page covers its npm package (mlola-ui).

### Is the Mlola UI MCP server safe to use?

Mlola UI scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Mlola UI MCP server expose?

Mlola UI exposes 10 tools: get_design_rules, search_components, get_component, get_tokens, check_markup, and 5 more. Their descriptions and schemas cost roughly 874 tokens of context every time the server is loaded.

### Is the Mlola UI MCP server still maintained?

Mlola UI is still listed as active in the MCP registry. We last reached this channel on 5 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 Mlola UI MCP server under?

Mlola UI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/mlola-ui
- Socket report: https://socket.dev/npm/package/mlola-ui
- Repository: https://github.com/mlolahq/mlola-ui
- Website: https://ui.mlola.com/docs/agents
- Changelog RSS feed: https://verifymcp.io/servers/mlolahq-mlola-ui/mlola-ui.xml
- Changelog JSON feed: https://verifymcp.io/servers/mlolahq-mlola-ui/mlola-ui.json
- HTML version of this page: https://verifymcp.io/servers/mlolahq-mlola-ui/mlola-ui
