ai.canaryusers/canaryusers
REMOTE · WWW.CANARYUSERS.AI · SCANNED SEP 20
A flock of AI users tests your deployed app and reports where real people get stuck, with fixes.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the ai.canaryusers/canaryusers MCP server?
ai.canaryusers/canaryusers is a hosted endpoint at https://www.canaryusers.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.canaryusers.ai
claude mcp add --transport http ai-canaryusers-canaryusers 'https://www.canaryusers.ai/api/mcp'
{
"mcpServers": {
"ai-canaryusers-canaryusers": {
"url": "https://www.canaryusers.ai/api/mcp"
}
}
} {
"servers": {
"ai-canaryusers-canaryusers": {
"type": "http",
"url": "https://www.canaryusers.ai/api/mcp"
}
}
} [mcp_servers.ai-canaryusers-canaryusers] url = "https://www.canaryusers.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-canaryusers-canaryusers": {
"type": "remote",
"url": "https://www.canaryusers.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add ai-canaryusers-canaryusers --url 'https://www.canaryusers.ai/api/mcp' --transport streamable-http
mcp_servers:
ai-canaryusers-canaryusers:
url: "https://www.canaryusers.ai/api/mcp" {
"McpServers": {
"ai-canaryusers-canaryusers": {
"Transport": "http",
"Url": "https://www.canaryusers.ai/api/mcp"
}
}
} assistant mcp add ai-canaryusers-canaryusers -t streamable-http -u 'https://www.canaryusers.ai/api/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://www.canaryusers.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.canaryusers.ai | CN=YR2,O=Let's Encrypt,C=US | 6 Aug 2026 | 4 Nov 2026 | RSA 2048 | SHA256-RSA | 5d8c454117722fb9a883c9b0fbacdedd07f |
| SANs: www.canaryusers.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.canaryusers.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| canaryusers.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.canaryusers.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.canaryusers.ai/api/mcp | HTTPS enforced | 308 | https://www.canaryusers.ai/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
canary_scan ~270
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.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | 'quick' (default, fast, free) or 'deep' (clicks through flows + visual review, ~1 credit). |
| url | string | yes | The public URL to scan (e.g. your deployed app or preview URL). |
No output schema declared.
No examples provided.
get_report_markdown ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| scanId | string | yes | The scan id (UUID) to fetch. |
No output schema declared.
No examples provided.
list_recent_scans ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many to return (default 10, max 50). |
No output schema declared.
No examples provided.
What is the ai.canaryusers/canaryusers MCP server?
ai.canaryusers/canaryusers is an MCP server listed in the public MCP registry as ai.canaryusers/canaryusers. A flock of AI users tests your deployed app and reports where real people get stuck, with fixes. This page covers its hosted endpoint (https://www.canaryusers.ai/api/mcp).
Is the ai.canaryusers/canaryusers MCP server safe to use?
ai.canaryusers/canaryusers scores 91 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ai.canaryusers/canaryusers MCP server expose?
ai.canaryusers/canaryusers exposes 3 tools: canary_scan, list_recent_scans, get_report_markdown. Their descriptions and schemas cost roughly 397 tokens of context every time the server is loaded.
Does the ai.canaryusers/canaryusers MCP server require authentication?
Yes. ai.canaryusers/canaryusers asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the ai.canaryusers/canaryusers MCP server still maintained?
ai.canaryusers/canaryusers is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.