Store Canary MCP server
io.github.erikras/store-canaryerikrasstreamable-httpv1.1.0Scanned
Free read-only WooCommerce checks: store, SSL, exposure, SEO, speed, products, policies + 3 prompts
8 tools: 7 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 7
- Can send data out · 7
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
7 tools here change things. Govern them.
- 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 Store Canary MCP server can do
The Store Canary MCP server is published by the GitHub account erikras. It has 8 tools. It can create or change data (7 tools: check_store, check_ssl, check_exposure, check_seo_basics and 3 more), but cannot delete data. 1 tool only reads.
7 tools bring in text other people can write (check_store, check_ssl, check_exposure and 4 more); 7 tools can send data out of your system (check_store, check_ssl, check_exposure and 4 more).
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 12, 2026, version 1.1.0.
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.
8 tools
Changes things 7Claude Code: ask
check_exposureFlag 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/deb…Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- 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.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check what a store exposes publicly
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
check_policiesCheck that the homepage links to privacy, terms, shipping and returns/refunds pages, and that each linked page on the same site loads.Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- 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.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check a store's policy pages
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
check_seo_basicsCheck 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.Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- 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.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check a store's SEO basics
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
check_speedTime one download each of a store's homepage, one product page and the cart from Cloudflare's network.Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- 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.
Description, as the server wrote it 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.
Annotations the server declares
- title: Time a store's key pages
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
check_sslCheck 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.Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- 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.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check a store's HTTPS setup
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
check_storeCheck 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 m…Reads text others writeCan send data out1 finding
Why it is in this group
- The name "check_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 "check_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 "check_store" says "store": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check a WooCommerce store
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
explain_findingExplain a finding code returned by any Store Canary tool (for example ssl_hsts or exposure_debug_log) in plain words, with a suggested fix.1 finding
Why it is in this group
- The name "explain_finding" says "explain": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "explain_finding" 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":false}; The name "explain_finding" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Explain a Store Canary finding
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
check_productsRead up to 10 published products from the public WooCommerce Store API and flag missing prices, missing images and out-of-stock items.Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "read": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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.
Annotations the server declares
- title: Sample a store's products
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
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 write7
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out7
- 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:24 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
- 7
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.storecanary.app/mcp: tools/list returned 8 tools to an anonymous client, including check_store (write), check_ssl (write), check_exposure (write), check_seo_basics (write), check_speed (write) and 2 more
Posture changes
- Nov 6, 2026
- Tools that change things, listed without credentials: 1 to 7
Findings
Matches of fixed checks, with the text they matched.
- Warncheck_store
The server marks "check_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 "check_store" says "store": a word for a change.
- Warnexplain_finding
The server marks "explain_finding" 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":false}; The name "explain_finding" says "explain": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools7 changed.~7 changedView diff
- Changed:check_exposureChanges thingsdescriptioninputSchema
- Changed:check_policiesChanges thingsdescriptioninputSchema
- Changed:check_productsOnly readsdescriptioninputSchema
- Changed:check_seo_basicsChanges thingsdescriptioninputSchema
- Changed:check_speedChanges thingsdescriptioninputSchema
- Changed:check_sslChanges thingsdescriptioninputSchema
- Changed:check_storeChanges thingsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 7.View diff
- Tools that change things, listed without credentials: 1 to 7
Tools7 added.+7 addedView diff
- Added:check_exposureChanges things
- Added:check_policiesChanges things
- Added:check_productsOnly reads
- Added:check_seo_basicsChanges things
- Added:check_speedChanges things
- Added:check_sslChanges things
- Added:explain_findingChanges things
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http store-canary https://mcp.storecanary.app/mcpclaude mcp add --transport http store-canary https://mcp.storecanary.app/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": [],
"ask": [
"mcp__store-canary__check_store",
"mcp__store-canary__check_ssl",
"mcp__store-canary__check_exposure",
"mcp__store-canary__check_seo_basics",
"mcp__store-canary__check_speed",
"mcp__store-canary__check_products",
"mcp__store-canary__check_policies",
"mcp__store-canary__explain_finding"
],
"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 store-canary. Review it before you use it.
Capability tags behind 7 rules
- mcp__store-canary__check_store untrusted-input, outbound
- mcp__store-canary__check_ssl untrusted-input, outbound
- mcp__store-canary__check_exposure untrusted-input, outbound
- mcp__store-canary__check_seo_basics untrusted-input, outbound
- mcp__store-canary__check_speed untrusted-input, outbound
- mcp__store-canary__check_products untrusted-input, outbound
- mcp__store-canary__check_policies 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/io.github.erikras/store-canary/verify?hash=2fa998348af9e17115be8a1ca5f21df0e8cd5b9d36883d951553c3a4a82ca48d" | jq -e '.changed == false'Pinned hash 2fa998348af9, from Nov 12, 2026, 08:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.erikras/store-canary/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.erikras/store-canary)Source: MCP Registry · repository. Synced Oct 30, 2026, 15:17 UTC.
Store Canary MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Store Canary MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 7 of which can change, send or delete something, and 2 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 Store Canary MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Store Canary MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Store Canary MCP server have?
- 8 tools: 7 write, 1 read. check_store, check_ssl, check_exposure, check_seo_basics, check_speed, check_policies, explain_finding and check_products.
Does the Store Canary MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Store Canary MCP server send data to outside services?
- 7 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_store, check_ssl, check_exposure, check_seo_basics, check_speed, check_products and 1 more.
Has the Store Canary MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.