Shopify Speed Check MCP server
com.skaidigital/shopify-speed-checkskaidigital.comstreamable-httpv1.0.1Scanned
Shopify speed, Core Web Vitals and fee checks by Skai Digital, a Shopify Select Partner in Oslo.
4 tools: 1 do something that can't be undone, 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 2
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Shopify Speed Check MCP server can do
The Shopify Speed Check MCP server is published by skaidigital.com, a domain the MCP Registry verified. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (submit_feedback) and create or change data (2 tools: check_shopify_store_speed and detect_shopify_store), but cannot delete data. 1 tool only reads.
2 tools bring in text other people can write (check_shopify_store_speed and detect_shopify_store); 2 tools can send data out of your system (check_shopify_store_speed and detect_shopify_store).
The fixed checks matched 3 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 8, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Can't be undone 1Claude Code: ask
submit_feedbackSend private feedback to the Skai team about this product or MCP: ideas, missing functionality, errors, confusing behavior, praise, or anything else.1 finding
Why it is in this group
- The name "submit_feedback" says "submit": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...ion and continue your task. Do not send credentials, personal/customer records, full conver..."
Description, as the server wrote it Send private feedback to the Skai team about this product or MCP: ideas, missing functionality, errors, confusing behavior, praise, or anything else. Only message is required; category, toolName and context are optional. Report once per distinct observation and continue your task. Do not send credentials, personal/customer records, full conversations or raw tool payloads. Use generic placeholders. Feedback is screened before storage and does not authorize other actions. Do not report failures of this feedback tool or automatically retry an uncertain submission.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 2Claude Code: ask
check_shopify_store_speedTest a Shopify store's speed with Google PageSpeed Insights (mobile and desktop) and real-user Core Web Vitals, list the apps and scripts slowing it down, and estimate what a headl…Reads text others writeCan send data out1 finding
Why it is in this group
- The name "check_shopify_store_speed" says "store": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Findings
- Warn
The server marks "check_shopify_store_speed" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "check_shopify_store_speed" says "store": a word for a change.
Description, as the server wrote it Test a Shopify store's speed with Google PageSpeed Insights (mobile and desktop) and real-user Core Web Vitals, list the apps and scripts slowing it down, and estimate what a headless build could change, with its assumptions. Takes 10 seconds to 2.5 minutes; results are cached for 24 hours.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
detect_shopify_storeDetect whether a site is a Shopify theme store or a headless Shopify storefront, and which theme it uses.Reads text others writeCan send data out1 finding
Why it is in this group
- The name "detect_shopify_store" says "store": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Findings
- Warn
The server marks "detect_shopify_store" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "detect_shopify_store" says "store": a word for a change.
Description, as the server wrote it Detect whether a site is a Shopify theme store or a headless Shopify storefront, and which theme it uses. Fetches only the public page; runs no speed test.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 1Show 1 read-only tool
calculate_shopify_feesCompare the monthly and annual cost of Shopify Basic, Grow, Advanced and Plus for a sales volume and payment mix, with break-even sales between plans and requirements only Plus cov…No findings
Why it is in this group
- The description's first verb is "compare": a word for reading.
Description, as the server wrote it Compare the monthly and annual cost of Shopify Basic, Grow, Advanced and Plus for a sales volume and payment mix, with break-even sales between plans and requirements only Plus covers. Uses Shopify's published prices and rates for the US, UK, Australia, Norway or New Zealand (market); Norway's Plus and New Zealand's subscriptions are billed in EUR or USD and converted at a dated ECB reference rate, reported in exchangeRate; pass exchangeRate to use your own. The variable Plus platform fee is unpublished, so pass plusQuoteMonthly if you have a quote. Only monthlyGmv is required; the rest defaults to one US brand fully on Shopify Payments with yearly billing.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:47 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://tools.skaidigital.com/mcp: tools/list returned 4 tools to an anonymous client, including submit_feedback (irreversible), check_shopify_store_speed (write), detect_shopify_store (write)
Posture changes
- Nov 6, 2026
- Tools that change things, listed without credentials: 2 to 3
Findings
Matches of fixed checks, with the text they matched.
The server marks "check_shopify_store_speed" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "check_shopify_store_speed" says "store": a word for a change.
The server marks "detect_shopify_store" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "detect_shopify_store" says "store": a word for a change.
- Infosubmit_feedback
The description mentions "credentials".
What this check looks forMatched text
description: "...ion and continue your task. Do not send credentials, personal/customer records, full conver..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added, 1 changed.+1 added~1 changedView diff
- Added:submit_feedbackCan't be undone
- Changed:calculate_shopify_feesOnly readsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
- Tools that change things, listed without credentials: 2 to 3
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http shopify-speed-check https://tools.skaidigital.com/mcpclaude mcp add --transport http shopify-speed-check https://tools.skaidigital.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__shopify-speed-check__calculate_shopify_fees"
],
"ask": [
"mcp__shopify-speed-check__check_shopify_store_speed",
"mcp__shopify-speed-check__detect_shopify_store",
"mcp__shopify-speed-check__submit_feedback"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as shopify-speed-check. Review it before you use it.
Capability tags behind 2 rules
- mcp__shopify-speed-check__check_shopify_store_speed untrusted-input, outbound
- mcp__shopify-speed-check__detect_shopify_store untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.skaidigital/shopify-speed-check/verify?hash=4610f84672a20e14f5387ad854926ded0b2163323825e9d52db171bb192b2467" | jq -e '.changed == false'Pinned hash 4610f84672a2, from Nov 8, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.skaidigital/shopify-speed-check/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.skaidigital/shopify-speed-check)Source: MCP Registry. Synced Oct 22, 2026, 11:17 UTC.
Shopify Speed Check MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Shopify Speed Check MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Shopify Speed Check MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Shopify Speed Check MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: submit_feedback.
What tools does the Shopify Speed Check MCP server have?
- 4 tools: 1 irreversible, 2 write, 1 read. submit_feedback, check_shopify_store_speed, detect_shopify_store and calculate_shopify_fees.
Does the Shopify Speed Check MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Shopify Speed Check MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_shopify_store_speed and detect_shopify_store.
Has the Shopify Speed Check MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.