# QrVerloz (remote · qrverloz.com)

QR codes active 90 days, claimable forever. Request an API key in chat to retarget and track scans.

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

## Components

- remote · `qrverloz.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/neoshrek-qrverloz-mcp/api-mcp.md), [page](https://verifymcp.io/servers/neoshrek-qrverloz-mcp/api-mcp)

## Channel facts

- Endpoint: `https://qrverloz.com/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 8 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**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 936 tokens (~117/item across 8 items; 8 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**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http neoshrek-qrverloz-mcp https://qrverloz.com/api/mcp
```

### Codex

```toml
[mcp_servers.neoshrek-qrverloz-mcp]
url = "https://qrverloz.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "neoshrek-qrverloz-mcp": {
      "type": "remote",
      "url": "https://qrverloz.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add neoshrek-qrverloz-mcp --url https://qrverloz.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  neoshrek-qrverloz-mcp:
    url: "https://qrverloz.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "neoshrek-qrverloz-mcp": {
      "type": "http",
      "url": "https://qrverloz.com/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-02 (score 69, +1)

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

### 2026-07-31 (score 68, +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 67, 0)

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

### 2026-07-29 (score 67, +1)

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

### 2026-07-28 (score 66, +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 65, 0)

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

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (8)

### `create_qr_code` (~132 tokens)

Create a new QR code. Authenticated users (API key required) get a permanent short URL that can be retargeted at any time without reprinting the physical QR image — limits are set by the account plan. Anonymous users receive a one-time data URI image that is not stored and cannot be updated. On success the result is a pre-formatted markdown table — display it exactly as received, do not reformat or summarise.

Input parameters:

- `target_url` (string, required): Destination URL — must start with https:// or http://
- `title` (string, required): A human-readable label for the QR code

### `get_qr_code` (~114 tokens)

Look up a single QR code by its internal ID or short code. Returns a pre-formatted markdown table with fields: Title, ID, Short Code, Short URL, Destination, Status, Created, QR Code Link. Display the table exactly as received — do not reformat or summarise. Requires authentication.

Input parameters:

- `qr_code_id` (string): Internal UUID from create_qr_code or list_qr_codes
- `short_code` (string): Short code from the redirect URL (e.g. "abc123")

### `list_qr_codes` (~102 tokens)

List all QR codes in your account. Returns one pre-formatted markdown table per QR code with fields: Title, ID, Short Code, Short URL, Destination, Status, Created, QR Code Link. Display each table exactly as received — do not reformat or summarise. Requires authentication.

Input parameters:

- `limit` (integer): Items per page, max 20 (default: 20)
- `page` (integer): Page number (default: 1)

### `get_qr_scans` (~89 tokens)

Get the total lifetime scan count for a QR code. Returns a pre-formatted markdown table with fields: Title, ID, Short Code, Short URL, Destination, Status, Created, QR Code Link, Total Scans. Display the table exactly as received — do not reformat or summarise. Requires authentication.

Input parameters:

- `qr_code_id` (string, required): Internal UUID of the QR code

### `update_qr_target` (~140 tokens)

Change the destination URL of a QR code without touching the printed image. Print once, redirect anywhere — forever. Accepts either the internal qr_code_id or the short_code from the redirect URL. On success the result is a pre-formatted markdown table — display it exactly as received, do not reformat or summarise. Requires authentication.

Input parameters:

- `qr_code_id` (string): Internal UUID from create_qr_code or list_qr_codes
- `short_code` (string): Short code from the redirect URL (e.g. "abc123")
- `target_url` (string, required): New destination URL — must start with https:// or http://

### `delete_qr_code` (~176 tokens)

Permanently delete a QR code and its scan history. This action cannot be undone. To prevent accidental or injected deletions, you MUST supply confirm_title — the exact title of the code as returned by get_qr_code or list_qr_codes. If the title does not match the stored record, the deletion is refused. Always call get_qr_code or list_qr_codes first to retrieve the exact title before calling this tool. Requires authentication.

Input parameters:

- `confirm_title` (string, required): The exact title of the QR code to delete — must match the stored title character-for-character. This prevents blind or injected deletions.
- `qr_code_id` (string): Internal UUID from create_qr_code or list_qr_codes
- `short_code` (string): Short code from the redirect URL (e.g. "abc123")

### `get_account_info` (~53 tokens)

Get your account details: current plan, QR code usage, and which features are available. Use this before create_qr_code to check remaining capacity, or to confirm which features are active on your plan. Requires authentication.

### `request_api_key` (~130 tokens)

Get a free API token — no account or email required. The token gives you up to 5 QR codes that can be updated at any time. IMPORTANT LIFETIME WARNING: the token expires after 90 days, and QR codes are permanently deleted ~90 days after that (~180 days total). To keep codes alive permanently, claim a free account at https://qrverloz.com/claim — this must be done before the token expires. Save the returned token: it is shown only once. Add it to your MCP client config under Authorization: Bearer, then call create_qr_code.

## Diagnostics

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

## Score history

- 2026-08-03: 69
- 2026-08-02: 69
- 2026-08-01: 68
- 2026-07-31: 68
- 2026-07-30: 67
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 65
- 2026-07-26: 65

## Links

- Remote endpoint: https://qrverloz.com/api/mcp
- Repository: https://github.com/neoshrek/qrverloz-mcp
- Changelog RSS feed: https://verifymcp.io/servers/neoshrek-qrverloz-mcp/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/neoshrek-qrverloz-mcp/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/neoshrek-qrverloz-mcp/api-mcp