io.github.dragnoir/shopify-theme-inspector
NPM · SHOPIFY-THEME-INSPECTOR-MCP · SCANNED SEP 20
Profile Shopify Liquid performance, find slow theme code, and explain fixes in plain language.
Available components
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
- A known CVE affects extract-zip, but no fixed version has been published, so there is nothing to upgrade to. View diagnostics → Partial
- No install/post-install scripts declared.Pass
- 59 of 192 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 67 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1335 tokens (~83/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "logout" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 17 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
How do I install the io.github.dragnoir/shopify-theme-inspector MCP server?
io.github.dragnoir/shopify-theme-inspector runs locally as an npm package, launched with npx -y shopify-theme-inspector-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · shopify-theme-inspector-mcp
claude mcp add dragnoir-shopify-theme-inspector -- npx -y shopify-theme-inspector-mcp
{
"mcpServers": {
"dragnoir-shopify-theme-inspector": {
"command": "npx",
"args": [
"-y",
"shopify-theme-inspector-mcp"
]
}
}
} {
"servers": {
"dragnoir-shopify-theme-inspector": {
"command": "npx",
"args": [
"-y",
"shopify-theme-inspector-mcp"
]
}
}
} codex mcp add dragnoir-shopify-theme-inspector -- npx -y shopify-theme-inspector-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dragnoir-shopify-theme-inspector": {
"type": "local",
"command": [
"npx",
"-y",
"shopify-theme-inspector-mcp"
],
"enabled": true
}
}
} openclaw mcp add dragnoir-shopify-theme-inspector --command npx --arg -y --arg shopify-theme-inspector-mcp
mcp_servers:
dragnoir-shopify-theme-inspector:
command: "npx"
args: ["-y", "shopify-theme-inspector-mcp"] {
"McpServers": {
"dragnoir-shopify-theme-inspector": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"shopify-theme-inspector-mcp"
]
}
}
} assistant mcp add dragnoir-shopify-theme-inspector -t stdio -c npx -a -y shopify-theme-inspector-mcp
{
"mcpServers": {
"dragnoir-shopify-theme-inspector": {
"command": "npx",
"args": [
"-y",
"shopify-theme-inspector-mcp"
]
}
}
} 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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 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.
- 15 Sept 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.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
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/shopify-theme-inspector-mcp@0.5.1
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 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-7pqw-9j4j-h8q3 | CVE-2026-19693 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H | no |
| GHSA-jmr9-qjv8-65gv | CVE-2026-56876 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 192 packages
| Packages resolved | 192 |
|---|---|
| Deprecated | 1 |
| Stale | 58 |
| 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 →
analyze_liquid_file ~99
Statically analyze a specific Liquid file for performance anti-patterns. Requires legacy cookie authentication (use 'login_legacy' tool).
| Name | Type | Req | Description |
|---|---|---|---|
| fileName | string | – | Specific file to analyze (e.g., 'layout/theme.liquid'). If omitted, analyzes layout/theme.liquid. |
| storeUrl | string | yes | The Shopify store URL |
| themeId | number | – | Theme ID to analyze. Defaults to the live (main) theme. |
No output schema declared.
No examples provided.
batch_profile ~90
Profile multiple pages on the same store in a single call. Returns a summary comparison of all pages sorted by render time. Useful for finding the slowest pages on a site. Maximum 10 pages per call.
| Name | Type | Req | Description |
|---|---|---|---|
| pagePaths | array | yes | Array of page paths to profile (e.g., ['/', '/collections/all', '/products/my-product']) |
| storeUrl | string | yes | The Shopify store URL |
No output schema declared.
No examples provided.
compare_pages ~99
Profile two pages on the same store and compare their performance side-by-side. Shows differences in render time, template breakdown, and recommendations. Great for A/B testing template changes or comparing product vs collection page performance.
| Name | Type | Req | Description |
|---|---|---|---|
| pagePathA | string | yes | First page path (e.g., '/' or '/products/my-product') |
| pagePathB | string | yes | Second page path to compare against |
| storeUrl | string | yes | The Shopify store URL |
No output schema declared.
No examples provided.
complete_login_in_chrome ~75
Complete a login_in_chrome flow using the full final chromiumapp.org callback URL copied from Chrome's address bar.
| Name | Type | Req | Description |
|---|---|---|---|
| callbackUrl | string | yes | The full final URL from Chrome's address bar, including code and state |
| storeUrl | string | yes | The same Shopify store URL used with login_in_chrome |
No output schema declared.
No examples provided.
export_profile ~141
Profile a page and export the results in a specified format. Supported formats: 'speedscope' (JSON for speedscope.app visualization), 'csv' (spreadsheet-friendly), 'markdown' (shareable report with tables, recommendations, and severity badges). Can save to a file or return inline.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | Export format: 'speedscope', 'csv', or 'markdown' |
| outputPath | string | – | Optional file path to save the export. If omitted, returns content inline. |
| pagePath | string | – | The page path to profile (defaults to '/') |
| storeUrl | string | yes | The Shopify store URL |
No output schema declared.
No examples provided.
find_slow_templates ~73
Identify Liquid templates and sections that are taking longer than a specified threshold to render. Requires OAuth2 authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| pagePath | string | – | The page path to profile |
| storeUrl | string | yes | The Shopify store URL |
| thresholdMs | number | – | Threshold in milliseconds. Defaults to 50ms. |
No output schema declared.
No examples provided.
get_auth_status ~53
Check authentication status. Shows both OAuth2 (for profiling) and legacy (for Admin API) authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| storeUrl | string | – | Optional: specific store URL to check. If omitted, lists all authenticated stores. |
No output schema declared.
No examples provided.
get_bottlenecks ~88
Profile a page and automatically detect performance anti-patterns. Returns prioritized recommendations with severity ratings (critical/warning/info), specific file/line locations, measured impact, and concrete fix suggestions. This is the BEST tool for identifying what to optimize.
| Name | Type | Req | Description |
|---|---|---|---|
| pagePath | string | – | The page path to analyze (defaults to '/') |
| storeUrl | string | yes | The Shopify store URL |
No output schema declared.
No examples provided.
get_profile_history ~120
View profiling history and performance trends for a store. Shows how render times have changed over time. Every profiling call is automatically saved to history. Use this to track the impact of optimizations.
| Name | Type | Req | Description |
|---|---|---|---|
| clearHistory | boolean | – | Set to true to clear history for this store/page. |
| limit | number | – | Maximum number of history entries to return (default: 10) |
| pagePath | string | – | Filter history to a specific page path. If omitted, lists all profiled pages. |
| storeUrl | string | yes | The Shopify store URL |
No output schema declared.
No examples provided.
get_profile_summary ~67
Profile a Shopify store page and return a structured performance summary with top slow nodes and template breakdown. More readable than raw profile_page data. Requires OAuth2 authentication first.
| Name | Type | Req | Description |
|---|---|---|---|
| pagePath | string | – | The page path to profile |
| storeUrl | string | yes | The Shopify store URL |
No output schema declared.
No examples provided.
health_check ~20
Check if the Shopify Theme Inspector MCP server is running correctly
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
login ~67
Authenticate with Shopify via OAuth2 (same method as the Chrome Theme Inspector extension). Opens a browser for you to log in. This provides full flame graph profiling data.
| Name | Type | Req | Description |
|---|---|---|---|
| storeUrl | string | yes | The Shopify store URL (e.g., onebed.com.au or mystore.myshopify.com) |
No output schema declared.
No examples provided.
login_in_chrome ~54
Start Shopify OAuth in the user's existing Chrome profile without closing Chrome. After authorization, copy the full final callback URL and pass it to complete_login_in_chrome.
| Name | Type | Req | Description |
|---|---|---|---|
| storeUrl | string | yes | The Shopify store URL |
No output schema declared.
No examples provided.
login_legacy ~71
Legacy cookie-based Shopify login. Opens browser for manual login. Required for 'analyze_liquid_file' tool which needs Admin API access. Use 'login' (OAuth2) for profiling tools.
| Name | Type | Req | Description |
|---|---|---|---|
| storeUrl | string | yes | The Shopify store URL (e.g., mystore.myshopify.com) |
No output schema declared.
No examples provided.
logout ~38
Remove saved authentication (both OAuth2 and legacy sessions) for a Shopify store
| Name | Type | Req | Description |
|---|---|---|---|
| storeUrl | string | yes | The Shopify store URL to logout from |
No output schema declared.
No examples provided.
profile_page ~96
Profile a Shopify store page to analyze Liquid template rendering performance. Returns FULL flame graph profiling data (same as Chrome extension). Requires OAuth2 authentication first (use the 'login' tool).
| Name | Type | Req | Description |
|---|---|---|---|
| pagePath | string | – | The page path to profile (e.g., /products/example). Defaults to homepage '/' |
| storeUrl | string | yes | The Shopify store URL (e.g., onebed.com.au or mystore.myshopify.com) |
No output schema declared.
No examples provided.
What is the io.github.dragnoir/shopify-theme-inspector MCP server?
io.github.dragnoir/shopify-theme-inspector is an MCP server listed in the public MCP registry as io.github.dragnoir/shopify-theme-inspector. Profile Shopify Liquid performance, find slow theme code, and explain fixes in plain language. This page covers its npm package (shopify-theme-inspector-mcp).
Is the io.github.dragnoir/shopify-theme-inspector MCP server safe to use?
io.github.dragnoir/shopify-theme-inspector scores 81 out of 100 on VerifyMCP. We recorded 2 known advisories against 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.dragnoir/shopify-theme-inspector MCP server expose?
io.github.dragnoir/shopify-theme-inspector exposes 16 tools: health_check, login, login_in_chrome, complete_login_in_chrome, login_legacy, and 11 more. Their descriptions and schemas cost roughly 1,251 tokens of context every time the server is loaded.
Is the io.github.dragnoir/shopify-theme-inspector MCP server still maintained?
io.github.dragnoir/shopify-theme-inspector 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.dragnoir/shopify-theme-inspector MCP server under?
io.github.dragnoir/shopify-theme-inspector declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.