# HasData Shopify (remote · mcp.hasdata.com)

The public product catalogue and collections of any Shopify storefront, as structured JSON.

- Trust score: 85/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `mcp.hasdata.com`: 85/100 (this document), [markdown](https://verifymcp.io/servers/com-hasdata-shopify/mcp.md), [page](https://verifymcp.io/servers/com-hasdata-shopify/mcp)
- npm · `@hasdata/shopify-mcp`: 49/100, [markdown](https://verifymcp.io/servers/com-hasdata-shopify/hasdata-shopify-mcp.md), [page](https://verifymcp.io/servers/com-hasdata-shopify/hasdata-shopify-mcp)
- pypi · `hasdata-shopify-mcp`: 34/100, [markdown](https://verifymcp.io/servers/com-hasdata-shopify/hasdata-shopify-mcp-2.md), [page](https://verifymcp.io/servers/com-hasdata-shopify/hasdata-shopify-mcp-2)

## Channel facts

- Endpoint: `https://mcp.hasdata.com/mcp?apis=shopify`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-17.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 444 tokens (~222/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 HasData Shopify MCP server?

HasData Shopify is a hosted endpoint at https://mcp.hasdata.com/mcp?apis=shopify, so there is nothing to install locally. 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 --transport http com-hasdata-shopify 'https://mcp.hasdata.com/mcp?apis=shopify'
```

### Cursor

```json
{
  "mcpServers": {
    "com-hasdata-shopify": {
      "url": "https://mcp.hasdata.com/mcp?apis=shopify"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-hasdata-shopify": {
      "type": "http",
      "url": "https://mcp.hasdata.com/mcp?apis=shopify"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-hasdata-shopify]
url = "https://mcp.hasdata.com/mcp?apis=shopify"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hasdata-shopify": {
      "type": "remote",
      "url": "https://mcp.hasdata.com/mcp?apis=shopify",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-hasdata-shopify --url 'https://mcp.hasdata.com/mcp?apis=shopify' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-hasdata-shopify:
    url: "https://mcp.hasdata.com/mcp?apis=shopify"
```

### Netclaw

```json
{
  "McpServers": {
    "com-hasdata-shopify": {
      "Transport": "http",
      "Url": "https://mcp.hasdata.com/mcp?apis=shopify"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-hasdata-shopify -t streamable-http -u 'https://mcp.hasdata.com/mcp?apis=shopify'
```

### Other

```json
{
  "mcpServers": {
    "com-hasdata-shopify": {
      "type": "http",
      "url": "https://mcp.hasdata.com/mcp?apis=shopify"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-17 (score 85, +1)

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

### 2026-10-15 (score 84, +1)

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

### 2026-10-13 (score 83, +1)

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

### 2026-10-11 (score 82, +1)

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

### 2026-10-10 (score 81, +1)

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

### 2026-10-07 (score 80, +41)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-09-28 (score 39, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 39, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (2)

### `hasdata_shopify_collections_getCollections` (~161 tokens)

shopify_collections: GET /

Get Shopify Store Collections

Lists collections from any public Shopify storefront URL with limit (up to 250) and page pagination. Returns each collection's id, title, handle, description, image, and timestamps. Use the returned handles as input to the Shopify Products endpoint to enumerate category-specific catalogs, or to map a competitor's merchandising taxonomy and track collection changes over time.

Input parameters:

- `limit` (number): The maximum number of collections to retrieve. Must be between 1 and 250.
- `page` (number): The page number of the results to retrieve. Must be a positive integer.
- `url` (string, required): The URL of the Shopify store. For example, 'https://b2bdemoexperience.myshopify.com'.

### `hasdata_shopify_products_getProducts` (~210 tokens)

shopify_products: GET /

Get Shopify Store Products

Pulls products from any public Shopify storefront URL, optionally filtered by a collection handle, with limit (up to 250) and page pagination. Returns product id, title, handle, vendor, product_type, tags, body_html, images, variants with prices/SKUs/inventory status, and timestamps. Use for competitive price monitoring, catalog mirroring, availability tracking, building product datasets for comparison shopping, or feeding structured SKU data into downstream analytics and dropshipping pipelines.

Input parameters:

- `collection` (string): The handle of the collection to filter the products. Provide the collection handle as a string.
- `limit` (number): The maximum number of products to retrieve. Must be between 1 and 250.
- `page` (number): The page number of the results to retrieve. Must be a positive integer.
- `url` (string, required): The URL of the Shopify store. For example, 'https://b2bdemoexperience.myshopify.com'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-hasdata-shopify/mcp#diagnostics

## Score history

- 2026-10-17: 85
- 2026-10-16: 84
- 2026-10-15: 84
- 2026-10-14: 83
- 2026-10-13: 83
- 2026-10-12: 82
- 2026-10-11: 82
- 2026-10-10: 81
- 2026-10-07: 80
- 2026-10-05: 39
- 2026-10-04: 39
- 2026-10-03: 39
- 2026-10-02: 39
- 2026-10-01: 39
- 2026-09-30: 39
- 2026-09-29: 39
- 2026-09-28: 39
- 2026-09-27: 39
- 2026-09-26: 39
- 2026-09-25: 39
- 2026-09-24: 39
- 2026-09-23: 39
- 2026-09-22: 39

## Common questions

### What is the HasData Shopify MCP server?

HasData Shopify is an MCP server listed in the public MCP registry as com.hasdata/shopify. The public product catalogue and collections of any Shopify storefront, as structured JSON. This page covers its hosted endpoint (https://mcp.hasdata.com/mcp?apis=shopify).

### Is the HasData Shopify MCP server safe to use?

HasData Shopify scores 85 out of 100 on VerifyMCP. 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 HasData Shopify MCP server expose?

HasData Shopify exposes 2 tools: hasdata_shopify_collections_getCollections, hasdata_shopify_products_getProducts. Their descriptions and schemas cost roughly 371 tokens of context every time the server is loaded.

### Does the HasData Shopify MCP server require authentication?

Yes. HasData Shopify asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the HasData Shopify MCP server still maintained?

HasData Shopify is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.hasdata.com/mcp?apis=shopify
- Authorisation metadata: https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/HasData/shopify-mcp
- Website: https://hasdata.com/apis/shopify-api
- Changelog RSS feed: https://verifymcp.io/servers/com-hasdata-shopify/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hasdata-shopify/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-hasdata-shopify/mcp