Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Shopify Store Sync

NPM · SHOPIFY-STORE-SYNC-MCP

Diff and sync Shopify stores: dry-run plans, cross-store ID remapping, never deletes.

71 Trust /100

Last scanned (13 hours ago)

Scores higher than 42% of npm servers

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4699 tokens (~361/item across 13 items; 13 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 Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.84 ▲ functional
  • 18 Nov 26 −9
    • Known CVEs: pass → unverified ▼ security
    • Schema quality: 261 → 361 ▼ functional
    • Dependency health: 0.85 → unverified ▼ functional
    • Tool coverage: 95% → 100% ▲ functional
    • Schema quality: good → excellent functional
    • Package version: 0.11.4 → 0.11.8 functional
    • Package version: 0.11.4 → 0.11.7 functional
  • 17 Nov 26 +26
    • Stability: 0.03 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Known CVEs: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Dependency health: unverified → 0.85 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.10.2 → 0.11.4 functional
    • Package version: 0.10.2 → 0.10.4 functional
  • 16 Nov 26 −10
    • Known CVEs: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Schema quality: 224 → 272 ▼ functional
    • Schema quality: 224 → 284 ▼ functional
    • Schema quality: 224 → 262 ▼ functional
    • Dependency health: 0.85 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.5.1 → 0.10.2 functional
    • Package version: 0.5.1 → 0.10.1 functional
    • Package version: 0.5.1 → 0.9.2 functional
    • Package version: 0.5.1 → 0.9.0 functional
    • Package version: 0.5.1 → 0.8.1 functional
    • Package version: 0.5.1 → 0.8.0 functional
    • Package version: 0.5.1 → 0.6.0 functional
  • 15 Nov 26 52

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/shopify-store-sync-mcp@0.11.8

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~4,550 tokens

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 →

Tool Tokens
apply_plan ~319

Write a reviewed plan to the target store. Refused unless the target has allowWrites=true. For a protected store the person is asked to confirm in the client (or applies from the command line); the assistant can't confirm on their behalf. Re-reads the target first and skips anything that changed since planning. Uploads missing files. Creates and updates only, never deletes. Every op is written to the audit log (get_audit_log). Returns { plan_id, status, totals (created, updated, skipped, failed), results per op }; a plan of more than 50 steps runs in the background instead and returns at once: follow it with apply_status and stop it with cancel_apply. A plan can be applied once, within an hour of plan_sync.

NameTypeReqDescription
confirmstring–Leave empty. Only read when the server runs with SYNC_ALLOW_AGENT_CONFIRM=true (unattended automation); otherwise a protected store is confirmed by the person, not by this argument.
onlyarray–Apply only these ops, by their seq number in the plan (e.g. [1, 2, 3]). Default: every op.
plan_idstringyesThe plan to write, from plan_sync. It must not have been applied yet and must be less than an hour old.
waitboolean–Wait for the whole apply before returning. By default a plan of more than 50 steps (SYNC_BACKGROUND_STEPS) runs in the background and this returns at once; follow it with apply_status.

No output schema declared.

No examples provided.

apply_status ~205

How far an apply has got: steps created, updated, skipped, failed and left per resource type, the current phase, progress inside a Shopify bulk operation, time so far and an estimate of the time left, failures counted per resource type and reason, and the latest failures. Also answers for an apply that ended or was interrupted by a server restart. Call it after apply_plan returns a background apply, every minute or so until state is done or error. resource narrows only the listed failures; the counts always cover every resource type. For what each step wrote use get_audit_log, to stop the apply use cancel_apply, and for what was planned use get_plan.

NameTypeReqDescription
failuresinteger–How many of the latest failures to list (default 20).
plan_idstring–The plan whose apply to report on. Default: the most recent apply.
resourcestring–List only the failures of this resource type, e.g. products.

No output schema declared.

No examples provided.

cancel_apply ~134

Stop an apply that is running in the background: no further step is started and the Shopify bulk operations it started are cancelled. What was already written stays written (nothing is rolled back or deleted). Also stops bulk operations left running by an apply whose server was restarted. If the apply has already ended, nothing is cancelled and its final state is returned. Returns { plan_id, state (cancelling, or interrupted for an apply from before a restart), note }. Follow with apply_status, then plan_sync to see what is left.

NameTypeReqDescription
plan_idstring–The plan being applied. Default: the most recent apply.

No output schema declared.

No examples provided.

compare_item ~238

Compare a single item between two stores, side by side: whether each has it, every field that differs (entry by entry inside JSON values), and whether the items it points at (products, pages, metaobjects...) exist in the target. Reads only that item where possible, so it is quick. Returns { status (identical, different, only in source, only in target, in neither), changes, refs, notCompared }. Use it for a targeted check instead of diff_stores; take the key from a diff_stores result.

NameTypeReqDescription
formatstring–"markdown" returns a report.
keystringyesThe item's key, as diff_stores lists it: "size_guide/shirts" (metaobjects), "faq" (pages), "PRODUCT.custom.fabric" (metafield_definitions)...
resourcestringyesResource type of the item
sourcestringyesStore alias, or "dir:<path>" for a snapshot folder made with export_snapshot.
targetstringyesStore alias, or "dir:<path>" for a snapshot folder made with export_snapshot.

No output schema declared.

No examples provided.

diff_stores ~737

Compare configuration between a source and a target, resource type by resource type. Returns for each type the counts (onlyInSource, changed, onlyInTarget, identical) and the keys in each section, with before and after values for every changed field (show_values=false keeps only the field paths); limit caps each list while the counts cover everything, and format="markdown" gives a report to share. Either side can be a snapshot folder ("dir:<path>"), e.g. to check whether production drifted from the committed config. The options shared with plan_sync (resources, include, prices, inventory, as_drafts...) only decide what is read and compared, so the diff matches the plan the same options would produce; nothing is written. Use compare_item for a single item, diff_themes for theme settings, and plan_sync to prepare the changes.

NameTypeReqDescription
as_draftsboolean–Leave the published state out of what is compared and copied: in a plan, new pages are created hidden and new metaobject entries as drafts, and existing ones keep their state. Products are always cre…
excludearray–Drop keys matching any of these globs.
formatstring–"markdown" returns a report to paste into a ticket or an email.
includearray–Only keys matching one of these globs, e.g. ["PRODUCT.custom.*", "faq/*", "fr:*"].
include_reservedboolean–metafield_definitions: also compare Shopify-reserved ones (namespace "shopify", the category metafields that drive storefront filters). Compared only: a plan reports them as conflicts and never write…
inventoryboolean–products: include stock (the available quantity per location, matched to the target's location with the same name) in what is read, compared and planned. Off by default. Needs read_inventory and read…
limitinteger–Max items listed per section (default 100, markdown 50). The counts always cover everything.
localesarray–Limit translations to these locales, e.g. ["fr", "de"]. Default: every non-primary locale.
metaobject_typesarray–Limit metaobjects to these types. Default: all non-reserved types.
namespacesarray–Limit metafield values (metafields) to these namespaces.
owner_typesarray–Metafield owner types. For metafield_definitions, default: PRODUCT, PRODUCTVARIANT, COLLECTION, CUSTOMER, ORDER, DRAFTORDER, COMPANY, COMPANY_LOCATION, LOCATION, MARKET, PAGE, BLOG, ARTICLE, SHOP. Fo…
pricesboolean–products: include variant prices and compare-at prices in what is read, compared and planned. Off by default, since prices usually differ per store.
resourcesarray–Resource types to include. Default: metafield_definitions, metaobject_definitions, collections, pages, shop_policies, metaobjects, menus, redirects. products, metafields and translations are opt-in.
show_valuesboolean–Include before/after values for each changed field (default true).
sourcestringyesStore alias, or "dir:<path>" for a snapshot folder made with export_snapshot.
targetstringyesStore alias, or "dir:<path>" for a snapshot folder made with export_snapshot.

No output schema declared.

No examples provided.

diff_themes ~338

Compare theme configuration between two stores: JSON templates, section groups and settings_data.json (default files: templates/*.json, sections/*.json, config/settings_data.json). Use it for theme settings; use diff_stores for store data such as metafields, metaobjects and pages. Compares the published themes unless source_theme or target_theme give theme ids. Returns file counts (onlyInSource, changed, onlyInTarget, identical), the files on one side only, and for each changed file the settings that differ with both values (first 100 per file); format="markdown" gives a report. Use ignore_settings to quiet settings that differ on purpose. Never writes to a theme; both stores need the read_themes scope.

NameTypeReqDescription
excludearray–Theme file patterns to leave out, e.g. ["templates/gift_card.json"].
filesarray–Theme file patterns, e.g. ["templates/product*.json"]
formatstring–"markdown" returns a report to paste into a ticket or an email.
ignore_settingsarray–Settings to leave out, as globs on their path, optionally limited to files: ["current.sections.header.*", "config/settings_data.json:current.color_*"]. Use it to quiet settings that differ on purpose…
sourcestringyesStore alias to compare from (snapshot folders hold no themes).
source_themestring–"main" (default) or a theme id
targetstringyesStore alias to compare with.
target_themestring–"main" (default) or a theme id

No output schema declared.

No examples provided.

export_snapshot ~632

Save a store's configuration to a folder on disk, one JSON file per item (sorted keys, no store IDs), ready to commit to git. dir must be new, empty, or an earlier snapshot folder (its item files are replaced); any other folder is refused. Returns a summary { dir, files, kinds } with the count per resource type, not the data; to see the data in the response use snapshot_store. Later, pass "dir:<path>" as the source of diff_stores or plan_sync to compare against it or restore from it. Reads the store and writes only local files, never to Shopify.

NameTypeReqDescription
as_draftsboolean–Leave the published state out of what is compared and copied: in a plan, new pages are created hidden and new metaobject entries as drafts, and existing ones keep their state. Products are always cre…
dirstringyesFolder to write, inside the snapshot base folder (SYNC_SNAPSHOT_DIR, or the folder the server runs in). Must be empty, new, or an earlier snapshot folder (its item files are replaced).
excludearray–Drop keys matching any of these globs.
includearray–Only keys matching one of these globs, e.g. ["PRODUCT.custom.*", "faq/*", "fr:*"].
include_reservedboolean–metafield_definitions: also compare Shopify-reserved ones (namespace "shopify", the category metafields that drive storefront filters). Compared only: a plan reports them as conflicts and never write…
inventoryboolean–products: include stock (the available quantity per location, matched to the target's location with the same name) in what is read, compared and planned. Off by default. Needs read_inventory and read…
localesarray–Limit translations to these locales, e.g. ["fr", "de"]. Default: every non-primary locale.
metaobject_typesarray–Limit metaobjects to these types. Default: all non-reserved types.
namespacesarray–Limit metafield values (metafields) to these namespaces.
owner_typesarray–Metafield owner types. For metafield_definitions, default: PRODUCT, PRODUCTVARIANT, COLLECTION, CUSTOMER, ORDER, DRAFTORDER, COMPANY, COMPANY_LOCATION, LOCATION, MARKET, PAGE, BLOG, ARTICLE, SHOP. Fo…
pricesboolean–products: include variant prices and compare-at prices in what is read, compared and planned. Off by default, since prices usually differ per store.
resourcesarray–Resource types to include. Default: metafield_definitions, metaobject_definitions, collections, pages, shop_policies, metaobjects, menus, redirects. products, metafields and translations are opt-in.
storestringyesStore alias to read

No output schema declared.

No examples provided.

get_audit_log ~206

Read what apply_plan wrote: the most recent audit log entries, newest first, one per step (plan, target store, resource type, key, outcome and message). Filter by plan, outcome (created, updated, skipped, failed) or resource type. Returns { log (file path), matched, returned, entries }: limit (default 50) caps the entries while matched counts every match; in a very large log only the most recent 8 MB is searched. Use it after an apply to see exactly what was written; use apply_status for the progress of a running apply and get_plan for what a plan intended. The log is a local file; nothing is read from Shopify.

NameTypeReqDescription
limitinteger–Max entries returned (default 50). matched counts them all.
outcomestring–Only entries with this outcome.
plan_idstring–Only entries of this plan.
resourcestring–Only entries of this resource type.

No output schema declared.

No examples provided.

get_plan ~230

Show a sync plan made by plan_sync, before or after it is applied. With plan_id: the plan as plan_sync returned it (totals, ops with field changes, warnings, expiry) plus, once applied, the apply's state and totals; only the first 200 ops are listed and long values are shortened unless full=true, and format="markdown" gives a report to share for review. Without plan_id: the 20 most recent plans (plan_id, createdAt, status, source, target, op count), to find one. To create a plan use plan_sync, to write it use apply_plan, and to follow a running apply use apply_status. Reads only the plans saved by this server, nothing from Shopify.

NameTypeReqDescription
formatstring–"markdown" returns the plan as a report, to share before applying it.
fullboolean–List every op with full values (default: first 200 ops, long values shortened).
plan_idstring–The plan to show, as returned by plan_sync. Omit to list the recent plans.

No output schema declared.

No examples provided.

list_resource_types ~115

List the resource types this server can snapshot, diff and sync (metafield definitions, metaobjects, pages, menus, products...). Returns [{ kind, default, description }]: kind is the value to pass in the resources argument of snapshot_store, export_snapshot, diff_stores and plan_sync; default tells whether it is read when resources is omitted; description says how items are keyed and what is copied. Use it to choose resources; use list_stores for the stores themselves. Takes no arguments and makes no Shopify calls.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_stores ~133

List the Shopify stores this server is configured for. Call it first: the aliases it returns are the store names every other tool takes (source, target, store). Returns { server, stores: [{ alias, domain, label, apiVersion, auth, allowWrites, protected }] }. allowWrites=false means apply_plan refuses that store; protected=true means a person confirms every apply to it. An empty list means no store is set up yet. Tokens and secrets are never returned. Takes no arguments and makes no Shopify calls. Next: list_resource_types for what can be synced, diff_stores to compare two stores.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

plan_sync ~664

Build a dry-run plan that would make the target store match the source (a store or a "dir:<path>" snapshot folder) for the selected resources. Reads both sides and writes nothing. Returns { plan_id, expiresAt, totals (create, update, conflict), byResource, ops, warnings, filesToUpload, onlyInTarget, targetWritable, targetProtected }; each op has a seq number, key, action, reason, missing references and field changes (the first 200 ops are listed). Conflicts are items that can't be written, with the reason; items only in the target are listed and never deleted. Show the plan to the person, then pass plan_id to apply_plan; it expires after one hour, and get_plan shows it again. To only look at differences, use diff_stores instead.

NameTypeReqDescription
as_draftsboolean–Leave the published state out of what is compared and copied: in a plan, new pages are created hidden and new metaobject entries as drafts, and existing ones keep their state. Products are always cre…
excludearray–Drop keys matching any of these globs.
includearray–Only keys matching one of these globs, e.g. ["PRODUCT.custom.*", "faq/*", "fr:*"].
include_reservedboolean–metafield_definitions: also compare Shopify-reserved ones (namespace "shopify", the category metafields that drive storefront filters). Compared only: a plan reports them as conflicts and never write…
inventoryboolean–products: include stock (the available quantity per location, matched to the target's location with the same name) in what is read, compared and planned. Off by default. Needs read_inventory and read…
localesarray–Limit translations to these locales, e.g. ["fr", "de"]. Default: every non-primary locale.
metaobject_typesarray–Limit metaobjects to these types. Default: all non-reserved types.
namespacesarray–Limit metafield values (metafields) to these namespaces.
owner_typesarray–Metafield owner types. For metafield_definitions, default: PRODUCT, PRODUCTVARIANT, COLLECTION, CUSTOMER, ORDER, DRAFTORDER, COMPANY, COMPANY_LOCATION, LOCATION, MARKET, PAGE, BLOG, ARTICLE, SHOP. Fo…
pricesboolean–products: include variant prices and compare-at prices in what is read, compared and planned. Off by default, since prices usually differ per store.
resourcesarray–Resource types to include. Default: metafield_definitions, metaobject_definitions, collections, pages, shop_policies, metaobjects, menus, redirects. products, metafields and translations are opt-in.
sourcestringyesStore alias, or "dir:<path>" for a snapshot folder made with export_snapshot.
targetstringyesStore alias the plan would write to (see list_stores; snapshot folders can't be a target).

No output schema declared.

No examples provided.

snapshot_store ~599

Read one store's configuration (or a snapshot folder made with export_snapshot) and return it in the response, in portable form with store IDs replaced by handles. Returns { store, domain, takenAt, resources: [{ kind, count, items }] }: items are keys only, or { key, data } with full=true, which can be large, so narrow first with resources, include or the other filters. Use it to inspect one store; to save the configuration to files use export_snapshot, and to compare two stores use diff_stores. Writes nothing.

NameTypeReqDescription
as_draftsboolean–Leave the published state out of what is compared and copied: in a plan, new pages are created hidden and new metaobject entries as drafts, and existing ones keep their state. Products are always cre…
excludearray–Drop keys matching any of these globs.
fullboolean–Include each item's data (can be large).
includearray–Only keys matching one of these globs, e.g. ["PRODUCT.custom.*", "faq/*", "fr:*"].
include_reservedboolean–metafield_definitions: also compare Shopify-reserved ones (namespace "shopify", the category metafields that drive storefront filters). Compared only: a plan reports them as conflicts and never write…
inventoryboolean–products: include stock (the available quantity per location, matched to the target's location with the same name) in what is read, compared and planned. Off by default. Needs read_inventory and read…
localesarray–Limit translations to these locales, e.g. ["fr", "de"]. Default: every non-primary locale.
metaobject_typesarray–Limit metaobjects to these types. Default: all non-reserved types.
namespacesarray–Limit metafield values (metafields) to these namespaces.
owner_typesarray–Metafield owner types. For metafield_definitions, default: PRODUCT, PRODUCTVARIANT, COLLECTION, CUSTOMER, ORDER, DRAFTORDER, COMPANY, COMPANY_LOCATION, LOCATION, MARKET, PAGE, BLOG, ARTICLE, SHOP. Fo…
pricesboolean–products: include variant prices and compare-at prices in what is read, compared and planned. Off by default, since prices usually differ per store.
resourcesarray–Resource types to include. Default: metafield_definitions, metaobject_definitions, collections, pages, shop_policies, metaobjects, menus, redirects. products, metafields and translations are opt-in.
storestringyesStore alias, or "dir:<path>" for a snapshot folder made with export_snapshot.

No output schema declared.

No examples provided.

Install

How do I install the Shopify Store Sync MCP server?

Shopify Store Sync runs locally as an npm package, launched with npx -y shopify-store-sync-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · shopify-store-sync-mcp

# add to Claude Code
claude mcp add ussefidder-shopify-store-sync-mcp -- npx -y shopify-store-sync-mcp
Common questions

What is the Shopify Store Sync MCP server?

Shopify Store Sync is an MCP server listed in the public MCP registry as io.github.ussefidder/shopify-store-sync-mcp. Diff and sync Shopify stores: dry-run plans, cross-store ID remapping, never deletes. This page covers its npm package (shopify-store-sync-mcp).

Is the Shopify Store Sync MCP server safe to use?

Shopify Store Sync scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Shopify Store Sync MCP server expose?

Shopify Store Sync exposes 13 tools: list_stores, list_resource_types, snapshot_store, export_snapshot, diff_stores, and 8 more. Their descriptions and schemas cost roughly 4,550 tokens of context every time the server is loaded.

Is the Shopify Store Sync MCP server still maintained?

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

What licence is the Shopify Store Sync MCP server under?

Shopify Store Sync declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Shopify Store Sync MCP server?

VerifyMCP ran 16 checks on Shopify Store Sync, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.