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.

Liro

REMOTE · LIRO.DEV

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

Available components

+3 this week 78 Trust /100

Last scanned (20 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 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 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1343 tokens (~134/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 Management40
  • Stability observed for 12 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

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

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

  • 12 Nov 26 +1

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

  • 10 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 72

    First indexed and scored.

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 21 Nov 2026 · Probed https://liro.dev/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=liro.dev CN=YR2,O=Let's Encrypt,C=US 9 Nov 2026 7 Feb 2027 RSA 2048 SHA256-RSA 675d578cc8976be87d77973e8f32da31d3e
SANs: liro.dev
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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 liro.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
liro.dev. No DS 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
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(self), geolocation=(), payment=(), usb=(), browsing-topics=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://liro.dev/api/mcp Verified 200
http (plaintext) http://liro.dev/api/mcp HTTPS enforced 308 https://liro.dev/api/mcp
MCP tools · 10 exposed · ~822 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_access ~43

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

NameTypeReqDescription
slugstringyesA component or template slug.

No output schema declared.

No examples provided.

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

NameTypeReqDescription
slugstringyesA component slug, like "data-table".

No output schema declared.

No examples provided.

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

NameTypeReqDescription
include_dependenciesboolean–Also return every file it imports (the theme, foundations, sibling components). Default true. Set false only if those are already in the project.
slugstringyesA component slug, like "data-table".

No output schema declared.

No examples provided.

get_installation ~184

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.

NameTypeReqDescription
installed_packagesarray–npm packages the project already has (from package.json), so they are not suggested again.
modestring–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_managerstring–Default npm.
slugsarrayyesOne or more component slugs.

No output schema declared.

No examples provided.

get_recipe ~90

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.

NameTypeReqDescription
slugstring–A recipe slug, like "ai-chat-app". Leave out to list the recipes.

No output schema declared.

No examples provided.

get_template ~42

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

NameTypeReqDescription
slugstringyesA template slug, like "avero".

No output schema declared.

No examples provided.

get_theme ~54

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_categories ~45

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_components ~105

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.

NameTypeReqDescription
categorystring–Only this category (name or slug from list_categories).
limitinteger–How many results. Default 8.
querystringyesWhat you need, in plain words: "animated dashboard card", "date range picker".

No output schema declared.

No examples provided.

search_templates ~60

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

NameTypeReqDescription
limitinteger––
querystring–What the template is for. Leave out to list all templates.

No output schema declared.

No examples provided.

Install

How do I install the Liro MCP server?

Liro is a hosted endpoint at https://liro.dev/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 · liro.dev

# add to Claude Code
claude mcp add --transport http dev-liro-liro 'https://liro.dev/api/mcp'
Common questions

What is the Liro MCP server?

Liro is an MCP server listed in the public MCP registry as dev.liro/liro. React + Tailwind UI components and recipes your AI coding tool can search and install. This page covers its hosted endpoint (https://liro.dev/api/mcp).

Is the Liro MCP server safe to use?

Liro scores 78 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 Liro MCP server expose?

Liro 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 Liro MCP server require authentication?

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

Is the Liro MCP server still maintained?

Liro is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Liro MCP server?

VerifyMCP ran 13 checks on Liro, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.