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

REMOTE · UI.MLOLA.COM · 2 COMPONENTS

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

0 this week 85 Trust /100

Last scanned (5 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability84
  • 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 1134 tokens (~103/item across 11 items; 9 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 Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 45% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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
    • Server version: 1.14.2 → 1.14.3 functional
  • 19 Oct 26 +1

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

  • 17 Oct 26 +1
    • Server version: 1.14.1 → 1.14.2 functional
    • Server version: 1.14.0 → 1.14.1 functional
  • 16 Oct 26 0
    • Server version: 1.13.2 → 1.14.0 functional
  • 15 Oct 26 +1

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

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 5 Nov 2026 · Probed https://ui.mlola.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ui.mlola.com CN=YE1,O=Let's Encrypt,C=US 25 Sept 2026 24 Dec 2026 ECDSA 256 ECDSA-SHA384 6466eb4776c1c9c805785e64e814330abf1
SANs: ui.mlola.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ui.mlola.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
mlola.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ui.mlola.com/mcp Verified 200
http (plaintext) http://ui.mlola.com/mcp HTTPS enforced 301 https://ui.mlola.com/mcp
MCP tools · 9 exposed · ~850 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
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_install_command ~87

How to set Mlola up: the commands to run in a project to add components, blocks, pages or templates (with the license step for Mlola Pro items), and the stylesheet link and script for a page with no build step. Leave names out for the setup alone.

NameTypeReqDescription
namesarray–Item names from search_components, for example ["button", "date-picker"].

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.

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 is a hosted endpoint at https://ui.mlola.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · ui.mlola.com

# add to Claude Code
claude mcp add --transport http mlolahq-mlola-ui 'https://ui.mlola.com/mcp'
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 hosted endpoint (https://ui.mlola.com/mcp).

Is the Mlola UI MCP server safe to use?

Mlola UI scores 85 out of 100 on VerifyMCP. 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 9 tools: get_design_rules, search_components, get_component, get_tokens, check_markup, and 4 more. Their descriptions and schemas cost roughly 850 tokens of context every time the server is loaded.

Does the Mlola UI MCP server require authentication?

No. We connected to Mlola UI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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.