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.

Mlola UI

NPM · MLOLA-UI · 2 COMPONENTS

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

0 this week 95 Trust /100

Last scanned (22 hours ago)

Scores higher than 98% of npm servers

Category Developer Tools

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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to mlolahq/mlola-ui). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 13 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1110 tokens (~92/item across 12 items; 10 tools + 2 resources), lean.Pass
  • 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 Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 33% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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
  • Supports UI / widget rendering.Pass
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.

  • 27 Oct 26 0
    • Stability: 0.97 → pass security
  • 26 Oct 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.

  • 24 Oct 26 +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.

  • 22 Oct 26 +1
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.80 → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Package version: 1.14.2 → 1.14.3 functional
  • 20 Oct 26 +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.

  • 18 Oct 26 +12
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 17 Oct 26 +4
    • Known CVEs: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.63 → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: pass → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Package version: 1.14.0 → 1.14.2 functional
    • Package version: 1.14.0 → 1.14.1 functional
  • 16 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 1.13.2 → 1.14.0 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 4 Nov 2026 · Analysed npm/mlola-ui@1.14.3

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 mlolahq/mlola-ui
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/mlolahq/mlola-ui/.github/workflows/publish.yml@refs/tags/v1.14.3
Rekor log index 3370553841
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:b5a810c82e34b6fb23c79842763fee0e8e2fc64211f3bcb19ec4e282c76bb51255f5725a2ecba8c94a8f291dd9b77d318e5fb45f763cc72fec94cc94b

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~874 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
add_components ~61

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.

NameTypeReqDescription
namesarrayyes–
overwriteboolean––

No output schema declared.

No examples provided.

check_markup ~135

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.

NameTypeReqDescription
markupstringyes–

No output schema declared.

No examples provided.

check_render ~148

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.

NameTypeReqDescription
messages–yesThe A2UI messages: an array of message objects, one message, or their JSON text (JSON Lines works too).

No output schema declared.

No examples provided.

get_component ~80

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.

NameTypeReqDescription
include_sourceboolean––
namestringyes–

No output schema declared.

No examples provided.

get_design_rules ~44

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_render_catalog ~83

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.

NameTypeReqDescription
formatstring––

No output schema declared.

No examples provided.

get_tokens ~70

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.

NameTypeReqDescription
groupstring–For example 'spacing', 'color', 'shadow', 'radius'.

No output schema declared.

No examples provided.

init_project ~50

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

render_ui ~122

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.

NameTypeReqDescription
messages–yesThe A2UI messages of the surface: createSurface, updateComponents, updateDataModel.

No output schema declared.

No examples provided.

search_components ~81

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.

NameTypeReqDescription
kindstring––
querystring–Words describing what you need. Empty lists everything.
tierstring––

No output schema declared.

No examples provided.

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.

npm · mlola-ui

# add to Claude Code
claude mcp add mlolahq-mlola-ui -- npx -y mlola-ui
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 4 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 4 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.