QRX
NPM · @QRXCODES/MCP · 2 COMPONENTS
Turn a prompt and a link into a branded, print-ready QR code that always scans.
Available components
Last scanned (8 hours ago)
Scores higher than 76% of npm servers
Category Design and Media
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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. View diagnostics → Unverified
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 26 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 733 tokens (~104/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
- Supports UI / widget rendering.Pass
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.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 21 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
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 5 Nov 2026 · Analysed npm/@qrxcodes/mcp@1.0.1
Provenance Repository mismatch
The attestation is cryptographically sound but binds a different repository to the one the registry declares. Most often the declared URL is simply stale.
| Result | Repository mismatch |
|---|---|
| Ecosystem | npm |
| Reason | Repository mismatch |
| Discovered via | Registry attestation endpoint |
| Source repo | qrxcodes/mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/qrxcodes/mcp/.github/workflows/publish.yml@refs/tags/v1.0.1 |
| Rekor log index | 3165191100 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c3da642a56fb041277806b6a5dc6500a8e881e73f6af07bb4dff791f5103265f11fc02f2f180de3ae4904104b6453a1ffdff8f0d6870e0b6bd802acaa |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
change_qr_code_destination Change where a QR code points ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | The new link scans should open: an absolute http or https URL. |
| id | string | yes | The code’s id. |
| Name | Type | Req | Description |
|---|---|---|---|
| createdAt | string | yes | – |
| destination | string|null | yes | Where a link code’s scans go; null for a Wi-Fi code. |
| error | object|null | yes | Why the code failed, when it did. |
| id | string | yes | 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 | yes | The finished image (PNG), once the code has succeeded. |
| object | – | yes | – |
| pageUrl | string | yes | The code’s page in the app. |
| prompt | string | yes | – |
| shortUrl | string|null | yes | The link the code encodes (`https://qrx.to/<id>`); scans go through it to `destination`. Null for a Wi-Fi code. |
| status | string | yes | `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 | yes | The style id, if one was chosen. |
| type | string | yes | `url` for a link code, `wifi` for a Wi-Fi code. More values may be added. |
| wifi | object|null | yes | The network a Wi-Fi code joins; null for a link code. The password is never returned. |
No examples provided.
generate_qr_code Generate a QR code ~220
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | The link scans open: an absolute http or https URL, e.g. https://example.com/menu. Give this or wifi. |
| prompt | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| createdAt | string | yes | – |
| destination | string|null | yes | Where a link code’s scans go; null for a Wi-Fi code. |
| error | object|null | yes | Why the code failed, when it did. |
| id | string | yes | 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 | yes | The finished image (PNG), once the code has succeeded. |
| object | – | yes | – |
| pageUrl | string | yes | The code’s page in the app. |
| prompt | string | yes | – |
| shortUrl | string|null | yes | The link the code encodes (`https://qrx.to/<id>`); scans go through it to `destination`. Null for a Wi-Fi code. |
| status | string | yes | `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 | yes | The style id, if one was chosen. |
| type | string | yes | `url` for a link code, `wifi` for a Wi-Fi code. More values may be added. |
| wifi | object|null | yes | The network a Wi-Fi code joins; null for a link code. The password is never returned. |
No examples provided.
get_account Get plan and usage ~49
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| codes | object | yes | The daily allowance. All null when the account has no daily limit. |
| credentials | object | yes | – |
| features | object | yes | – |
| object | – | yes | – |
| plan | string | yes | 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 | yes | – |
No examples provided.
get_profile Get the signed-in QRX account ~42
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| id | string | yes | – |
| name | string | yes | – |
| nickname | string | yes | – |
No examples provided.
get_qr_code Get a QR code ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The code’s id. |
| wait | integer | – | Seconds to wait for a processing code to finish before answering, 0 to 25. |
| Name | Type | Req | Description |
|---|---|---|---|
| createdAt | string | yes | – |
| destination | string|null | yes | Where a link code’s scans go; null for a Wi-Fi code. |
| error | object|null | yes | Why the code failed, when it did. |
| id | string | yes | 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 | yes | The finished image (PNG), once the code has succeeded. |
| object | – | yes | – |
| pageUrl | string | yes | The code’s page in the app. |
| prompt | string | yes | – |
| shortUrl | string|null | yes | The link the code encodes (`https://qrx.to/<id>`); scans go through it to `destination`. Null for a Wi-Fi code. |
| status | string | yes | `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 | yes | The style id, if one was chosen. |
| type | string | yes | `url` for a link code, `wifi` for a Wi-Fi code. More values may be added. |
| wifi | object|null | yes | The network a Wi-Fi code joins; null for a link code. The password is never returned. |
No examples provided.
list_qr_codes List QR codes ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | nextCursor from the previous page. |
| limit | integer | – | How many codes to return, 1 to 100. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| hasMore | boolean | yes | – |
| nextCursor | string|null | yes | Pass as `cursor` for the next page; null on the last page. |
| object | – | yes | – |
No examples provided.
list_styles List QR code styles ~43
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| hasMore | boolean | yes | – |
| nextCursor | null | yes | – |
| object | – | yes | – |
No examples provided.
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.
npm · @qrxcodes/mcp
claude mcp add codes-qrx-mcp -- npx -y @qrxcodes/mcp
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.