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.

io.github.enzoemir1/shopops-mcp

NPM · SHOPOPS-MCP-SERVER · SCANNED SEP 20

AI e-commerce operations. Inventory, pricing, segmentation, and analytics.

Available components

0 this week 79 Trust /100
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
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1208 tokens (~75/item across 16 items; 12 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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
Install

How do I install the io.github.enzoemir1/shopops-mcp server?

io.github.enzoemir1/shopops-mcp runs locally as an npm package, launched with npx -y shopops-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · shopops-mcp-server

# add to Claude Code
claude mcp add enzoemir1-shopops-mcp -- npx -y shopops-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "enzoemir1-shopops-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "shopops-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "enzoemir1-shopops-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "shopops-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add enzoemir1-shopops-mcp -- npx -y shopops-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "enzoemir1-shopops-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "shopops-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add enzoemir1-shopops-mcp --command npx --arg -y --arg shopops-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  enzoemir1-shopops-mcp:
    command: "npx"
    args: ["-y", "shopops-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "enzoemir1-shopops-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "shopops-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add enzoemir1-shopops-mcp -t stdio -c npx -a -y shopops-mcp-server
// mcp.json
{
  "mcpServers": {
    "enzoemir1-shopops-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "shopops-mcp-server"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 17 Sept 26 −4
    • Stability: pass → 0.77 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/shopops-mcp-server@1.2.2

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 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~1,146 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
customers_churn ~95

Identify customers at risk of churning based on RFM recency + frequency signals. Returns an object with at_risk, hibernating, and lost arrays — each contains customer id, name, email, last_order_date, days_since_last_order, total_spent, total_orders, and a win_back_recommendation string. Use this for targeted re-engagement campaigns.

NameTypeReqDescription
store_idstringyesStore ID

No output schema declared.

No examples provided.

customers_segment ~58

RFM (Recency, Frequency, Monetary) customer segmentation. Categorizes customers into segments: Champions, Loyal, Potential, At Risk, New, Hibernating, Lost — with actionable recommendations.

NameTypeReqDescription
store_idstringyesStore ID

No output schema declared.

No examples provided.

inventory_forecast ~61

Predict stock depletion dates using moving-average sales velocity. Returns reorder points, safety stock levels, and suggested reorder quantities for each product.

NameTypeReqDescription
product_idstringSpecific product ID (omit for all products)
store_idstringyesStore ID

No output schema declared.

No examples provided.

inventory_status ~92

Snapshot of current stock levels for a connected store. Returns a summary object with total product count, out-of-stock count, low-stock count (≤10 units), plus two arrays: out_of_stock and low_stock — each containing product id, title, sku, quantity, and status. Items are sorted by urgency (lowest quantity first). Read-only and idempotent.

NameTypeReqDescription
store_idstringyesStore ID

No output schema declared.

No examples provided.

order_anomalies ~100

Statistical anomaly detection on recent orders. Flags high-value orders (>3σ from mean), velocity spikes (customer ordering unusually fast), unusual quantities, off-hours purchases (2am-5am), and new-customer high-value orders. Returns an array of anomalies with order_id, anomaly_type, severity (low/medium/high), reason, and recommended_action. Useful for fraud detection and revenue spike investigation.

NameTypeReqDescription
store_idstringyesStore ID

No output schema declared.

No examples provided.

pricing_analyze ~108

Analyze pricing across products with margin calculation, sales velocity, and rule-based price optimization suggestions. Returns an array where each element contains product_title, current_price, cost, margin_percent, daily_units_sold, revenue_per_day, suggested_price (or null if no change recommended), and suggestion_reason. Pass product_id to scope to a single product, omit for full catalog.

NameTypeReqDescription
product_idstringSpecific product ID (omit for all)
store_idstringyesStore ID

No output schema declared.

No examples provided.

pricing_optimize ~89

Filtered pricing recommendations — only products where a price change is suggested. Returns a summary with total_suggestions count and an optimizations array (product, current_price, suggested_price, change_percent, reason, daily_revenue), sorted by absolute change_percent (biggest moves first). Use this instead of pricing_analyze when you only want actionable changes.

NameTypeReqDescription
store_idstringyesStore ID

No output schema declared.

No examples provided.

product_performance ~73

Product performance report with ABC analysis. Category A = top 80% revenue, B = next 15%, C = bottom 5%. Includes trends, margins, and daily sales velocity.

NameTypeReqDescription
period_daysintegerAnalysis period in days (default 30)
store_idstringyesStore ID

No output schema declared.

No examples provided.

report_daily ~59

Daily operational report: orders, revenue, top products, new vs returning customers, low stock alerts, and anomaly count.

NameTypeReqDescription
datestringDate in YYYY-MM-DD format (defaults to today)
store_idstringyesStore ID

No output schema declared.

No examples provided.

report_weekly ~42

Weekly trend report: revenue/order changes vs previous week, customer segment distribution, trending products, and AI-generated insights.

NameTypeReqDescription
store_idstringyesStore ID

No output schema declared.

No examples provided.

store_connect ~238

Manage Shopify or WooCommerce store connections. action="connect" adds a new store and performs an initial sync of products, orders, and customers; action="sync" refreshes cached data for an existing store; action="list" returns all connected stores with their sync counts. Returns a JSON payload with store metadata (id, name, platform, url, counts, last_sync) — credentials are never returned.

NameTypeReqDescription
actionstringyesconnect = add new store, sync = refresh existing store, list = show all stores
api_keystringPlatform API access token (required for connect)
api_secretstringPlatform API secret — REQUIRED for woocommerce, ignored for shopify
namestringHuman-readable store name (required for connect, e.g. "My Shop")
platformstring"shopify" or "woocommerce" (required for connect)
store_idstringExisting store UUID (required for sync)
urlstringStore base URL starting with https:// (required for connect, e.g. "https://myshop.myshopify.com")

No output schema declared.

No examples provided.

store_demo_seed ~131

Create a realistic demo store populated with 20 products, 40 customers across 6 archetype buckets (champions, loyal, new, at-risk, hibernating, one-off), and 150+ orders spanning the last 6 months. Use this to explore ShopOps without real Shopify or WooCommerce credentials — every tool (inventory_status, customers_segment, order_anomalies, report_weekly, etc.) will return meaningful output on the returned store_id. Safe to call multiple times; each call creates a new demo store with a unique ID. Returns the store_id plus product/customer/order counts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the io.github.enzoemir1/shopops-mcp server?

io.github.enzoemir1/shopops-mcp is listed in the public MCP registry as io.github.enzoemir1/shopops-mcp. AI e-commerce operations. Inventory, pricing, segmentation, and analytics. This page covers its npm package (shopops-mcp-server).

Is the io.github.enzoemir1/shopops-mcp server safe to use?

io.github.enzoemir1/shopops-mcp scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.enzoemir1/shopops-mcp server expose?

io.github.enzoemir1/shopops-mcp exposes 12 tools: store_connect, store_demo_seed, inventory_status, inventory_forecast, pricing_analyze, and 7 more. Their descriptions and schemas cost roughly 1,146 tokens of context every time the server is loaded.

Is the io.github.enzoemir1/shopops-mcp server still maintained?

io.github.enzoemir1/shopops-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.enzoemir1/shopops-mcp server under?

io.github.enzoemir1/shopops-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.