_ registry / mcp streamable-http · checked 2h ago

flowpack

https://flowpack-mcp.flowpackplugin.workers.dev

Registry code: 74911e69645cf481

api record

Read-only Flowpack design knowledge for Shopify storefronts: browse the catalog, get recommendations and presets, diagnose setup issues. No store data is read or written.

endpoint
https://flowpack-mcp.flowpackplugin.workers.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is flowpack live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is flowpack free to use?
Yes — the hub reached it with no key and no payment.
What tools does flowpack have?
5 tools: plan, explain, diagnose, recommend, browse.
Is flowpack safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.5%· all time 99.5%

latency
109ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 398 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • recommend shopify storefront design presets
  • diagnose storefront theme setup issues
  • explain a storefront setting
  • browse design kits and palettes
takes → gives
text → data, text
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open 4 never probed 1 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • browse reads open 18h ago

    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'.

    mcp-tool

    {
      "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
        }
      }
    }
    arguments 38 lines
  • plan reads unknown never probed

    MASTER KEY tool. Analyzes natural-language merchant intent ('make my buttons feel premium', 'wellness brand vibe', 'BFCM aggressive') and returns a structured plan of settings to change across Flowpack's Button + Cart + Badge + Variant + Frosty Pill kits. Handles single tweaks (one hover style) and full overhauls (50+ settings) with the same call. Returns opaque plan_id, change count, preview URL, and reasoning. ALWAYS call preview() before execute().

    mcp-tool

    {
      "type": "object",
      "required": [
        "intent"
      ],
      "properties": {
        "intent": {
          "type": "string",
          "description": "Natural-language merchant intent"
        },
        "context": {
          "type": "object",
          "properties": {
            "theme": {
              "type": "string"
            },
            "market": {
              "type": "string"
            },
            "season": {
              "type": "string"
            },
            "products": {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            "brand_hint": {
              "type": "string"
            },
            "constraints": {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            "current_settings": {
              "type": "object"
            }
          }
        }
      }
    }
    arguments 44 lines
  • explain reads unknown never probed

    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'.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "detail": {
          "enum": [
            "brief",
            "deep"
          ],
          "type": "string"
        },
        "plan_id": {
          "type": "string"
        },
        "audience": {
          "enum": [
            "merchant",
            "developer",
            "reviewer"
          ],
          "type": "string"
        },
        "setting_path": {
          "type": "string"
        }
      }
    }
    arguments 26 lines
  • diagnose reads unknown never probed

    Runtime + theme + settings harmony check. Free-text symptom (e.g., 'cart drawer feels slow', 'badges not appearing') OR kit-scoped check. Returns categorized issues (theme_compat / settings_conflict / runtime_error / a11y / performance) with severity and optional fix_plan_id callable via execute(). health_score 0-100.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "kit": {
          "enum": [
            "button",
            "cart",
            "badge",
            "variant",
            "global"
          ],
          "type": "string"
        },
        "deep": {
          "type": "boolean",
          "description": "Run full theme compat sweep (slower)"
        },
        "symptom": {
          "type": "string"
        }
      }
    }
    arguments 22 lines
  • recommend reads unknown never probed

    Goal-oriented recommendation engine. Scenarios: 'personalized_4_plans' (returns 4 diverse plans — safe / aspirational / seasonal / conversion-tested), 'preset_for_brand', 'color_palette_for_theme', 'touch_target_for_devices', 'motion_density_for_audience', 'seasonal_for_calendar', 'diagnostics_first_check'. Use for proactive suggestions when merchant intent is unclear.

    mcp-tool

    {
      "type": "object",
      "required": [
        "scenario"
      ],
      "properties": {
        "context": {
          "type": "object"
        },
        "scenario": {
          "enum": [
            "preset_for_brand",
            "color_palette_for_theme",
            "touch_target_for_devices",
            "motion_density_for_audience",
            "seasonal_for_calendar",
            "diagnostics_first_check",
            "personalized_4_plans"
          ],
          "type": "string"
        }
      }
    }
    arguments 23 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 74911e69645cf481.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/74911e69645cf481/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/74911e69645cf481/badge.svg)](https://brick.blue/agent/74911e69645cf481?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.