# Layro (remote · layropro.com)

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

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `layropro.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/layropro-layro/api-mcp.md), [page](https://verifymcp.io/servers/layropro-layro/api-mcp)

## Channel facts

- Endpoint: `https://layropro.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

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. 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.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1290 tokens (~129/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% 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 11 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.

## Install

### How do I install the Layro MCP server?

Layro is a hosted endpoint at https://layropro.com/api/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.

### Claude

```bash
claude mcp add --transport http layropro-layro 'https://layropro.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "layropro-layro": {
      "url": "https://layropro.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "layropro-layro": {
      "type": "http",
      "url": "https://layropro.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.layropro-layro]
url = "https://layropro.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "layropro-layro": {
      "type": "remote",
      "url": "https://layropro.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add layropro-layro --url 'https://layropro.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  layropro-layro:
    url: "https://layropro.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "layropro-layro": {
      "Transport": "http",
      "Url": "https://layropro.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add layropro-layro -t streamable-http -u 'https://layropro.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "layropro-layro": {
      "type": "http",
      "url": "https://layropro.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-05 (score 76, +1)

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

### 2026-11-03 (score 75, +1)

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

### 2026-10-31 (score 74, +1)

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

### 2026-10-30 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 73)

First indexed and scored.

## MCP tools (10)

### `search_components` (~105 tokens)

Search Layro components

Find Layro 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.

Input parameters:

- `category` (string): Only this category (name or slug from list_categories).
- `limit` (integer): How many results. Default 8.
- `query` (string, required): What you need, in plain words: "animated dashboard card", "date range picker".

### `get_component` (~78 tokens)

Get a Layro component

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.

Input parameters:

- `slug` (string, required): A component slug, like "data-table".

### `get_component_code` (~121 tokens)

Get a Layro component's code

The complete source for one component and every file it imports, ready to save at the paths given. Free components need a free Layro account's token; Pro components need the caller's Layro lifetime access. Install with the shadcn CLI instead when you can run commands (see get_installation).

Input parameters:

- `include_dependencies` (boolean): Also return every file it imports (the theme, foundations, sibling components). Default true. Set false only if those are already in the project.
- `slug` (string, required): A component slug, like "data-table".

### `get_installation` (~184 tokens)

Install Layro components

Installation for one or more components: the one-time @layro registry setup for components.json, the shadcn CLI command (always @layro/<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.

Input parameters:

- `installed_packages` (array): npm packages the project already has (from package.json), so they are not suggested again.
- `mode` (string): Default "cli": the shadcn CLI install, packages and files. "manual" or "both" adds copy-by-hand steps, for when you cannot run the CLI.
- `package_manager` (string): Default npm.
- `slugs` (array, required): One or more component slugs.

### `list_categories` (~45 tokens)

List Layro categories

The categories in the Layro catalogue with the components in each, plus the library contract: stack, theme, access, install path, and the accessibility and responsive behaviour every component has.

### `search_templates` (~60 tokens)

Search Layro templates

Find complete Layro React / Next.js templates: what each is, its stack, a live preview and how it is licensed.

Input parameters:

- `limit` (integer)
- `query` (string): What the template is for. Leave out to list all templates.

### `get_template` (~42 tokens)

Get a Layro template

One template's details and whether the caller may download it. Never returns the template's files.

Input parameters:

- `slug` (string, required): A template slug, like "settle".

### `check_access` (~43 tokens)

Check Layro access

Whether the caller can take a component or template, and why: free, subscriber, lifetime, purchased or unauthorized.

Input parameters:

- `slug` (string, required): A component or template slug.

### `get_theme` (~54 tokens)

Get the Layro theme

The theme's colour tokens (light and dark values, and what each one colours), how to restyle Layro to a brand from your own CSS without editing components, the type scale, and the cn() config for it.

### `get_recipe` (~90 tokens)

Get a Layro recipe

Complete, runnable files that combine several Layro 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.

Input parameters:

- `slug` (string): A recipe slug, like "ai-chat-app". Leave out to list the recipes.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/layropro-layro/api-mcp#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73

## Common questions

### What is the Layro MCP server?

Layro is an MCP server listed in the public MCP registry as io.github.Layropro/layro. React + Tailwind UI components and recipes your AI coding tool can search and install. This page covers its hosted endpoint (https://layropro.com/api/mcp).

### Is the Layro MCP server safe to use?

Layro scores 76 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 Layro MCP server expose?

Layro exposes 10 tools: search_components, get_component, get_component_code, get_installation, list_categories, and 5 more. Their descriptions and schemas cost roughly 822 tokens of context every time the server is loaded.

### Does the Layro MCP server require authentication?

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

### Is the Layro MCP server still maintained?

Layro 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.

## Links

- Remote endpoint: https://layropro.com/api/mcp
- Website: https://layropro.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/layropro-layro/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/layropro-layro/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/layropro-layro/api-mcp