# io.github.tmill313/shopbuddy (npm · shopbuddy)

Safe Shopify theme changes for AI agents: staging, validation, visual review, approval, rollback.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `getshopbuddy.vercel.app`: 38/100, [markdown](https://verifymcp.io/servers/tmill313-shopbuddy/api-mcp.md), [page](https://verifymcp.io/servers/tmill313-shopbuddy/api-mcp)
- npm · `shopbuddy`: 75/100 (this document), [markdown](https://verifymcp.io/servers/tmill313-shopbuddy/shopbuddy.md), [page](https://verifymcp.io/servers/tmill313-shopbuddy/shopbuddy)

## Channel facts

- Registry: `npm`
- Package: `shopbuddy`
- Version: `0.3.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 42 of 142 dependencies flagged as unhealthy (2 deprecated).
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (UNLICENSED) isn't a recognized OSI-approved license.
  - Actively maintained (last published 17 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 803 tokens (~73/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add tmill313-shopbuddy -- npx -y shopbuddy
```

### Cursor

```json
{
  "mcpServers": {
    "tmill313-shopbuddy": {
      "command": "npx",
      "args": [
        "-y",
        "shopbuddy"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tmill313-shopbuddy": {
      "command": "npx",
      "args": [
        "-y",
        "shopbuddy"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add tmill313-shopbuddy -- npx -y shopbuddy
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tmill313-shopbuddy": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "shopbuddy"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tmill313-shopbuddy --command npx --arg -y --arg shopbuddy
```

### Hermes

```yaml
mcp_servers:
  tmill313-shopbuddy:
    command: "npx"
    args: ["-y", "shopbuddy"]
```

### Netclaw

```json
{
  "McpServers": {
    "tmill313-shopbuddy": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "shopbuddy"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add tmill313-shopbuddy -t stdio -c npx -a -y shopbuddy
```

### Other

```json
{
  "mcpServers": {
    "tmill313-shopbuddy": {
      "command": "npx",
      "args": [
        "-y",
        "shopbuddy"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 75, +1)

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

### 2026-09-16 (score 74, +1)

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

### 2026-09-14 (score 73, +1)

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

### 2026-09-12 (score 72, +1)

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

### 2026-09-10 (score 71, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-02 (score 67)

First indexed and scored.

## MCP tools (11)

### `shopbuddy_login` (~63 tokens)

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.

Input parameters:

- `apiUrl` (string): Platform URL; defaults to the configured one

### `shopbuddy_list_stores` (~44 tokens)

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).

### `shopbuddy_connect_store` (~34 tokens)

Opens the browser page where the user connects a Shopify store. The Theme Access password must be entered there by the human.

### `shopbuddy_start_change` (~154 tokens)

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.

Input parameters:

- `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, required): Store domain or id from shopbuddy_list_stores
- `title` (string, required): Short title, e.g. 'Sticky add to cart on mobile'

### `shopbuddy_pull` (~34 tokens)

Re-download the staging theme into the workspace (resets local edits to the server baseline).

Input parameters:

- `workspace` (string)

### `shopbuddy_status` (~38 tokens)

Change request status plus local files added/modified/deleted vs the baseline, and whether they are pushed yet.

Input parameters:

- `workspace` (string)

### `shopbuddy_validate` (~38 tokens)

Run Shopify Theme Check and JSON checks on the workspace, scoped to changed files. Fix every error before pushing.

Input parameters:

- `workspace` (string)

### `shopbuddy_push_preview` (~67 tokens)

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.

Input parameters:

- `message` (string, required): One-line summary of what changed
- `workspace` (string)

### `shopbuddy_submit` (~61 tokens)

Mark the latest pushed revision ready for human review (pushes first if there are unpushed changes). Share the returned reviewUrl with the user.

Input parameters:

- `message` (string, required): What changed and why, for the reviewer
- `workspace` (string)

### `shopbuddy_review` (~38 tokens)

Full detail of the change request: revisions, files with diffs, validation, screenshots, approval, deployments.

Input parameters:

- `workspace` (string)

### `shopbuddy_set_preview_pages` (~53 tokens)

Set which storefront paths get screenshotted for this change (e.g. ['/', '/products/handle']). Applies to the next push.

Input parameters:

- `pages` (array, required)
- `workspace` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/tmill313-shopbuddy/shopbuddy#diagnostics

## Score history

- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 74
- 2026-09-17: 74
- 2026-09-16: 74
- 2026-09-15: 73
- 2026-09-14: 73
- 2026-09-13: 72
- 2026-09-12: 72
- 2026-09-11: 71
- 2026-09-10: 71
- 2026-09-09: 67
- 2026-09-08: 67
- 2026-09-07: 67
- 2026-09-06: 67
- 2026-09-05: 67
- 2026-09-04: 67
- 2026-09-03: 67
- 2026-09-02: 67

## Common questions

### 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 75 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.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 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.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.

## Links

- npm package: https://www.npmjs.com/package/shopbuddy
- Socket report: https://socket.dev/npm/package/shopbuddy
- Repository: https://github.com/tmill313/shopbuddy-plugin
- Website: https://getshopbuddy.vercel.app/
- Changelog RSS feed: https://verifymcp.io/servers/tmill313-shopbuddy/shopbuddy.xml
- Changelog JSON feed: https://verifymcp.io/servers/tmill313-shopbuddy/shopbuddy.json
- HTML version of this page: https://verifymcp.io/servers/tmill313-shopbuddy/shopbuddy