# ai.canaryusers/canaryusers (remote · www.canaryusers.ai)

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

- Trust score: 78/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `www.canaryusers.ai`: 78/100 (this document), [markdown](https://verifymcp.io/servers/ai-canaryusers-canaryusers/api-mcp.md), [page](https://verifymcp.io/servers/ai-canaryusers-canaryusers/api-mcp)

## Channel facts

- Endpoint: `https://www.canaryusers.ai/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 597 tokens (~199/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-canaryusers-canaryusers https://www.canaryusers.ai/api/mcp
```

### Codex

```toml
[mcp_servers.ai-canaryusers-canaryusers]
url = "https://www.canaryusers.ai/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-canaryusers-canaryusers": {
      "type": "remote",
      "url": "https://www.canaryusers.ai/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-canaryusers-canaryusers --url https://www.canaryusers.ai/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-canaryusers-canaryusers:
    url: "https://www.canaryusers.ai/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-canaryusers-canaryusers": {
      "type": "http",
      "url": "https://www.canaryusers.ai/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 78, +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.

### 2026-07-31 (score 77, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 71, +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.

### 2026-07-27 (score 70, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 69)

First indexed and scored.

## MCP tools (3)

### `canary_scan` (~270 tokens)

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.

Input parameters:

- `depth` (string): 'quick' (default, fast, free) or 'deep' (clicks through flows + visual review, ~1 credit).
- `url` (string, required): The public URL to scan (e.g. your deployed app or preview URL).

### `list_recent_scans` (~64 tokens)

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.

Input parameters:

- `limit` (number): How many to return (default 10, max 50).

### `get_report_markdown` (~63 tokens)

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.

Input parameters:

- `scanId` (string, required): The scan id (UUID) to fetch.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-canaryusers-canaryusers/api-mcp#diagnostics

## Score history

- 2026-08-03: 78
- 2026-08-02: 78
- 2026-08-01: 77
- 2026-07-31: 77
- 2026-07-30: 72
- 2026-07-29: 71
- 2026-07-28: 71
- 2026-07-27: 70
- 2026-07-26: 69

## Links

- Remote endpoint: https://www.canaryusers.ai/api/mcp
- Authorisation metadata: https://www.canaryusers.ai/.well-known/oauth-protected-resource/api/mcp
- Repository: https://github.com/CanaryUsers-ai/canaryusers-mcp
- Website: https://www.canaryusers.ai/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-canaryusers-canaryusers/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-canaryusers-canaryusers/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-canaryusers-canaryusers/api-mcp