# QRX (npm · @qrxcodes/mcp)

Turn a prompt and a link into a branded, print-ready QR code that always scans.

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `qrx.codes`: 37/100, [markdown](https://verifymcp.io/servers/codes-qrx-mcp/qrx.md), [page](https://verifymcp.io/servers/codes-qrx-mcp/qrx)
- npm · `@qrxcodes/mcp`: 83/100 (this document), [markdown](https://verifymcp.io/servers/codes-qrx-mcp/qrxcodes-mcp.md), [page](https://verifymcp.io/servers/codes-qrx-mcp/qrxcodes-mcp)

## Channel facts

- Registry: `npm`
- Package: `@qrxcodes/mcp`
- Version: `1.0.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 26 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 733 tokens (~104/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the QRX MCP server?

QRX runs locally as an npm package, launched with npx -y @qrxcodes/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add codes-qrx-mcp -- npx -y @qrxcodes/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "codes-qrx-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@qrxcodes/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "codes-qrx-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@qrxcodes/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add codes-qrx-mcp -- npx -y @qrxcodes/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "codes-qrx-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@qrxcodes/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add codes-qrx-mcp --command npx --arg -y --arg @qrxcodes/mcp
```

### Hermes

```yaml
mcp_servers:
  codes-qrx-mcp:
    command: "npx"
    args: ["-y", "@qrxcodes/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "codes-qrx-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@qrxcodes/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add codes-qrx-mcp -t stdio -c npx -a -y @qrxcodes/mcp
```

### Other

```json
{
  "mcpServers": {
    "codes-qrx-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@qrxcodes/mcp"
      ]
    }
  }
}
```

## 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-11-05 (score 83, +1)

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

### 2026-11-03 (score 82, +1)

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

### 2026-11-01 (score 81, +1)

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

### 2026-10-30 (score 80, +1)

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

### 2026-10-28 (score 79, +1)

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

### 2026-10-26 (score 78, +1)

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

### 2026-10-24 (score 77, +1)

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

### 2026-10-21 (score 76, +4)

- [functional improvement] Stability: unverified → 0.27

## MCP tools (7)

### `generate_qr_code` (~220 tokens)

Generate a QR code

Use this when the user wants a new QR code that is also a picture: a scannable code painted into art from a description, that opens a link (or joins a Wi-Fi network, if the account’s plan includes Wi-Fi codes). It starts the code and answers at once with its id while the picture is painted, which usually takes under a minute; then call get_qr_code with the id to wait for the image. Do not use it to look at, list or change codes that already exist. Each code counts against the user’s QRX allowance.

Input parameters:

- `destination` (string): The link scans open: an absolute http or https URL, e.g. https://example.com/menu. Give this or wifi.
- `prompt` (string, required): What the picture should show, e.g. "a lighthouse on a cliff at sunset".
- `style` (string): A style id from list_styles. Leave out for the default.
- `wifi` (object): The Wi-Fi network the code joins. Give this or destination.

Output parameters:

- `createdAt` (string)
- `destination` (string|null): Where a link code’s scans go; null for a Wi-Fi code.
- `error` (object|null): Why the code failed, when it did.
- `id` (string): The code’s id. A link code’s id is also the path of its short link: lowercase letters and digits, currently 6 characters. A Wi-Fi code’s id is a UUID. Treat every id as an opaque, case-sensitive stri…
- `imageUrl` (string|null): The finished image (PNG), once the code has succeeded.
- `object`
- `pageUrl` (string): The code’s page in the app.
- `prompt` (string)
- `shortUrl` (string|null): The link the code encodes (`https://qrx.to/<id>`); scans go through it to `destination`. Null for a Wi-Fi code.
- `status` (string): `processing` until the picture is painted and checked to scan; then `succeeded` or `failed`. `queued` is reserved for a code waiting to start. More values may be added: treat anything other than `suc…
- `style` (string|null): The style id, if one was chosen.
- `type` (string): `url` for a link code, `wifi` for a Wi-Fi code. More values may be added.
- `wifi` (object|null): The network a Wi-Fi code joins; null for a link code. The password is never returned.

### `get_qr_code` (~122 tokens)

Get a QR code

Use this when you have a QR code’s id (from generate_qr_code or list_qr_codes) and need its status or finished image. While the code is still being painted it waits up to `wait` seconds (25 by default) for it to finish before answering, so call it again if it is still processing. Do not use it to make a new code.

Input parameters:

- `id` (string, required): The code’s id.
- `wait` (integer): Seconds to wait for a processing code to finish before answering, 0 to 25.

Output parameters:

- `createdAt` (string)
- `destination` (string|null): Where a link code’s scans go; null for a Wi-Fi code.
- `error` (object|null): Why the code failed, when it did.
- `id` (string): The code’s id. A link code’s id is also the path of its short link: lowercase letters and digits, currently 6 characters. A Wi-Fi code’s id is a UUID. Treat every id as an opaque, case-sensitive stri…
- `imageUrl` (string|null): The finished image (PNG), once the code has succeeded.
- `object`
- `pageUrl` (string): The code’s page in the app.
- `prompt` (string)
- `shortUrl` (string|null): The link the code encodes (`https://qrx.to/<id>`); scans go through it to `destination`. Null for a Wi-Fi code.
- `status` (string): `processing` until the picture is painted and checked to scan; then `succeeded` or `failed`. `queued` is reserved for a code waiting to start. More values may be added: treat anything other than `suc…
- `style` (string|null): The style id, if one was chosen.
- `type` (string): `url` for a link code, `wifi` for a Wi-Fi code. More values may be added.
- `wifi` (object|null): The network a Wi-Fi code joins; null for a link code. The password is never returned.

### `list_qr_codes` (~82 tokens)

List QR codes

Use this when the user asks about QR codes they already have, newest first, a page at a time (pass nextCursor as cursor for the next page). Do not use it to make a code.

Input parameters:

- `cursor` (string): nextCursor from the previous page.
- `limit` (integer): How many codes to return, 1 to 100.

Output parameters:

- `data` (array)
- `hasMore` (boolean)
- `nextCursor` (string|null): Pass as `cursor` for the next page; null on the last page.
- `object`

### `change_qr_code_destination` (~94 tokens)

Change where a QR code points

Use this when the user wants an existing link QR code to open a different web address. Printed copies follow at once. It only works for link codes, and only if the account’s plan allows changing destinations. Do not use it to make a new code.

Input parameters:

- `destination` (string, required): The new link scans should open: an absolute http or https URL.
- `id` (string, required): The code’s id.

Output parameters:

- `createdAt` (string)
- `destination` (string|null): Where a link code’s scans go; null for a Wi-Fi code.
- `error` (object|null): Why the code failed, when it did.
- `id` (string): The code’s id. A link code’s id is also the path of its short link: lowercase letters and digits, currently 6 characters. A Wi-Fi code’s id is a UUID. Treat every id as an opaque, case-sensitive stri…
- `imageUrl` (string|null): The finished image (PNG), once the code has succeeded.
- `object`
- `pageUrl` (string): The code’s page in the app.
- `prompt` (string)
- `shortUrl` (string|null): The link the code encodes (`https://qrx.to/<id>`); scans go through it to `destination`. Null for a Wi-Fi code.
- `status` (string): `processing` until the picture is painted and checked to scan; then `succeeded` or `failed`. `queued` is reserved for a code waiting to start. More values may be added: treat anything other than `suc…
- `style` (string|null): The style id, if one was chosen.
- `type` (string): `url` for a link code, `wifi` for a Wi-Fi code. More values may be added.
- `wifi` (object|null): The network a Wi-Fi code joins; null for a link code. The password is never returned.

### `get_account` (~49 tokens)

Get plan and usage

Use this when the user asks how many QR codes they can still make today, when the daily count resets, or what their QRX account can do. Do not use it to make or list codes.

Output parameters:

- `codes` (object): The daily allowance. All null when the account has no daily limit.
- `credentials` (object)
- `features` (object)
- `object`
- `plan` (string): What the account pays for. `features` says what it can do today, and the two can differ (for QRX staff, say), so act on `features`. More values may be added.
- `rateLimits` (object)

### `get_profile` (~42 tokens)

Get the signed-in QRX account

Use this when you need to know which QRX account is connected, for example to confirm it with the user. Do not use it for limits; use get_account.

Output parameters:

- `email` (string)
- `id` (string)
- `name` (string)
- `nickname` (string)

### `list_styles` (~43 tokens)

List QR code styles

Use this when the user wants to choose a look for a new QR code; pass a style id to generate_qr_code. Do not use it to make a code.

Output parameters:

- `data` (array)
- `hasMore` (boolean)
- `nextCursor` (null)
- `object`

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/codes-qrx-mcp/qrxcodes-mcp#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79
- 2026-10-28: 79
- 2026-10-27: 78
- 2026-10-26: 78
- 2026-10-25: 77
- 2026-10-24: 77
- 2026-10-23: 76
- 2026-10-22: 76
- 2026-10-21: 76
- 2026-10-20: 72
- 2026-10-19: 72
- 2026-10-18: 72
- 2026-10-17: 72
- 2026-10-16: 72
- 2026-10-15: 72
- 2026-10-14: 72
- 2026-10-13: 72
- 2026-10-12: 39
- 2026-10-11: 39

## Common questions

### What is the QRX MCP server?

QRX is an MCP server listed in the public MCP registry as codes.qrx/mcp. Turn a prompt and a link into a branded, print-ready QR code that always scans. This page covers its npm package (@qrxcodes/mcp).

### Is the QRX MCP server safe to use?

QRX scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 QRX MCP server expose?

QRX exposes 7 tools: generate_qr_code, get_qr_code, list_qr_codes, change_qr_code_destination, get_account, and 2 more. Their descriptions and schemas cost roughly 652 tokens of context every time the server is loaded.

### Is the QRX MCP server still maintained?

QRX is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the QRX MCP server under?

QRX declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@qrxcodes/mcp
- Socket report: https://socket.dev/npm/package/@qrxcodes/mcp
- Repository: https://github.com/qrxcodes/qrx-mcp
- Website: https://qrx.codes/developers
- Changelog RSS feed: https://verifymcp.io/servers/codes-qrx-mcp/qrxcodes-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/codes-qrx-mcp/qrxcodes-mcp.json
- HTML version of this page: https://verifymcp.io/servers/codes-qrx-mcp/qrxcodes-mcp