Layro
REMOTE · LAYROPRO.COM
React + Tailwind UI components and recipes your AI coding tool can search and install.
Available components
Last scanned (2 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% 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 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
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.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 31 Oct 26 +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.
- 30 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 73
First indexed and scored.
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://layropro.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=layropro.com | CN=YR1,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | RSA 2048 | SHA256-RSA | 503462816191408c9c179c4908b60f5b75a |
| SANs: layropro.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of layropro.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| layropro.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://layropro.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://layropro.com/api/mcp | HTTPS enforced | 308 | https://layropro.com/api/mcp |
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 →
check_access Check Layro access ~43
Whether the caller can take a component or template, and why: free, subscriber, lifetime, purchased or unauthorized.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | A component or template slug. |
No output schema declared.
No examples provided.
get_component Get a Layro component ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | A component slug, like "data-table". |
No output schema declared.
No examples provided.
get_component_code Get a Layro component's code ~121
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | A component slug, like "data-table". |
No output schema declared.
No examples provided.
get_installation Install Layro components ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | One or more component slugs. |
No output schema declared.
No examples provided.
get_recipe Get a Layro recipe ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | A recipe slug, like "ai-chat-app". Leave out to list the recipes. |
No output schema declared.
No examples provided.
get_template Get a Layro template ~42
One template's details and whether the caller may download it. Never returns the template's files.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | A template slug, like "settle". |
No output schema declared.
No examples provided.
get_theme Get the Layro theme ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_categories List Layro categories ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_components Search Layro components ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only this category (name or slug from list_categories). |
| limit | integer | – | How many results. Default 8. |
| query | string | yes | What you need, in plain words: "animated dashboard card", "date range picker". |
No output schema declared.
No examples provided.
search_templates Search Layro templates ~60
Find complete Layro React / Next.js templates: what each is, its stack, a live preview and how it is licensed.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | – | What the template is for. Leave out to list all templates. |
No output schema declared.
No examples provided.
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.
remote · layropro.com
claude mcp add --transport http layropro-layro 'https://layropro.com/api/mcp'
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.