# Quality QR (remote · quality-qr.app)

Create and manage trackable QR codes with scan tracking, analytics, and dynamic URL updates.

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

## Components

- remote · `quality-qr.app`: 65/100 (this document), [markdown](https://verifymcp.io/servers/silly-geese-quality-qr/api-mcp.md), [page](https://verifymcp.io/servers/silly-geese-quality-qr/api-mcp)

## Channel facts

- Endpoint: `https://quality-qr.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1233 tokens (~205/item across 6 items; 6 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**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http silly-geese-quality-qr https://quality-qr.app/api/mcp
```

### Codex

```toml
[mcp_servers.silly-geese-quality-qr]
url = "https://quality-qr.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "silly-geese-quality-qr": {
      "type": "remote",
      "url": "https://quality-qr.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add silly-geese-quality-qr --url https://quality-qr.app/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  silly-geese-quality-qr:
    url: "https://quality-qr.app/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "silly-geese-quality-qr": {
      "type": "http",
      "url": "https://quality-qr.app/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-03 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 64, +1)

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

### 2026-07-30 (score 63, +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 62, +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 61, +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 60)

First indexed and scored.

## MCP tools (6)

### `quality_qr_create` (~565 tokens)

Create a new trackable QR code saved to your Quality QR account. Use this when the user wants to generate a QR code for a URL, WiFi network, contact card, calendar event, phone number, email, SMS, restaurant menu, app download link, or social media profile. The QR code is persisted with scan tracking and analytics. Returns an inline SVG image of the QR code.

Input parameters:

- `content` (string): The content to encode. Required for url, text, pdf, menu, and app-store types. For url types, provide the full URL including https://. For other types, use the 'data' parameter instead.
- `data` (object): Type-specific structured data. Use instead of 'content' for complex types. WiFi: {ssid: string, password?: string, encryption?: 'WPA'|'WEP'|'nopass', hidden?: boolean}. vCard: {firstName: string, las…
- `design` (object): Optional visual customization for the QR code.
- `isDynamic` (boolean): Set to true to create a dynamic QR code whose destination URL can be changed later without reprinting the physical code. Only works for URL-based types (url, pdf, menu, app-store, social). Default: f…
- `name` (string): A human-readable name for the QR code, e.g. 'Office WiFi' or 'Spring Menu 2026'. Auto-generated as 'MCP: {type} {date}' if omitted.
- `type` (string, required): QR code content type. 'url' for websites, 'wifi' for network credentials, 'vcard' for contact cards, 'email' for pre-filled emails, 'phone' for tap-to-call, 'sms' for pre-filled texts, 'text' for pla…

### `quality_qr_list` (~131 tokens)

List QR codes in the user's Quality QR account. Use this when the user wants to see their existing QR codes, find a specific code, or check how many codes they have. Returns ID, name, type, short URL, active status, and creation date for each code.

Input parameters:

- `limit` (number): Maximum number of results to return. Default: 50, maximum: 100.
- `offset` (number): Number of results to skip for pagination. Default: 0.
- `type` (string): Filter results to only QR codes of this type. Omit to return all types.

### `quality_qr_get` (~97 tokens)

Get full details of a specific QR code by its ID. Use this when the user wants to inspect a particular QR code's configuration, check its destination URL, view its design settings, or see its current status. Returns all metadata including content, destination, design, scan limits, and timestamps.

Input parameters:

- `id` (string, required): The unique identifier of the QR code. Obtain this from quality_qr_list or quality_qr_create responses.

### `quality_qr_update` (~193 tokens)

Update an existing QR code's properties. Use this when the user wants to change where a QR code points to, rename it, or enable/disable it. Destination URL changes only work for dynamic URL-based types (url, pdf, menu, app-store, social). Name and active status can be changed for any QR code type.

Input parameters:

- `destinationUrl` (string): New destination URL. Only works for dynamic URL-based types (url, pdf, menu, app-store, social). The physical QR code does not need reprinting.
- `id` (string, required): The unique identifier of the QR code to update. Obtain this from quality_qr_list or quality_qr_create responses.
- `isActive` (boolean): Set to false to disable the QR code (scans will stop redirecting). Set to true to re-enable it.
- `name` (string): New human-readable name for the QR code.

### `quality_qr_delete` (~90 tokens)

Permanently delete a QR code from the user's account. Use this when the user wants to remove a QR code they no longer need. The short URL will immediately stop redirecting. This action frees up a plan quota slot and cannot be undone.

Input parameters:

- `id` (string, required): The unique identifier of the QR code to permanently delete. Obtain this from quality_qr_list or quality_qr_create responses.

### `quality_qr_analytics` (~157 tokens)

Get scan analytics for a specific QR code. Use this when the user wants to know how many times a QR code has been scanned, see daily scan trends, understand which devices are scanning, or see which countries scans come from. Returns total scans, scans by day, device breakdown (mobile/tablet/desktop), and top 5 countries.

Input parameters:

- `days` (number): Number of days of scan history to retrieve. Default: 30. Capped by plan: Free tier = 7 days max, Pro = 30 days, Business = 365 days.
- `id` (string, required): The unique identifier of the QR code to get analytics for. Obtain this from quality_qr_list or quality_qr_create responses.

## Diagnostics

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

## Score history

- 2026-08-03: 65
- 2026-08-02: 64
- 2026-08-01: 64
- 2026-07-31: 64
- 2026-07-30: 63
- 2026-07-29: 62
- 2026-07-28: 62
- 2026-07-27: 61
- 2026-07-26: 60

## Links

- Remote endpoint: https://quality-qr.app/api/mcp
- Repository: https://github.com/silly-geese/quality-qr-mcp
- Website: https://quality-qr.app/
- Changelog RSS feed: https://verifymcp.io/servers/silly-geese-quality-qr/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/silly-geese-quality-qr/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/silly-geese-quality-qr/api-mcp