UI Registry
NPM · UI-REGISTRY-MCP · SCANNED AUG 3
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · ui-registry-mcp
claude mcp add mrityunjay-tiwari-ui-registry-mcp -- npx -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": {
"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.
- 3 Aug 26 +25
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Schema quality: unverified → excellent ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: MIT functional
- 2 Aug 26 +20
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- 1 Aug 26 +13
- Tool coverage: unverified → 100 ▲ functional
- 31 Jul 26 −20
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 43
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.