Shopify (akson) MCP Server
@akson/mcp-shopify
npm
v1.0.2
Published by @akson — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
A comprehensive Model Context Protocol (MCP) server for Shopify Admin API integration
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Shell/command execution in server code (bin/shopify-mcp-server.js)MTC-SRC-002
In the server's implementation (`bin/shopify-mcp-server.js:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from 'child_process'; import { fileURLToPath } from 'url'; import { dirname, join } from 'path'; cons
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server bin/shopify-mcp-server.js
Tools 23
Each tool and what it can reach — statically extracted from the published source.
get_best_sellersno sensitive capabilityget_collection_productsno sensitive capabilityget_customerno sensitive capabilityget_customer_ordersno sensitive capabilityget_discountno sensitive capabilityget_inventory_levelsno sensitive capabilityget_locationsno sensitive capabilityget_orderno sensitive capabilityget_order_transactionsno sensitive capabilityget_productno sensitive capability
Show 13 more tools ↓
get_product_metafieldsno sensitive capabilityget_product_variantsno sensitive capabilityget_sales_summaryno sensitive capabilityget_shipping_zonesno sensitive capabilityget_shop_infono sensitive capabilitylist_collectionsno sensitive capabilitylist_customersno sensitive capabilitylist_discountsno sensitive capabilitylist_fulfillment_servicesno sensitive capabilitylist_ordersno sensitive capabilitylist_productsno sensitive capabilitysearch_customersno sensitive capabilitysearch_productsno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (23 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.2 latest |
A 93/100 | 1 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @akson/mcp-shopify --onlineOther implementations of Shopify 14
Independent packages implementing the same tool, scanned with the same engine. Compare all 15 side by side →
Model Context Protocol server for the Shopify Admin GraphQL API
MCP Server for Shopify API, enabling interaction with store data through GraphQL API
Shopify Admin GraphQL API MCP server by AIWerk - manage products, orders, customers, inventory, and more from your AI agent
MCP Server for Shopify API, enabling interaction with store data through GraphQL API
MCP server for shopify integration
Shopify MCP Pack — wraps the Shopify Admin REST API (2024-01)
More in Business & CRM
Free public tax reference data — GST/VAT, income, company and capital-gains tax rules for 50+ countries.
The approval gate for unattended UCP buying agents — a policy/approval MCP proxy in front of a merchant's UCP checkout endpoint.
Autotask PSA MCP server. Generic entity query/get/create/update across the full REST API plus convenience tools for tickets, companies, contacts, projects, tasks and time entries. AI-safe with readonly mode and destructive-action confirmation. stdio + opt
MCP server for B2C Commerce developer experience tools
Search, compare and contact real-world companies through a public MCP business directory.
Norwegian business register (Brønnøysundregistrene) as an MCP server — companies, roles, subunits and annual accounts, with the register's silent traps encoded as guards.