Skills/npm/shopify-multi-store-mcp-server

shopify-multi-store-mcp-server@2.2.1

VERIFIED· startup only

Publisher claims: "One MCP server for every Shopify store: 31 tools for search, reports, bulk exports, inventory, discounts, content, webhooks and guarded writes, plus all Admin API mutations. Read-only mode. Claude, ChatGPT, Codex, Cursor, VS Code, or hosted on Cloudflare." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher alex-brecher · publishing for 88 daysInstalls 862Last detonated 56 min ago
$claude mcp add shopify-multi-store-mcp-server -- npx -y shopify-multi-store-mcp-server
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
OAUTH_ALLOW_ANY_REDIRECTOAUTH_ALLOW_LOOPBACK_REDIRECTSOAUTH_CIMD_ALLOWED_HOSTSOAUTH_REDIRECT_URISOAUTH_REDIRECT_URIS_REPLACEOAUTH_STORESHOPIFY_APP_CLIENT_SECRETSHOPIFY_MULTI_STORE_OAUTH_STORESHOPIFY_TOKEN_ENCRYPTION_KEYSHOPIFY_TOKEN_ENCRYPTION_KEYSConfiguration, not credentials: ACTIONS_DENYLIST, ACTIONS_DENYLIST_REPLACE, AUDIT_DB, MCP_PUBLIC_URL, SERVER_DISPLAY_NAME, SHOPIFY_APP_CLIENT_ID, SHOPIFY_APP_SCOPES, SHOPIFY_IDENTITY_STORE, SHOPIFY_MULTI_STORE_ALLOW_FILE_KEYRING, SHOPIFY_MULTI_STORE_AUDIT_LOG, SHOPIFY_MULTI_STORE_DATA_DIR, SHOPIFY_READ_ONLY, SHOPIFY_READ_ONLY_STORES, SHOPIFY_READ_ONLY_USERS
Where it talks to
no vendor host named in the codeAlso shopify.dev — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names shopify.dev as well as its own vendor. The guard injects OAUTH_ALLOW_ANY_REDIRECT, OAUTH_ALLOW_LOOPBACK_REDIRECTS, OAUTH_CIMD_ALLOWED_HOSTS, OAUTH_REDIRECT_URIS, OAUTH_REDIRECT_URIS_REPLACE, OAUTH_STORE, SHOPIFY_APP_CLIENT_SECRET, SHOPIFY_MULTI_STORE_OAUTH_STORE, SHOPIFY_TOKEN_ENCRYPTION_KEY, SHOPIFY_TOKEN_ENCRYPTION_KEYS only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- npx -y shopify-multi-store-mcp-server

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

What changed since 2.0.3

vet-skills diff shopify-multi-store-mcp-server 2.0.3 2.2.1

In the sandbox, this version reached for nothing 2.0.3 did not. Compared from the two recorded runs, not from source.

No longer contacted
oauth-store.internal

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-18 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 28 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
7.7sprocessdependency install exit 0
28sclaimedstartup only: exited (0) before answering · code: 'ERR_MODULE_NOT_FOUND', url: 'file:///tmp/ks-detonate-b0Eocp/task/home/work/acme-api/.claude/skills/shopify-multi-store-mcp-server/dist/platform/schema-source.js' } Node.js v22.23.5
28sprocessscript backend runs setup only
28sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packagepackage.json:43 · npx invocation of non-well-known package — may execute untrusted code…. The Deploy to Cloudflare flow creates it. With the CLI, create it first with `npx wrangler d1 create shopify-multi-store-audit` and put its database_id in wrangler.jsonc;…Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
Collapsed <details> block carrying instructionsREADME.md:242 · Collapsed <details> block carrying instructions<summary><strong>Import an existing stores.json file</strong></summary> ```bash shopify-multi-store import /absolute/path/to/stores.json ``` The import copies cFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01

Cost to the agent

Instructions loaded
≈109 tok
1 file · 81 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for shopify-multi-store-mcp-server@2.2.1 as of 7 min ago. This is the package itself, not its dependencies.