Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Nothing to run from here
Moltline Shopify Prep is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
6
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Check a product CSV, handles, variant matrices and metafield keys. 4 of 6 free.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http moltline-shopify-prep-mcp https://mcp.moltlinestudio.com/shopify
# 2 — ask your agent for something these tools do
# product_csv_check, url_handle, variant_matrix and 3 more
Moltline Shopify Prep costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MOAll 22 servers
moltlinestudio22 servers
15 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http moltline-shopify-prep-mcp https://mcp.moltlinestudio.com/shopifyReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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"}, ...], "unrecogn
| Parameter | Type | Required | Notes |
|---|---|---|---|
| header_row | array | yes | 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 | no | "new" when creating products, where Shopify requires only Title; "update" when changing existing ones, where it also requires URL handle. Default "new". |
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 alr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | The product title or a candidate handle, e.g. "Men's Merino Wool Socks". |
| existing | no | Handles already used in the store or the file, so a collision can be reported and a suffixed alternative suggested. Optional. |
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 wh
| Parameter | Type | Required | Notes |
|---|---|---|---|
| options | object | yes | Option names mapped to their values, e.g. {"Size": ["S", "M"], "Colour": ["Black"]}. Each list needs at least one value. |
| max_variants | integer | no | 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. |
| max_options | integer | no | Ceiling on distinct option names. Default 3. |
| list_rows | boolean | no | When true, also return every variant combination. Off by default because the list can be very large. |
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 a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| namespace | string | yes | The metafield namespace, e.g. "custom". |
| key | string | yes | The metafield key, e.g. "care_instructions". |
| value_type | string | no | The intended metafield type, echoed back for your record, e.g. "single_line_text_field". Not validated against Shopify's type list, which changes. |
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, "
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prices | array | yes | Current prices, at least one, each greater than 0. |
| change_pct | number | no | Percentage change applied first, e.g. 10 to raise by 10% or -5 to cut by 5%. Default 0. |
| change_flat | number | no | Flat amount applied after the percentage. Default 0. |
| round_to | number | no | Rounding increment applied last, e.g. 0.01 or 0.05. Default 0.01. |
| charm_ending | string | no | Force every price to end in these cents, e.g. ".99" or ".95". Applied after rounding. Empty by default. |
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, cou
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_total | number | yes | Value of one order including anything the processor takes a percentage of. Must be greater than 0. |
| fee_pct | number | no | Percentage fee per transaction. Default 2.9 — a common published rate, not a promise about your account. |
| fee_fixed | number | no | Fixed fee per transaction. Default 0.30. |
| refund_rate_pct | number | no | Share of order value refunded, as a percentage. Default 0. |
| orders | integer | no | How many orders to model. Default 1. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Moltline Shopify Prep or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.2.0.
1.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Moltline Shopify Prep can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.