Store Canary

Check a store's HTTPS setup

check_ssl

Read-onlyIdempotent

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "check_ssl"
  }
}

Input Schema

Name	Required	Description	Default
`url`	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.

Output Schema

Name	Required	Description
`url`	Yes	Normalized store origin that was checked.
`status`	Yes	checked = findings below; otherwise no store request was made.
`liteUrl`	Yes	Store Canary Lite on WordPress.org (free).
`overall`	Yes
`summary`	Yes
`auditUrl`	Yes	Full Store Canary audit (plain external link).
`findings`	Yes
`checkedAt`	Yes
`reportUrl`	No	Shareable read-only report page. The result is encoded in the link; nothing is stored.
`proTrialUrl`	Yes	Store Canary Pro 30-day free trial.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

changedInput schema / properties / url / description

Previous value: -"The store's public address, for example https://example.com"New value: +"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."

Changed1 schema field changedOct 30, 2026

addedOutput schema / properties / reportUrl

Added value: +{
+  "description": "Shareable read-only report page. The result is encoded in the link; nothing is stored.",
+  "format": "uri",
+  "type": "string"
+}

AddedOct 30, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, but the description adds real value: exactly what the GET requests will and won't do (never logs in, adds to cart, or submits forms) and the honest limitation that exact certificate expiry isn't observable externally. This sets expectations beyond the structured hints, though it doesn't discuss response timing, rate limits, or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the enumerated checks, then limitations and input handling. Every sentence carries information, though the hostname/path note is duplicated from the schema and could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the description covers the key expectation-setting caveats (expiry invisibility, no persistence, no form submission). Missing only the practical context of how long a run takes or what conditions cause an error.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single url parameter is fully documented there, including the bare-hostname acceptance and path-ignoring behavior. The description restates the same facts ('A bare hostname is fine; URL paths are ignored') rather than adding new syntax or format guidance, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb+resource and enumerates the four concrete checks (certificate acceptance, http→https redirect, redirect-chain length/staying on HTTPS, HSTS header). That makes the scope unmistakably distinct from check_seo_basics or check_speed, though it never explicitly names a sibling the way a 5 would.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly frames this as a one-off outside fetch and rules out ongoing monitoring ('Nothing is monitored or saved; ongoing checks are Store Canary Pro'), which effectively tells the agent when not to use it. It stops short of naming an alternative sibling tool or stating prerequisites for when a full store audit is warranted.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Store Canary tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.