Skip to main content
Glama

Server Details

A flock of AI users tests your deployed app and reports where real people get stuck, with fixes.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
CanaryUsers-ai/canaryusers-mcp
GitHub Stars
0
Server Listing
CanaryUsers MCP Server
ChatGPT
–
Claude
–

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct role: canary_scan initiates a new scan, get_report_markdown retrieves a specific report, and list_recent_scans lists past scans. No overlap or ambiguity exists between them.

Naming Consistency4/5

Two tools follow the verb_noun pattern (get_report_markdown, list_recent_scans), but canary_scan uses a noun_noun structure that doesn't explicitly indicate the action. The snake_case style is consistent, so the deviation is minor.

Tool Count5/5

With only 3 tools, the server is tightly scoped to the core scan workflow: create, retrieve, and list. Every tool is necessary and sufficient for the service's purpose.

Completeness5/5

The tools cover the full lifecycle of a scan: initiate, fetch the report via scanId, and list historical scans. The workflow around asynchronous scan completion is fully supported with polling via get_report_markdown.

Available Tools

3 tools
canary_scanAInspect

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.

Inputs: url (required), depth.

get_report_markdownAInspect

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.

Inputs: scanId (required).

list_recent_scansAInspect

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.

Inputs: limit.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.