Liquid Composer
REMOTE · LIQUID-COMPOSER.VERCEL.APP
Check Liquid Glass app icon recipes and open them in the browser editor.
Available components
Last scanned (21 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Design and Media
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 Usability49
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 657 tokens (~219/item across 3 items; 3 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 Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 3 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 66
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 4 Nov 2026 · Probed https://liquid-composer.vercel.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of liquid-composer.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | 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; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://liquid-composer.vercel.app/mcp | Verified | 200 | |
| http (plaintext) | http://liquid-composer.vercel.app/mcp | HTTPS enforced | 308 | https://liquid-composer.vercel.app/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 →
liquid_open Open in Liquid Composer ~62
Turn a recipe into a link that opens the icon in Liquid Composer. The link carries the recipe in its URL fragment, so opening it does not send the recipe to a server. Images must be inline SVG markup or data: URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| recipe | object | yes | – |
No output schema declared.
No examples provided.
liquid_schema Recipe schema ~20
JSON Schema of recipes and layer patches, and the guide.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
liquid_validate Validate recipe ~31
Check a recipe without opening it; returns ok or the list of issues with their paths.
| Name | Type | Req | Description |
|---|---|---|---|
| recipe | – | yes | – |
No output schema declared.
No examples provided.
How do I install the Liquid Composer MCP server?
Liquid Composer is a hosted endpoint at https://liquid-composer.vercel.app/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 · liquid-composer.vercel.app
claude mcp add --transport http frontedu-liquid-composer 'https://liquid-composer.vercel.app/mcp'
What is the Liquid Composer MCP server?
Liquid Composer is an MCP server listed in the public MCP registry as io.github.frontedu/liquid-composer. Check Liquid Glass app icon recipes and open them in the browser editor. This page covers its hosted endpoint (https://liquid-composer.vercel.app/mcp).
Is the Liquid Composer MCP server safe to use?
Liquid Composer scores 67 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 Liquid Composer MCP server expose?
Liquid Composer exposes 3 tools: liquid_schema, liquid_validate, liquid_open. Their descriptions and schemas cost roughly 113 tokens of context every time the server is loaded.
Does the Liquid Composer MCP server require authentication?
No. We connected to Liquid Composer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Liquid Composer MCP server still maintained?
Liquid Composer 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.