# Moltline Shopify Prep (remote · mcp.moltlinestudio.com)

Check a product CSV, handles, variant matrices and metafield keys. 4 of 6 free.

- Trust score: 87/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.moltlinestudio.com`: 87/100 (this document), [markdown](https://verifymcp.io/servers/com-moltlinestudio-shopify/shopify.md), [page](https://verifymcp.io/servers/com-moltlinestudio-shopify/shopify)

## Channel facts

- Endpoint: `https://mcp.moltlinestudio.com/shopify`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1935 tokens (~322/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Moltline Shopify Prep MCP server?

Moltline Shopify Prep is a hosted endpoint at https://mcp.moltlinestudio.com/shopify, 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.

### Claude

```bash
claude mcp add --transport http com-moltlinestudio-shopify 'https://mcp.moltlinestudio.com/shopify'
```

### Cursor

```json
{
  "mcpServers": {
    "com-moltlinestudio-shopify": {
      "url": "https://mcp.moltlinestudio.com/shopify"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-moltlinestudio-shopify": {
      "type": "http",
      "url": "https://mcp.moltlinestudio.com/shopify"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-moltlinestudio-shopify]
url = "https://mcp.moltlinestudio.com/shopify"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-moltlinestudio-shopify": {
      "type": "remote",
      "url": "https://mcp.moltlinestudio.com/shopify",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-moltlinestudio-shopify --url 'https://mcp.moltlinestudio.com/shopify' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-moltlinestudio-shopify:
    url: "https://mcp.moltlinestudio.com/shopify"
```

### Netclaw

```json
{
  "McpServers": {
    "com-moltlinestudio-shopify": {
      "Transport": "http",
      "Url": "https://mcp.moltlinestudio.com/shopify"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-moltlinestudio-shopify -t streamable-http -u 'https://mcp.moltlinestudio.com/shopify'
```

### Other

