liquefy-ui
NPM · @LIQUEFY-UI/MCP
Answers questions about liquefy-ui from its real API surface, so an agent stops inventing props.
Available components
Last scanned (21 hours ago)
Scores higher than 99% of npm servers
Category Developer Tools
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to liquefy-ui/liquefy-ui). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 521 tokens (~65/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 30 Oct 26 0
- Package version: 0.1.4 → 0.1.5 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.97 functional
- 19 Oct 26 +1
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed npm/@liquefy-ui/mcp@0.1.5
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | liquefy-ui/liquefy-ui |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/liquefy-ui/liquefy-ui/.github/workflows/release.yml@refs/heads/rc |
| Rekor log index | 3583236217 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d900f8ab4093e64e4a325d02ec0e49e762cb1c856c0bd7f017d440d6a51f5d4d9bd0db9bfd877617edf780ff3b622cc44d26f1ebf3b03084c76a5ee30 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
get_component ~70
Get the real API of one component: its exported names, every exported type declaration verbatim, the import line, and the docs and registry URLs. Use this instead of guessing prop names.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | An export name like "LiquidButton" or a file slug like "liquid-button". |
No output schema declared.
No examples provided.
get_component_source ~67
Get the copy-paste source of a component, with imports already rewritten to shadcn aliases (@/components/ui, @/lib, @/hooks). Use this when the user wants to own and edit the code.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | An export name or file slug. |
No output schema declared.
No examples provided.
get_conventions ~49
The conventions of this library that are easy to get wrong: the client boundary, the required provider, the styles prop, which props do not exist. Read this before writing liquefy-ui code.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_core_api ~62
The public API of @liquefy-ui/core, the dependency-free engine under the components: the WebGL renderer, the bezel lens, the spring integrator and the tokens. Use it to drive the physics on an element the React components do not cover.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_tokens ~47
List the --lq-* design tokens and their real values, per theme scope.
| Name | Type | Req | Description |
|---|---|---|---|
| theme | string | – | Which scope to read: global defaults, or the dark or light theme block. |
No output schema declared.
No examples provided.
list_components ~60
List every component, hook and internal module in liquefy-ui with a one-line description. Start here when you do not know what the library contains.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Narrow to components ("ui"), hooks, or shared internals ("lib"). |
No output schema declared.
No examples provided.
list_icons ~65
List the icons in @liquefy-ui/icons by name, with their props. Use it before reaching for another icon library, and to check a name exists rather than guessing it.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional filter, e.g. "arrow" or "check". |
No output schema declared.
No examples provided.
search_components ~65
Free-text search across component names, descriptions and type declarations. Use it to answer "is there a component for X" or "which component has prop Y".
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Words to look for, e.g. "toast", "onValueChange", "glass". |
No output schema declared.
No examples provided.
How do I install the liquefy-ui MCP server?
liquefy-ui runs locally as an npm package, launched with npx -y @liquefy-ui/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 · @liquefy-ui/mcp
claude mcp add liquefy-ui-liquefy-ui -- npx -y @liquefy-ui/mcp
What is the liquefy-ui MCP server?
liquefy-ui is an MCP server listed in the public MCP registry as io.github.liquefy-ui/liquefy-ui. Answers questions about liquefy-ui from its real API surface, so an agent stops inventing props. This page covers its npm package (@liquefy-ui/mcp).
Is the liquefy-ui MCP server safe to use?
liquefy-ui scores 97 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 liquefy-ui MCP server expose?
liquefy-ui exposes 8 tools: list_components, get_component, search_components, get_component_source, get_tokens, and 3 more. Their descriptions and schemas cost roughly 485 tokens of context every time the server is loaded.
Is the liquefy-ui MCP server still maintained?
liquefy-ui is still listed as active in the MCP registry. We last reached this channel on 4 November 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 liquefy-ui MCP server under?
liquefy-ui declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.