# LNX QR codes (remote · qr.lnx.net)

Styled, print-ready QR codes for links, text, email or phone, with frames and custom colors.

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

## Components

- remote · `qr.lnx.net`: 79/100 (this document), [markdown](https://verifymcp.io/servers/net-lnx-qr/qr.md), [page](https://verifymcp.io/servers/net-lnx-qr/qr)

## Channel facts

- Endpoint: `https://qr.lnx.net/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-10-23.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 449 tokens (~449/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the LNX QR codes MCP server?

LNX QR codes is a hosted endpoint at https://qr.lnx.net/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.

### Claude

```bash
claude mcp add --transport http net-lnx-qr 'https://qr.lnx.net/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "net-lnx-qr": {
      "url": "https://qr.lnx.net/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "net-lnx-qr": {
      "type": "http",
      "url": "https://qr.lnx.net/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.net-lnx-qr]
url = "https://qr.lnx.net/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-lnx-qr": {
      "type": "remote",
      "url": "https://qr.lnx.net/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add net-lnx-qr --url 'https://qr.lnx.net/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  net-lnx-qr:
    url: "https://qr.lnx.net/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "net-lnx-qr": {
      "Transport": "http",
      "Url": "https://qr.lnx.net/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add net-lnx-qr -t streamable-http -u 'https://qr.lnx.net/mcp'
```

### Other

```json
{
  "mcpServers": {
    "net-lnx-qr": {
      "type": "http",
      "url": "https://qr.lnx.net/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-10-23 (score 79, +1)

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

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

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

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

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

### 2026-10-17 (score 76, +1)

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

### 2026-10-15 (score 75, +1)

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

### 2026-10-12 (score 74, +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-10 (score 73, +2)

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

### 2026-10-06 (score 71, +1)

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

## MCP tools (1)

### `create_qr_code` (~358 tokens)

Create a QR code

Creates a styled QR code for a link, text, email address or phone number and returns the image, a print-size PNG link and a link to edit it in the LNX QR studio. Choose a style and an optional frame with a short call to action (e.g. "SCAN FOR MENU").

Input parameters:

- `background` (string): Optional hex background color, e.g. #ffffff. Must be light.
- `color` (string): Optional hex color for the code itself, e.g. #1e3a8a; overrides the style's colors. Must be dark.
- `content` (string, required): What the code opens: a URL, a text, an email address or a phone number (max 900 characters).
- `content_type` (string): url (default), text, email (opens a new email) or phone (starts a call).
- `email_body` (string): email only: prefilled message.
- `email_subject` (string): email only: prefilled subject.
- `frame` (string): Frame around the code. none (default) or outline have no text; label-bottom, label-top, button, solid-card, ticket, tag, bubble, banner, arrow, corners, minimal, phone, double show frame_text.
- `frame_font` (string)
- `frame_text` (string): Call to action shown in the frame, max 24 characters, e.g. "SCAN ME", "SCAN FOR MENU".
- `style` (string): Design. classic = plain black squares; rounded / dots = soft black shapes; violet, peach, forest, sunset = color gradients; sand, sky, rose, mint = single brand-like colors; ink-dots = black dots.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/net-lnx-qr/qr#diagnostics

## Score history

- 2026-10-23: 79
- 2026-10-22: 78
- 2026-10-21: 78
- 2026-10-20: 77
- 2026-10-19: 77
- 2026-10-18: 76
- 2026-10-17: 76
- 2026-10-16: 75
- 2026-10-15: 75
- 2026-10-14: 74
- 2026-10-13: 74
- 2026-10-12: 74
- 2026-10-11: 73
- 2026-10-10: 73
- 2026-10-06: 71
- 2026-10-05: 70
- 2026-10-04: 70
- 2026-10-03: 69
- 2026-10-02: 69
- 2026-10-01: 68

## Common questions

### What is the LNX QR codes MCP server?

LNX QR codes is an MCP server listed in the public MCP registry as net.lnx/qr. Styled, print-ready QR codes for links, text, email or phone, with frames and custom colors. This page covers its hosted endpoint (https://qr.lnx.net/mcp).

### Is the LNX QR codes MCP server safe to use?

LNX QR codes scores 79 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 LNX QR codes MCP server expose?

LNX QR codes exposes 1 tool: create_qr_code. Their descriptions and schemas cost roughly 358 tokens of context every time the server is loaded.

### Does the LNX QR codes MCP server require authentication?

No. We connected to LNX QR codes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the LNX QR codes MCP server still maintained?

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

## Links

- Remote endpoint: https://qr.lnx.net/mcp
- Website: https://lnx.net/qr
- Changelog RSS feed: https://verifymcp.io/servers/net-lnx-qr/qr.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-lnx-qr/qr.json
- HTML version of this page: https://verifymcp.io/servers/net-lnx-qr/qr