Canaryusers

What it can reach

From its install config and its own description; a sandbox run will confirm this later.

Checks on v1.2.2

1. Real tool

   passrules 2026-09-29.1 · 5 hours ago

2. Static scan

   passrules 2026-09-29.1 · 5 hours ago

3. Claims check

   skippedrules 2026-09-29.1 · 5 hours ago
   • infoLLM claims check is not configured on this deploy.

Install

Each app still asks you to confirm. Everything is pinned to the version checked above.

{
  "servers": {
    "canaryusers": {
      "type": "http",
      "url": "https://www.canaryusers.ai/api/mcp"
    }
  }
}

Tools it offers

As the server describes them. This text comes from the publisher and is shown as-is.

• canary_scan

  Run a CanaryUsers UX scan on a DEPLOYED URL (your live or preview app — not source code). A flock of AI personas evaluates the page and reports where real users would get stuck, with concrete fixes. Returns AI-ready findings you can act on immediately. Use depth='deep' for the thorough scan that renders the page, checks it VISUALLY on desktop + mobile (catches mobile breakage and layout issues), and clicks through key flows like signup/checkout (slower, ~60-90s, uses one credit); depth='quick' (default) is a fast static check that does NOT see mobile or visual issues — use 'deep' when the user mentions mobile, layout, or visual problems. IMPORTANT: if this returns status 'running' with a scanId, the findings are not ready yet — wait ~30s, then call get_report_markdown(scanId), repeating until it returns the report. Always fetch and present the findings before stopping, then offer to fix the top issues.

• list_recent_scans

  List the most recent CanaryUsers UX scans for your account (id, URL, CanaryScore, grade, status, date). Use this to find a scan to dig into.

• get_report_markdown

  Get one scan's full report as AI-ready markdown: the findings ranked by severity, why each matters, and how to fix it. Pass a scanId from list_recent_scans.