io.github.tmill313/shopbuddy
NPM · SHOPBUDDY · 2 COMPONENTS
Safe Shopify theme changes for AI agents: staging, validation, visual review, approval, rollback.
Available components
Last scanned (22 hours ago)
Scores higher than 65% of npm servers
Category E-commerce
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 Security93
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects minimatch 10.2.6, reached via @shopify/theme-check-node > @shopify/theme-check-common > minimatch. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 41 of 139 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: the license (UNLICENSED) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 62 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 803 tokens (~73/item across 11 items; 11 tools + 0 resources), lean.Pass
- 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 Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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.
- 31 Oct 26 −1
- CVE-2026-118764 affects this package: medium ▼ security
- Known CVEs: pass → fail ▼ security
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed npm/shopbuddy@0.3.0
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-g3hv-75wg-m249 | CVE-2026-118764 | medium | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 139 packages
| Packages resolved | 139 |
|---|---|
| Deprecated | 2 |
| Stale | 40 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
shopbuddy_connect_store ~34
Opens the browser page where the user connects a Shopify store. The Theme Access password must be entered there by the human.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
shopbuddy_list_stores ~44
Connected Shopify stores. If none are connected, returns the URL where the user connects one (their Theme Access password is entered in the browser, never through the agent).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
shopbuddy_login ~63
Sign in to the shopbuddy platform. Opens the user's browser to approve a short code; call again until status is 'approved'. Not needed when SHOPBUDDY_API_KEY is configured.
| Name | Type | Req | Description |
|---|---|---|---|
| apiUrl | string | – | Platform URL; defaults to the configured one |
No output schema declared.
No examples provided.
shopbuddy_pull ~34
Re-download the staging theme into the workspace (resets local edits to the server baseline).
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | – | – |
No output schema declared.
No examples provided.
shopbuddy_push_preview ~67
Upload changed files to the unpublished staging theme, run server-side validation, and queue before/after screenshots. Returns the revision with previewUrl, validation, risk, and any pushError.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | One-line summary of what changed |
| workspace | string | – | – |
No output schema declared.
No examples provided.
shopbuddy_review ~38
Full detail of the change request: revisions, files with diffs, validation, screenshots, approval, deployments.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | – | – |
No output schema declared.
No examples provided.
shopbuddy_set_preview_pages ~53
Set which storefront paths get screenshotted for this change (e.g. ['/', '/products/handle']). Applies to the next push.
| Name | Type | Req | Description |
|---|---|---|---|
| pages | array | yes | – |
| workspace | string | – | – |
No output schema declared.
No examples provided.
shopbuddy_start_change ~154
Create a change request for a store (duplicates the live theme into an unpublished staging theme) and pull the theme into a local workspace directory. Returns the absolute workspace path to edit files in.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Where to create the workspace; defaults to ./shopify-changes/<slug> under the current directory |
| previewPages | array | – | Storefront paths to screenshot, e.g. ['/', '/products/some-handle'] |
| request | string | – | What the merchant asked for, verbatim if possible |
| store | string | yes | Store domain or id from shopbuddy_list_stores |
| title | string | yes | Short title, e.g. 'Sticky add to cart on mobile' |
No output schema declared.
No examples provided.
shopbuddy_status ~38
Change request status plus local files added/modified/deleted vs the baseline, and whether they are pushed yet.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | – | – |
No output schema declared.
No examples provided.
shopbuddy_submit ~61
Mark the latest pushed revision ready for human review (pushes first if there are unpushed changes). Share the returned reviewUrl with the user.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | What changed and why, for the reviewer |
| workspace | string | – | – |
No output schema declared.
No examples provided.
shopbuddy_validate ~38
Run Shopify Theme Check and JSON checks on the workspace, scoped to changed files. Fix every error before pushing.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.tmill313/shopbuddy MCP server?
io.github.tmill313/shopbuddy runs locally as an npm package, launched with npx -y shopbuddy. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · shopbuddy
claude mcp add tmill313-shopbuddy -- npx -y shopbuddy
What is the io.github.tmill313/shopbuddy MCP server?
io.github.tmill313/shopbuddy is an MCP server listed in the public MCP registry as io.github.tmill313/shopbuddy. Safe Shopify theme changes for AI agents: staging, validation, visual review, approval, rollback. This page covers its npm package (shopbuddy).
Is the io.github.tmill313/shopbuddy MCP server safe to use?
io.github.tmill313/shopbuddy scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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 io.github.tmill313/shopbuddy MCP server expose?
io.github.tmill313/shopbuddy exposes 11 tools: shopbuddy_login, shopbuddy_list_stores, shopbuddy_connect_store, shopbuddy_start_change, shopbuddy_pull, and 6 more. Their descriptions and schemas cost roughly 624 tokens of context every time the server is loaded.
Is the io.github.tmill313/shopbuddy MCP server still maintained?
io.github.tmill313/shopbuddy is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.tmill313/shopbuddy MCP server under?
io.github.tmill313/shopbuddy declares the UNLICENSED licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.