UI Registry
NPM · UI-REGISTRY-MCP · SCANNED SEP 24
Live access to 12 shadcn-style component libraries so agents compose UI from real components.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 72 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1292 tokens (~215/item across 6 items; 6 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 Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
How do I install the UI Registry MCP server?
UI Registry runs locally as an npm package, launched with npx -y ui-registry-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · ui-registry-mcp
claude mcp add mrityunjay-tiwari-ui-registry-mcp -- npx -y ui-registry-mcp
{
"mcpServers": {
"mrityunjay-tiwari-ui-registry-mcp": {
"command": "npx",
"args": [
"-y",
"ui-registry-mcp"
]
}
}
} {
"servers": {
"mrityunjay-tiwari-ui-registry-mcp": {
"command": "npx",
"args": [
"-y",
"ui-registry-mcp"
]
}
}
} codex mcp add mrityunjay-tiwari-ui-registry-mcp -- npx -y ui-registry-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mrityunjay-tiwari-ui-registry-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"ui-registry-mcp"
],
"enabled": true
}
}
} openclaw mcp add mrityunjay-tiwari-ui-registry-mcp --command npx --arg -y --arg ui-registry-mcp
mcp_servers:
mrityunjay-tiwari-ui-registry-mcp:
command: "npx"
args: ["-y", "ui-registry-mcp"] {
"McpServers": {
"mrityunjay-tiwari-ui-registry-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"ui-registry-mcp"
]
}
}
} assistant mcp add mrityunjay-tiwari-ui-registry-mcp -t stdio -c npx -a -y ui-registry-mcp
{
"mcpServers": {
"mrityunjay-tiwari-ui-registry-mcp": {
"command": "npx",
"args": [
"-y",
"ui-registry-mcp"
]
}
}
} 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.
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
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 24 Sept 2026 · Analysed npm/ui-registry-mcp@0.7.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_consistency Check design consistency across components ~95
Given a set of components (from get_component / search results), statically analyze their source for design clashes when mixed together: inconsistent border-radius scales, hardcoded colors vs theme tokens, missing dark-mode variants, and conflicting icon/animation libraries. Returns findings with concrete pointers so you can normalize the UI before shipping. Run this after assembling components from different libraries.
| Name | Type | Req | Description |
|---|---|---|---|
| components | array | yes | The components you plan to use together |
No output schema declared.
No examples provided.
compare_components Compare a component across libraries ~107
For a given intent (e.g. 'pricing table', 'date picker'), fetch the single best match from EACH library and return them side by side: dependencies, file count, lines of code, install command, and a source preview. Use this to choose the nicest implementation instead of taking the first search hit.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The component intent, e.g. 'pricing table' |
| registries | array | – | Optional subset of registry ids to compare (default: all) |
No output schema declared.
No examples provided.
get_component Get a component's real source ~123
Fetch the full, current source of one component from a specific library: file contents, npm dependencies, registry dependencies, and the exact install command. Use this after search_components. The returned source is real code you can drop into the project and edit freely. IMPORTANT: relay the returned 'attribution' line to the user so they know which library and source URL the component came from.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Component name exactly as returned by search_components |
| registry | string | yes | Registry id, e.g. 'reui' (see list_registries) |
No output schema declared.
No examples provided.
list_components List the full component directory ~175
Browse the complete directory of every component across all libraries, each with its DIRECT URL (the registry JSON / shadcn install URL). Paginated — thousands of entries. Filter by registry and/or type, and page with offset/limit. Use this to enumerate what exists or to fetch a component's canonical source URL for attribution. Note: the directory includes premium/gated components too — some URLs 401 on install; use search_components(verified:true) when you need installable-only results.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max entries per page (default 200) |
| offset | integer | – | Pagination offset (default 0) |
| registry | string | – | Optional registry id to restrict to one library |
| type | string | – | Optional type filter: 'ui' | 'block' | 'component' | 'hook' |
No output schema declared.
No examples provided.
list_registries List component registries ~71
List the component libraries this server can pull from (id, name, homepage, license, and any notes such as premium/gated warnings). Call this first to see what is available. When a registry's notes mention premium/gated components, use verified:true in search_components to get only installable ones.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_components Search components across libraries ~249
Search all configured component libraries (or one) for components matching a natural-language query, e.g. 'pricing table', 'date picker', 'sidebar'. Synonym-aware: 'modal' also finds 'dialog', 'dropdown' finds 'select', etc. Returns a ranked, lightweight list (registry, name, type, title, description) — NOT the source. Pick the best match, then call get_component to fetch its real code. Set verified:true to return only components confirmed installable (filters out premium/gated ones that would 401).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 20) |
| query | string | yes | What you need, e.g. 'pricing table' or 'avatar group' |
| registry | string | – | Optional registry id to restrict the search (see list_registries) |
| type | string | – | Optional type filter: 'ui' (single component), 'block' (composed section), 'component', 'hook' |
| verified | boolean | – | When true, fetch-check results and return only components that are actually installable (drops premium/gated items that would 401). Slower; use when you want guaranteed-installable results. |
No output schema declared.
No examples provided.
What is the UI Registry MCP server?
UI Registry is an MCP server listed in the public MCP registry as io.github.mrityunjay-tiwari/ui-registry-mcp. Live access to 12 shadcn-style component libraries so agents compose UI from real components. This page covers its npm package (ui-registry-mcp).
Is the UI Registry MCP server safe to use?
UI Registry scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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 UI Registry MCP server expose?
UI Registry exposes 6 tools: list_registries, search_components, get_component, compare_components, check_consistency, list_components. Their descriptions and schemas cost roughly 820 tokens of context every time the server is loaded.
Is the UI Registry MCP server still maintained?
UI Registry is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the UI Registry MCP server under?
UI Registry declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.