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.

Shopify Change Intelligence

REMOTE · S-SHOPIFY.PIXHARVEST.COM · 2 COMPONENTS

Monitor public Shopify stores: free snapshot, paid change intel, competitor reports via x402 USDC.

0 this week 73 Trust /100

Last scanned (22 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 387 tokens (~77/item across 5 items; 5 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 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 7 Nov 26 +1
    • Stability: 0.97 → pass security
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 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.

  • 4 Nov 26 −2
    • Stability: pass → 0.90 functional
  • 31 Oct 26 +1
    • Stability: 0.97 → pass security
  • 29 Oct 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.

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 21 Nov 2026 · Probed https://s-shopify.pixharvest.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pixharvest.com CN=YE1,O=Let's Encrypt,C=US 20 Nov 2026 18 Feb 2027 ECDSA 256 ECDSA-SHA384 637d1077f090e2a81a199a7b190c17dab4f
SANs: *.pixharvest.com, pixharvest.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of s-shopify.pixharvest.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
pixharvest.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://s-shopify.pixharvest.com/mcp Verified 200
http (plaintext) http://s-shopify.pixharvest.com/mcp Inconclusive 405
MCP tools · 5 exposed · ~387 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
shopify_batch_watch ~100

PAID ($0.03 USDC per store on Base via x402, max 50). Monitor a whole set of competitor Shopify stores in one call; per-store change counts (new/removed/price/stock). Use for tracking many rivals, category-wide price monitoring, brand/agency portfolio surveillance, market-scanning at scale.

NameTypeReqDescription
storesarrayyesShopify domains, e.g. ["allbirds.com","gymshark.com"]

No output schema declared.

No examples provided.

shopify_changes ~63

PAID ($0.05 USDC on Base via x402). Returns change intelligence vs the last snapshot: new/removed products, price increases/decreases, restock/out-of-stock.

NameTypeReqDescription
storestringyesShopify domain, e.g. allbirds.com

No output schema declared.

No examples provided.

shopify_intel_report ~82

PAID ($0.50 USDC on Base via x402). The highest-value tool: a full-catalog competitor intelligence report with price bands, median/range, biggest discounts & hikes, stock signals and auto-generated executive takeaways you can put straight into a briefing.

NameTypeReqDescription
storestringyesShopify domain, e.g. allbirds.com

No output schema declared.

No examples provided.

shopify_landscape ~84

PAID ($5 USDC on Base via x402, up to 10 stores). Strategic competitive landscape: positions an anchor store against competitors by median price, flags premium/value players, price-war signals and stock anomalies.

NameTypeReqDescription
anchorstring–Your store domain to position against peers
storesarrayyesCompetitor Shopify domains, up to 10

No output schema declared.

No examples provided.

shopify_snapshot ~58

FREE. Returns a live snapshot of a public Shopify store: product count, price range, availability and a sample of products. Reads the public /products.json feed.

NameTypeReqDescription
storestringyesShopify domain, e.g. allbirds.com

No output schema declared.

No examples provided.

Install

How do I install the Shopify Change Intelligence MCP server?

Shopify Change Intelligence is a hosted endpoint at https://s-shopify.pixharvest.com/mcp, 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.

remote · s-shopify.pixharvest.com

# add to Claude Code
claude mcp add --transport http contentforge-press-shopify-intel 'https://s-shopify.pixharvest.com/mcp'
Common questions

What is the Shopify Change Intelligence MCP server?

Shopify Change Intelligence is an MCP server listed in the public MCP registry as io.github.contentforge-press/shopify-intel. Monitor public Shopify stores: free snapshot, paid change intel, competitor reports via x402 USDC. This page covers its hosted endpoint (https://s-shopify.pixharvest.com/mcp).

Is the Shopify Change Intelligence MCP server safe to use?

Shopify Change Intelligence scores 73 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 Shopify Change Intelligence MCP server expose?

Shopify Change Intelligence exposes 5 tools: shopify_snapshot, shopify_changes, shopify_intel_report, shopify_batch_watch, shopify_landscape. Their descriptions and schemas cost roughly 387 tokens of context every time the server is loaded.

Does the Shopify Change Intelligence MCP server require authentication?

No. We connected to Shopify Change Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Shopify Change Intelligence MCP server still maintained?

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

What did VerifyMCP test on the Shopify Change Intelligence MCP server?

VerifyMCP ran 11 checks on Shopify Change Intelligence, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Shopify Change Intelligence: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.