Store Canary
REMOTE · MCP.STORECANARY.APP
Free read-only WooCommerce checks: store, SSL, exposure, SEO, speed, products, policies + 3 prompts
Available components
Last scanned (10 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1194 tokens (~149/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
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.
- 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 →
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.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 0
- Tool “check_exposure” rewrote its description, which is the text the model reads security
- Tool “check_policies” rewrote its description, which is the text the model reads security
- Tool “check_products” rewrote its description, which is the text the model reads security
- Tool “check_seo_basics” rewrote its description, which is the text the model reads security
- Tool “check_speed” rewrote its description, which is the text the model reads security
- Tool “check_ssl” rewrote its description, which is the text the model reads security
- Tool “check_store” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “check_exposure” reworded the description of “url” cosmetic
- “check_policies” reworded the description of “url” cosmetic
- “check_products” reworded the description of “url” cosmetic
- “check_seo_basics” reworded the description of “url” cosmetic
- “check_speed” reworded the description of “url” cosmetic
- “check_ssl” reworded the description of “url” cosmetic
- “check_store” reworded the description of “url” cosmetic
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 155 → 109 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “black_friday_audit” functional
- New prompt “checkout_check” functional
- New prompt “explain_finding” functional
- New tool “check_exposure” functional
- New tool “check_policies” functional
- New tool “check_products” functional
- New tool “check_seo_basics” functional
- New tool “check_speed” functional
- New tool “check_ssl” functional
- New tool “explain_finding” functional
- 29 Oct 26 67
First indexed and scored.
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 5 Nov 2026 · Probed https://mcp.storecanary.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=storecanary.app | CN=WE1,O=Google Trust Services,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 5bc47baeeae5a7313720bb6983c0144 |
| SANs: storecanary.app, mcp.storecanary.app, *.mcp.storecanary.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.storecanary.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| storecanary.app. | 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 |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.storecanary.app/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.storecanary.app/mcp | Inconclusive | 405 |
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 →
check_exposure Check what a store exposes publicly ~161
Flag WordPress, WooCommerce, plugin and PHP versions a store shows publicly (generator tags, asset ?ver= values, X-Powered-By), a public /readme.html and a readable /wp-content/debug.log. Log contents are never returned or kept. Read-only: one run of GET requests only; never logs in, adds to cart or submits forms. Nothing is monitored or saved; ongoing checks are Store Canary Pro. A bare hostname is fine; URL paths are ignored and the host's homepage is checked.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The store's public address, for example https://example.com. A bare hostname (example.com) is fine. Any path, query or fragment is ignored: the homepage of the host is checked. |
| Name | Type | Req | Description |
|---|---|---|---|
| auditUrl | string | yes | Full Store Canary audit (plain external link). |
| checkedAt | string | yes | – |
| findings | array | yes | – |
| liteUrl | string | yes | Store Canary Lite on WordPress.org (free). |
| overall | string|null | yes | – |
| proTrialUrl | string | yes | Store Canary Pro 30-day free trial. |
| reportUrl | string | – | Shareable read-only report page. The result is encoded in the link; nothing is stored. |
| status | string | yes | checked = findings below; otherwise no store request was made. |
| summary | string | yes | – |
| url | string|null | yes | Normalized store origin that was checked. |
No examples provided.
check_policies Check a store's policy pages ~135
Check that the homepage links to privacy, terms, shipping and returns/refunds pages, and that each linked page on the same site loads. Read-only: one run of GET requests only; never logs in, adds to cart or submits forms. Nothing is monitored or saved; ongoing checks are Store Canary Pro. A bare hostname is fine; URL paths are ignored and the host's homepage is checked.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The store's public address, for example https://example.com. A bare hostname (example.com) is fine. Any path, query or fragment is ignored: the homepage of the host is checked. |
| Name | Type | Req | Description |
|---|---|---|---|
| auditUrl | string | yes | Full Store Canary audit (plain external link). |
| checkedAt | string | yes | – |
| findings | array | yes | – |
| liteUrl | string | yes | Store Canary Lite on WordPress.org (free). |
| overall | string|null | yes | – |
| proTrialUrl | string | yes | Store Canary Pro 30-day free trial. |
| reportUrl | string | – | Shareable read-only report page. The result is encoded in the link; nothing is stored. |
| status | string | yes | checked = findings below; otherwise no store request was made. |
| summary | string | yes | – |
| url | string|null | yes | Normalized store origin that was checked. |
No examples provided.
check_products Sample a store's products ~133
Read up to 10 published products from the public WooCommerce Store API and flag missing prices, missing images and out-of-stock items. Read-only: one run of GET requests only; never logs in, adds to cart or submits forms. Nothing is monitored or saved; ongoing checks are Store Canary Pro. A bare hostname is fine; URL paths are ignored and the host's homepage is checked.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The store's public address, for example https://example.com. A bare hostname (example.com) is fine. Any path, query or fragment is ignored: the homepage of the host is checked. |
| Name | Type | Req | Description |
|---|---|---|---|
| auditUrl | string | yes | Full Store Canary audit (plain external link). |
| checkedAt | string | yes | – |
| findings | array | yes | – |
| liteUrl | string | yes | Store Canary Lite on WordPress.org (free). |
| overall | string|null | yes | – |
| proTrialUrl | string | yes | Store Canary Pro 30-day free trial. |
| reportUrl | string | – | Shareable read-only report page. The result is encoded in the link; nothing is stored. |
| status | string | yes | checked = findings below; otherwise no store request was made. |
| summary | string | yes | – |
| url | string|null | yes | Normalized store origin that was checked. |
No examples provided.
check_seo_basics Check a store's SEO basics ~142
Check a store's robots.txt (and whether it blocks the whole site), its XML sitemap, the homepage title and meta description, and noindex on the homepage. Read-only: one run of GET requests only; never logs in, adds to cart or submits forms. Nothing is monitored or saved; ongoing checks are Store Canary Pro. A bare hostname is fine; URL paths are ignored and the host's homepage is checked.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The store's public address, for example https://example.com. A bare hostname (example.com) is fine. Any path, query or fragment is ignored: the homepage of the host is checked. |
| Name | Type | Req | Description |
|---|---|---|---|
| auditUrl | string | yes | Full Store Canary audit (plain external link). |
| checkedAt | string | yes | – |
| findings | array | yes | – |
| liteUrl | string | yes | Store Canary Lite on WordPress.org (free). |
| overall | string|null | yes | – |
| proTrialUrl | string | yes | Store Canary Pro 30-day free trial. |
| reportUrl | string | – | Shareable read-only report page. The result is encoded in the link; nothing is stored. |
| status | string | yes | checked = findings below; otherwise no store request was made. |
| summary | string | yes | – |
| url | string|null | yes | Normalized store origin that was checked. |
No examples provided.
check_speed Time a store's key pages ~141
Time one download each of a store's homepage, one product page and the cart from Cloudflare's network. One sample per page, not a lab test or an average. Read-only: one run of GET requests only; never logs in, adds to cart or submits forms. Nothing is monitored or saved; ongoing checks are Store Canary Pro. A bare hostname is fine; URL paths are ignored and the host's homepage is checked.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The store's public address, for example https://example.com. A bare hostname (example.com) is fine. Any path, query or fragment is ignored: the homepage of the host is checked. |
| Name | Type | Req | Description |
|---|---|---|---|
| auditUrl | string | yes | Full Store Canary audit (plain external link). |
| checkedAt | string | yes | – |
| findings | array | yes | – |
| liteUrl | string | yes | Store Canary Lite on WordPress.org (free). |
| overall | string|null | yes | – |
| proTrialUrl | string | yes | Store Canary Pro 30-day free trial. |
| reportUrl | string | – | Shareable read-only report page. The result is encoded in the link; nothing is stored. |
| status | string | yes | checked = findings below; otherwise no store request was made. |
| summary | string | yes | – |
| url | string|null | yes | Normalized store origin that was checked. |
No examples provided.
check_ssl Check a store's HTTPS setup ~154
Check that a store's HTTPS certificate is accepted, http:// permanently redirects to https://, the redirect chain is short and stays on HTTPS, and an HSTS header is set. The exact certificate expiry date isn't visible to an outside fetch. Read-only: one run of GET requests only; never logs in, adds to cart or submits forms. Nothing is monitored or saved; ongoing checks are Store Canary Pro. A bare hostname is fine; URL paths are ignored and the host's homepage is checked.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The store's public address, for example https://example.com. A bare hostname (example.com) is fine. Any path, query or fragment is ignored: the homepage of the host is checked. |
| Name | Type | Req | Description |
|---|---|---|---|
| auditUrl | string | yes | Full Store Canary audit (plain external link). |
| checkedAt | string | yes | – |
| findings | array | yes | – |
| liteUrl | string | yes | Store Canary Lite on WordPress.org (free). |
| overall | string|null | yes | – |
| proTrialUrl | string | yes | Store Canary Pro 30-day free trial. |
| reportUrl | string | – | Shareable read-only report page. The result is encoded in the link; nothing is stored. |
| status | string | yes | checked = findings below; otherwise no store request was made. |
| summary | string | yes | – |
| url | string|null | yes | Normalized store origin that was checked. |
No examples provided.
check_store Check a WooCommerce store ~150
Check a public WooCommerce store from the outside: is it reachable, is HTTPS valid and are redirects sane, is WooCommerce detected, do /cart/ and /checkout/ load, and are payment markers visible on checkout. Read-only: GET requests only, never adds to cart, logs in or submits forms. Returns pass/warn/fail findings plus a link to the full audit. Pass a bare hostname or URL; paths are ignored and the host's homepage is checked.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The store's public address, for example https://example.com. A bare hostname (example.com) is fine. Any path, query or fragment is ignored: the homepage of the host is checked. |
| Name | Type | Req | Description |
|---|---|---|---|
| auditUrl | string | yes | Full Store Canary audit (plain external link). |
| checkedAt | string | yes | – |
| findings | array | yes | – |
| liteUrl | string | yes | Store Canary Lite on WordPress.org (free). |
| overall | string|null | yes | – |
| proTrialUrl | string | yes | Store Canary Pro 30-day free trial. |
| reportUrl | string | – | Shareable read-only report page. The result is encoded in the link; nothing is stored. |
| status | string | yes | checked = findings below; otherwise no store request was made. |
| summary | string | yes | – |
| url | string|null | yes | Normalized store origin that was checked. |
No examples provided.
explain_finding Explain a Store Canary finding ~67
Explain a finding code returned by any Store Canary tool (for example ssl_hsts or exposure_debug_log) in plain words, with a suggested fix. Makes no network requests.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | A finding id from a Store Canary result, for example checkout or seo_noindex. |
| Name | Type | Req | Description |
|---|---|---|---|
| auditUrl | string | yes | Full Store Canary audit (plain external link). |
| code | string | yes | – |
| fix | string|null | yes | – |
| liteUrl | string | yes | Store Canary Lite on WordPress.org (free). |
| meaning | string|null | yes | – |
| proTrialUrl | string | yes | Store Canary Pro 30-day free trial. |
| status | string | yes | – |
| summary | string | yes | – |
| title | string|null | yes | – |
| tool | string|null | yes | The tool that returns this finding. |
No examples provided.
How do I install the Store Canary MCP server?
Store Canary is a hosted endpoint at https://mcp.storecanary.app/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 · mcp.storecanary.app
claude mcp add --transport http erikras-store-canary 'https://mcp.storecanary.app/mcp'
What is the Store Canary MCP server?
Store Canary is an MCP server listed in the public MCP registry as io.github.erikras/store-canary. Free read-only WooCommerce checks: store, SSL, exposure, SEO, speed, products, policies + 3 prompts. This page covers its hosted endpoint (https://mcp.storecanary.app/mcp).
Is the Store Canary MCP server safe to use?
Store Canary scores 72 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 Store Canary MCP server expose?
Store Canary exposes 8 tools: check_store, check_ssl, check_exposure, check_seo_basics, check_speed, and 3 more. Their descriptions and schemas cost roughly 1,083 tokens of context every time the server is loaded.
Does the Store Canary MCP server require authentication?
No. We connected to Store Canary without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Store Canary MCP server still maintained?
Store Canary is still listed as active in the MCP registry. We last reached this channel on 5 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 Store Canary MCP server?
VerifyMCP ran 12 checks on Store Canary, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Store Canary: 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.