Moltline Shopify Prep
REMOTE · MCP.MOLTLINESTUDIO.COM
Check a product CSV, handles, variant matrices and metafield keys. 4 of 6 free.
Available components
Last scanned (13 minutes ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 26 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “bulk_price_change” rewrote its description, which is the text the model reads security
- Tool “metafield_key_check” rewrote its description, which is the text the model reads security
- Tool “product_csv_check” rewrote its description, which is the text the model reads security
- Tool “url_handle” rewrote its description, which is the text the model reads security
- Tool “variant_matrix” rewrote its description, which is the text the model reads security
- “payout_estimate” reworded the description of “fee_pct” cosmetic
- 25 Oct 26 0
- Tool “bulk_price_change” rewrote its description, which is the text the model reads security
- Tool “metafield_key_check” rewrote its description, which is the text the model reads security
- Tool “payout_estimate” rewrote its description, which is the text the model reads security
- Tool “product_csv_check” rewrote its description, which is the text the model reads security
- Tool “url_handle” rewrote its description, which is the text the model reads security
- Tool “variant_matrix” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.moltlinestudio.com/shopify
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=moltlinestudio.com | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 5fcf21014c71aedb0ee8aa375beac0b4 |
| SANs: moltlinestudio.com, *.moltlinestudio.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.moltlinestudio.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| moltlinestudio.com. | present | 2371 | 13 | Verified |
| mcp.moltlinestudio.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15576000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'nonce-26fdb5f1-a7c0-4af1-b2e5-5e34c459568b'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self' https://api.moltlinestudio.com https://mcp.moltlinestudio.com; form-action 'self'; frame-ancestors 'none'; base-uri 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.moltlinestudio.com/shopify | Verified | 200 | |
| http (plaintext) | http://mcp.moltlinestudio.com/shopify | HTTPS enforced | 301 | https://mcp.moltlinestudio.com/shopify |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bulk_price_change Bulk Price Change ~386
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
metafield_key_check Metafield Key Check ~267
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | The metafield key, e.g. "care_instructions". |
| namespace | string | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
payout_estimate Payout Estimate ~315
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
product_csv_check Product Csv Check ~311
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | "new" when creating products, where Shopify requires only Title; "update" when changing existing ones, where it also requires URL handle. Default "new". |
Structured output declared, but exposes no named fields.
No examples provided.
url_handle Url Handle ~254
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.
| Name | Type | Req | Description |
|---|---|---|---|
| existing | – | – | Handles already used in the store or the file, so a collision can be reported and a suffixed alternative suggested. Optional. |
| title | string | yes | The product title or a candidate handle, e.g. "Men's Merino Wool Socks". |
Structured output declared, but exposes no named fields.
No examples provided.
variant_matrix Variant Matrix ~344
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Option names mapped to their values, e.g. {"Size": ["S", "M"], "Colour": ["Black"]}. Each list needs at least one value. |
Structured output declared, but exposes no named fields.
No examples provided.
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.
remote · mcp.moltlinestudio.com
claude mcp add --transport http com-moltlinestudio-shopify 'https://mcp.moltlinestudio.com/shopify'
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 86 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.