```json
{
  "mcpServers": {
    "com-moltlinestudio-shopify": {
      "type": "http",
      "url": "https://mcp.moltlinestudio.com/shopify"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 87, +1)

- [security] Stability: 0.97 → pass

### 2026-09-17 (score 86, +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.

### 2026-09-15 (score 85, +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.

### 2026-09-13 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `product_csv_check` (~311 tokens)

Product Csv Check

Check a product CSV's header row against Shopify's current columns. FREE.

Catches the failure that wastes the most time: a template copied from an
out-of-date guide, using column names Shopify renamed. Typical input
{"header_row": ["Handle", "Title", "Body (HTML)", "Variant Price"]}
returns {"ok": false, "missing_required": [], "renamed": [{"found":
"Handle", "use": "URL handle"}, ...], "unrecognised": [], "verdict": "..."}.

Use before an import, on the header row alone. Not for whether the values
in the rows are valid — check a handle with url_handle and a metafield key
with metafield_key_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "header_row must contain at least one column name"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `header_row` (array, required): The CSV's first row as a list of column names, exactly as written in the file, e.g. ["Handle", "Title", "Variant Price"].
- `mode` (string): "new" when creating products, where Shopify requires only Title; "update" when changing existing ones, where it also requires URL handle. Default "new".

### `url_handle` (~254 tokens)

Url Handle

Turn a product title into a valid, unique Shopify URL handle. FREE.

Shopify handles are lowercase, may contain letters, numbers and dashes,
and may not contain spaces. Typical input {"title": "Men's  Merino Wool
Socks (2-Pack)"} returns {"handle": "mens-merino-wool-socks-2-pack",
"valid": true, "changed": true, "collisions": []}.

Use when generating handles for an import, or checking one you already
have. Not for validating a whole header row — that is product_csv_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "title must not be empty"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `existing`: Handles already used in the store or the file, so a collision can be reported and a suffixed alternative suggested. Optional.
- `title` (string, required): The product title or a candidate handle, e.g. "Men's Merino Wool Socks".

### `variant_matrix` (~344 tokens)

Variant Matrix

Count the variants a set of options produces, and flag the ceilings. FREE.

Option counts multiply, so three modest lists become a number nobody
intended. Typical input {"options": {"Size": ["S", "M", "L"], "Colour":
["Black", "Navy"]}} returns {"option_count": 2, "variant_count": 6,
"within_limits": true, "per_option": {"Size": 3, "Colour": 2}}.

Use before building an import file, to find out whether the catalogue
needs splitting into several products. Not for validating the resulting
CSV's columns — that is product_csv_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "options must contain at least one option"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `list_rows` (boolean): When true, also return every variant combination. Off by default because the list can be very large.
- `max_options` (integer): Ceiling on distinct option names. Default 3.
- `max_variants` (integer): Ceiling to check against. Default 2048, which is the limit Shopify announced on 15 October 2025, up from 100. Override it if your plan differs.
- `options` (object, required): Option names mapped to their values, e.g. {"Size": ["S", "M"], "Colour": ["Black"]}. Each list needs at least one value.

### `metafield_key_check` (~267 tokens)

Metafield Key Check

Validate a metafield namespace and key before you define it. FREE.

Shopify metafield namespaces and keys are lowercase alphanumerics and
underscores; a capital letter or a dash is rejected at definition time,
usually after the rest of the import has already run. Typical input
{"namespace": "custom", "key": "Care-Instructions"} returns {"ok": false,
"problems": ["key: dashes and capitals are not allowed"], "suggested_key":
"care_instructions"}.

Use when designing metafields. Not for the CSV column that carries them —
that is product_csv_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `key` (string, required): The metafield key, e.g. "care_instructions".
- `namespace` (string, required): The metafield namespace, e.g. "custom".
- `value_type` (string): The intended metafield type, echoed back for your record, e.g. "single_line_text_field". Not validated against Shopify's type list, which changes.

### `bulk_price_change` (~386 tokens)

Bulk Price Change

Apply one pricing rule across a list of prices and show the effect. PREMIUM (license).

Percentage first, then the flat amount, then rounding — stated explicitly
because the order changes the answer. Typical input {"prices": [19.99,
24.5], "change_pct": 10, "charm_ending": ".99"} returns {"rows":
[{"was": 19.99, "now": 21.99}, {"was": 24.5, "now": 26.99}],
"total_was": 44.49, "total_now": 48.98, "uplift_pct": 10.09}.

Use when repricing a catalogue before export. Not for what a price nets
you after Shopify's fees — that is payout_estimate. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "prices must contain at least one price"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `change_flat` (number): Flat amount applied after the percentage. Default 0.
- `change_pct` (number): Percentage change applied first, e.g. 10 to raise by 10% or -5 to cut by 5%. Default 0.
- `charm_ending` (string): Force every price to end in these cents, e.g. ".99" or ".95". Applied after rounding. Empty by default.
- `prices` (array, required): Current prices, at least one, each greater than 0.
- `round_to` (number): Rounding increment applied last, e.g. 0.01 or 0.05. Default 0.01.

### `payout_estimate` (~315 tokens)

Payout Estimate

Estimate what actually lands in the bank after processing fees. PREMIUM (license).

Typical input {"order_total": 84.5, "fee_pct": 2.9, "fee_fixed": 0.3,
"orders": 120, "refund_rate_pct": 4} returns {"gross": 10140.0, "fees":
330.06, "refunds": 405.6, "net_payout": 9404.34, "effective_fee_pct":
3.26}.

Use for cash-flow planning. Not as an authoritative fee schedule: rates
depend on your plan, country and card mix, so pass your own. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `fee_fixed` (number): Fixed fee per transaction. Default 0.30.
- `fee_pct` (number): Percentage fee per transaction. Default 2.9 — a common published rate, not a promise about your account.
- `order_total` (number, required): Value of one order including anything the processor takes a percentage of. Must be greater than 0.
- `orders` (integer): How many orders to model. Default 1.
- `refund_rate_pct` (number): Share of order value refunded, as a percentage. Default 0.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-moltlinestudio-shopify/shopify#diagnostics

## Score history

- 2026-09-20: 87
- 2026-09-19: 87
- 2026-09-18: 86
- 2026-09-17: 86
- 2026-09-16: 85
- 2026-09-15: 85
- 2026-09-14: 84
- 2026-09-13: 84
- 2026-09-12: 83
- 2026-09-11: 83
- 2026-09-10: 82
- 2026-09-09: 82
- 2026-09-08: 81
- 2026-09-07: 81
- 2026-09-06: 81
- 2026-09-05: 80
- 2026-09-04: 80
- 2026-09-03: 79
- 2026-09-02: 79
- 2026-09-01: 78
- 2026-08-31: 78
- 2026-08-30: 77
- 2026-08-29: 77
- 2026-08-28: 76
- 2026-08-27: 76
- 2026-08-26: 75
- 2026-08-25: 73
- 2026-08-24: 73
- 2026-08-23: 72
- 2026-08-22: 72

## Common questions

### What is the Moltline Shopify Prep MCP server?

Moltline Shopify Prep is an MCP server listed in the public MCP registry as com.moltlinestudio/shopify. Check a product CSV, handles, variant matrices and metafield keys. 4 of 6 free. This page covers its hosted endpoint (https://mcp.moltlinestudio.com/shopify).

### Is the Moltline Shopify Prep MCP server safe to use?

Moltline Shopify Prep scores 87 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 Moltline Shopify Prep MCP server expose?

Moltline Shopify Prep exposes 6 tools: product_csv_check, url_handle, variant_matrix, metafield_key_check, bulk_price_change, payout_estimate. Their descriptions and schemas cost roughly 1,877 tokens of context every time the server is loaded.

### Does the Moltline Shopify Prep MCP server require authentication?

No. We connected to Moltline Shopify Prep without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Moltline Shopify Prep MCP server still maintained?

Moltline Shopify Prep is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.moltlinestudio.com/shopify
- Repository: https://github.com/GarphenGate/moltline-mcp
- Website: https://moltlinestudio.com/servers.html#shopify
- Changelog RSS feed: https://verifymcp.io/servers/com-moltlinestudio-shopify/shopify.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-moltlinestudio-shopify/shopify.json
- HTML version of this page: https://verifymcp.io/servers/com-moltlinestudio-shopify/shopify