Skip to content

Mlola UI MCP server

io.github.mlolahq/mlola-uimlolahqstreamable-httpv1.15.2Scanned

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

9 tools: 2 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 2 write, 7 read.
  • Reads private data · 3
  • Reads text others write · 4
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Mlola UI MCP server can do

The Mlola UI MCP server is published by the GitHub account mlolahq. It has 9 tools. It can create or change data (2 tools: check_markup and check_render), but cannot delete data. 7 tools only read.

3 tools read private data (search_components, get_render_catalog and render_ui); 4 tools bring in text other people can write (get_design_rules, search_components, get_render_catalog and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 1.15.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 2Claude Code: ask
  • check_markupChecks HTML or JSX: classes and --ml-* tokens that do not exist (with the closest that do), variant classes, data-* values and React props a component does not take, a control's cl…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Checks HTML or JSX: classes and --ml-* tokens that do not exist (with the closest that do), variant classes, data-* values and React props a component does not take, a control's class on an element that cannot be operated (ml-button on a div), buttons, links, fields and images with no name, utility classes, misuse of data-theme or data-mode, and in style attributes, <style> blocks and utility classes (bg-[#fafafa]) what is typed by hand instead of read from a token: colors, spacing, type sizes, radii, shadows, durations, layers, overridden theme tokens and text faded with opacity. Each issue names its line and the fix. 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.

    Annotations the server declares

    • readOnlyHint: true
  • check_renderChecks A2UI messages (createSurface, updateComponents, updateDataModel, deleteSurface) against the Mlola Render catalog before they render: components and props that do not exist, …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
Only reads 7Show 7 read-only tools
  • get_componentEverything 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, de…No findings

    Why it is in this group

    • The name "get_component" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • get_design_rulesThe rules for building UI with Mlola: compose first, color by role, measure with the scales, shared state words, touch and focus; the project setup (the theme on <html>, every them…Reads text others writeNo findings

    Why it is in this group

    • The name "get_design_rules" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "html": it reads web pages, which anyone can write.
    Description, as the server wrote it
    The rules for building UI with Mlola: compose first, color by role, measure with the scales, shared state words, touch and focus; the project setup (the theme on <html>, every theme's fonts); and what each layout primitive does. Read once before writing UI.

    Annotations the server declares

    • readOnlyHint: true
  • get_install_commandHow 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 …No findings

    Why it is in this group

    • The name "get_install_command" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • get_render_catalogThe 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…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_render_catalog" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • get_tokensThe --ml-* tokens grouped by purpose (planes and ink, color roles, spacing, type, density, shape, depth, motion, layers…).No findings

    Why it is in this group

    • The name "get_tokens" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • render_uiShows an interface in the conversation: a form, a status card, a table of results.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "show": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "show" and "conversation": it reads messages.
    • untrusted-inputThe description's first sentence says "show" and "conversation": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • search_componentsFind components, blocks, pages and templates by what they do (for example 'date range', 'chat input', 'pricing').Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "search_components" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "find" and "chat": it reads messages.
    • untrusted-inputThe description's first sentence says "find" and "chat": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:08 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://ui.mlola.com/mcp: tools/list returned 9 tools to an anonymous client, including check_markup (write), check_render (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.15.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http mlola-ui https://ui.mlola.com/mcp
claude mcp add --transport http mlola-ui https://ui.mlola.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__mlola-ui__get_design_rules",
      "mcp__mlola-ui__search_components",
      "mcp__mlola-ui__get_component",
      "mcp__mlola-ui__get_tokens",
      "mcp__mlola-ui__get_render_catalog",
      "mcp__mlola-ui__render_ui",
      "mcp__mlola-ui__get_install_command"
    ],
    "ask": [
      "mcp__mlola-ui__check_markup",
      "mcp__mlola-ui__check_render"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as mlola-ui. Review it before you use it.

Capability tags behind 4 rules
  • mcp__mlola-ui__get_design_rules untrusted-input
  • mcp__mlola-ui__search_components private-data, untrusted-input
  • mcp__mlola-ui__get_render_catalog private-data, untrusted-input
  • mcp__mlola-ui__render_ui private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.mlolahq/mlola-ui/verify?hash=901de2b192822f2e61f41ce68234624bd7a834eb7d11b4d9c0f46ed38854f4b5" | jq -e '.changed == false'

Pinned hash 901de2b19282, from Nov 11, 2026, 08:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.mlolahq/mlola-ui/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.mlolahq/mlola-ui
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.mlolahq/mlola-ui.svg)](https://radar.anlyon.com/servers/io.github.mlolahq/mlola-ui)

Source: MCP Registry · repository. Synced Nov 11, 2026, 08:18 UTC.

Mlola UI MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Mlola UI MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Mlola UI MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Mlola UI MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Mlola UI MCP server have?

9 tools: 2 write, 7 read. check_markup, check_render, get_design_rules, search_components, get_component, get_tokens, get_render_catalog, render_ui and 1 more.

Does the Mlola UI MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Mlola UI MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Mlola UI MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.