Skip to content

Layro MCP server

io.github.Layropro/layroLayroprostreamable-httpv1.3.0Scanned

React + Tailwind UI components and recipes your AI coding tool can search and install.

10 tools: 1 change things and 9 only read.

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

Tools listed without sign-in. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Layro MCP server can do

The Layro MCP server is published by the GitHub account Layropro. It has 10 tools. It can create or change data (1 tool: check_access), but cannot delete data. 9 tools only read.

4 tools read private data (get_component, get_component_code, get_installation and 1 more); 2 tools bring in text other people can write (get_installation and get_recipe).

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 10, 2026, version 1.3.0.

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.

10 tools

Changes things 1Claude Code: ask
  • check_accessWhether the caller can take a component or template, and why: free, subscriber, lifetime, purchased or unauthorized.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
    Whether the caller can take a component or template, and why: free, subscriber, lifetime, purchased or unauthorized.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 9Show 9 read-only tools
  • get_componentEverything about one component except its source: when to use it, props, variants, npm dependencies, the files it installs, a typechecked usage example with real props, how it size…Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    Description, as the server wrote it
    Everything about one component except its source: when to use it, props, variants, npm dependencies, the files it installs, a typechecked usage example with real props, how it sizes and scrolls (layout), the components it pairs with and the recipes it appears in.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_component_codeThe complete source for one component and every file it imports, ready to save at the paths given.Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    Description, as the server wrote it
    The complete source for one component and every file it imports, ready to save at the paths given. Free components need a free Liro account's token; Pro components need the caller's Liro lifetime access. Install with the shadcn CLI instead when you can run commands (see get_installation).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_installationInstallation for one or more components: the one-time @liro registry setup for components.json, the shadcn CLI command (always @liro/<slug>, never a bare URL), a ready-to-run agent…Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Installation for one or more components: the one-time @liro registry setup for components.json, the shadcn CLI command (always @liro/<slug>, never a bare URL), a ready-to-run agent command with a 15-minute install token when this connection carries a CLI token, the npm packages still missing (pass installed_packages from package.json), the files and where they go, and the theme setup.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_recipeComplete, runnable files that combine several Liro components the way they fit together: an AI chat app shell (Sidebar + Conversation History + AI Chat, with a phone drawer), a das…Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    • untrusted-inputThe description's first sentence says "chat": it reads messages, which other people can write.
    Description, as the server wrote it
    Complete, runnable files that combine several Liro components the way they fit together: an AI chat app shell (Sidebar + Conversation History + AI Chat, with a phone drawer), a dashboard app and a billing page. Without a slug, lists the recipes. Every recipe typechecks against the components.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_templateOne template's details and whether the caller may download it.No findings

    Why it is in this group

    • The name "get_template" says "get": a word for reading.
    Description, as the server wrote it
    One template's details and whether the caller may download it. Never returns the template's files.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_themeThe theme's colour tokens (light and dark values, and what each one colours), how to restyle Liro to a brand from your own CSS without editing components, the type scale, and the c…No findings

    Why it is in this group

    • The name "get_theme" says "get": a word for reading.
    Description, as the server wrote it
    The theme's colour tokens (light and dark values, and what each one colours), how to restyle Liro to a brand from your own CSS without editing components, the type scale, and the cn() config for it.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_categoriesThe categories in the Liro catalogue with the components in each, plus the library contract: stack, theme, access, install path, and the accessibility and responsive behaviour ever…No findings

    Why it is in this group

    • The name "list_categories" says "list": a word for reading.
    Description, as the server wrote it
    The categories in the Liro catalogue with the components in each, plus the library contract: stack, theme, access, install path, and the accessibility and responsive behaviour every component has.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_componentsFind Liro React + Tailwind components by what they do.No findings

    Why it is in this group

    • The name "search_components" says "search": a word for reading.
    Description, as the server wrote it
    Find Liro React + Tailwind components by what they do. Returns the best matches first with slug, category, access (free or pro) and version. Start here, then call get_component for details.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_templatesFind complete Liro React / Next.js templates: what each is, its stack, a live preview and how it is licensed.No findings

    Why it is in this group

    • The name "search_templates" says "search": a word for reading.
    Description, as the server wrote it
    Find complete Liro React / Next.js templates: what each is, its stack, a live preview and how it is licensed.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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 data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
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, 18:23 UTC, unchanged since Oct 29, 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
1
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 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://layropro.com/api/mcp: tools/list returned 10 tools to an anonymous client, including check_access (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. Tools10 changed.~10 changedView diff

Install

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

claude mcp add --transport http layro https://layropro.com/api/mcp
claude mcp add --transport http layro https://layropro.com/api/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__layro__search_components",
      "mcp__layro__get_component",
      "mcp__layro__get_component_code",
      "mcp__layro__get_installation",
      "mcp__layro__list_categories",
      "mcp__layro__search_templates",
      "mcp__layro__get_template",
      "mcp__layro__get_theme",
      "mcp__layro__get_recipe"
    ],
    "ask": [
      "mcp__layro__check_access"
    ],
    "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 layro. Review it before you use it.

Capability tags behind 4 rules
  • mcp__layro__get_component private-data
  • mcp__layro__get_component_code private-data
  • mcp__layro__get_installation private-data, untrusted-input
  • mcp__layro__get_recipe 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.Layropro/layro/verify?hash=b020d50542a676210dd22cbc0664d36927d8d86d309c8c79de3f55ec22d2be7c" | jq -e '.changed == false'

Pinned hash b020d50542a6, from Nov 10, 2026, 14: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.Layropro/layro/changes.xml

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

Badge

Anlyon Radar badge for io.github.Layropro/layro
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Layropro/layro.svg)](https://radar.anlyon.com/servers/io.github.Layropro/layro)

Source: MCP Registry. Synced Nov 9, 2026, 07:17 UTC.

Layro MCP server: questions and answers

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

Is the Layro MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 1 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 Layro MCP server delete data?

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

Can the Layro 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 Layro MCP server have?

10 tools: 1 write, 9 read. check_access, search_components, get_component, get_component_code, get_installation, list_categories, search_templates, get_template and 2 more.

Does the Layro MCP server need sign-in or OAuth?

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

Does the Layro MCP server send data to outside services?

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

Has the Layro MCP server changed its tools?

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