mcp-registry/io.github.flowpackplugin/flowpack · v2.0.0
As of 2026-10-27 03:16 UTC, the Flowpackplugin Flowpack MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Flowpack: Shopify design catalog — badge/button/bar looks, honest-urgency presets, diagnosis.
Point your MCP client at this streamable-http endpoint: https://flowpack-mcp.flowpackplugin.workers.dev/mcp
14 parameter(s) across 5 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.flowpackplugin%2Fflowpack/fixes
{
"name": "browse",
"description": "Universal catalog reader. Routes by domain ('kits', 'presets', 'palettes', 'seasonal', 'settings', 'decorations', 'effects', 'diagnostics', 'anatomy', 'compatibility') with optional facet filter (e.g., 'button.hover') and free-text query. Returns paged items with id/name/description and metadata-only marker. Use this for ANY merchant question about 'what options are available' or 'show me X'.",
"inputSchema": {
"type": "object",
"required": [
"domain"
],
"properties": {
"page": {
"type": "integer",
"minimum": 1
},
"facet": {
"type": "string"
},
"query": {
"type": "string"
},
"domain": {
"enum": [
"kits",
"presets",
"palettes",
"seasonal",
"settings",
"decorations",
"effects",
"diagnostics",
"anatomy",
"compatibility"
],
"type": "string"
},
"page_size": {
"type": "integer",
"maximum": 50,
"minimum": 1
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "explain",
"description": "Natural-language explanation of a plan_id (what it does) or setting_path (what one setting controls). Audience: merchant (default), developer, or reviewer. Detail: brief (1-2 sentences) or deep (full context + related settings + a11y notes). Use when merchant asks 'what does this do' or 'why this preset'.",
"inputSchema": {
"type": "object",
"properties": {
"detail": {
"enum": [
"brief",
"deep"
],
"type": "string"
},
"plan_id": {
"type": "string"
},
"audience": {
"enum": [
"merchant",
"developer",
"reviewer"
],
"type": "string"
},
"setting_path": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.flowpackplugin/flowpack"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.flowpackplugin/flowpack"}) over MCP.
plan ~260 tokensbrowse ~221 tokensrecommend ~200 tokensdiagnose ~163 tokensexplain ~159 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.flowpackplugin%2Fflowpack?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.flowpackplugin%2Fflowpack?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.flowpackplugin%2Fflowpack.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.flowpackplugin%2Fflowpack.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.flowpackplugin%2Fflowpack?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c7e906d527340885…, first seen 2026-10-17, included at leaf 10713 of 77,037. Version history · verify what your client received.
Compare: most reliable other servers · most reliable devops servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 03:16 UTC, the Flowpackplugin Flowpack MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Flowpackplugin Flowpack MCP server advertises 5 tools, including browse, diagnose, explain, plan, recommend.
Point your MCP client at this streamable-http endpoint: https://flowpack-mcp.flowpackplugin.workers.dev/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.