Liquid Composer
io.github.frontedu/liquid-composerfrontedustreamable-httpv2.1.0Scanned
Check Liquid Glass app icon recipes and open them in the browser editor.
3 tools: 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 2Claude Code: ask
liquid_openTurn a recipe into a link that opens the icon in Liquid Composer.1 finding
Why it is in this group
- The name "liquid_open" says "open": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "liquid_open" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "liquid_open" says "open": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Open in Liquid Composer
- readOnlyHint: true
- openWorldHint: false
liquid_schemaJSON Schema of recipes and layer patches, and the guide.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it JSON Schema of recipes and layer patches, and the guide.
Annotations the server declares
- title: Recipe schema
- readOnlyHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
liquid_validateCheck a recipe without opening it; returns ok or the list of issues with their paths.No findings
Why it is in this group
- The name "liquid_validate" says "validate": a word for reading.
Description, as the server wrote it Check a recipe without opening it; returns ok or the list of issues with their paths.
Annotations the server declares
- title: Validate recipe
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
- Warnliquid_open
The server marks "liquid_open" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "liquid_open" says "open": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 2.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http liquid-composer https://liquid-composer.vercel.app/mcpclaude mcp add --transport http liquid-composer https://liquid-composer.vercel.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__liquid-composer__liquid_validate"
],
"ask": [
"mcp__liquid-composer__liquid_schema",
"mcp__liquid-composer__liquid_open"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as liquid-composer. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/io.github.frontedu/liquid-composer/verify?hash=8e273dbc664eda0967a95d6ed4d7627e4570c7daaa7fe43b478c65a98fc9b547" | jq -e '.changed == false'Pinned hash 8e273dbc664e, from Nov 2, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/io.github.frontedu/liquid-composer/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/io.github.frontedu/liquid-composer)Source: MCP Registry · repository. Synced Nov 2, 2026, 03:17 UTC.