# io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13 (remote · mcp.zovo.one)

QR codes and barcodes offline: WiFi, vCards, SEPA payment codes, Code 128, EAN-13, SVG or PNG.

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

## Components

- remote · `mcp.zovo.one`: 83/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-barcode-qr-code-sepa-payment-ean13/mcp-barcode.md), [page](https://verifymcp.io/servers/theluckystrike-barcode-qr-code-sepa-payment-ean13/mcp-barcode)
- mcpb · `barcode.mcpb`: 45/100, [markdown](https://verifymcp.io/servers/theluckystrike-barcode-qr-code-sepa-payment-ean13/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-barcode-mc.md), [page](https://verifymcp.io/servers/theluckystrike-barcode-qr-code-sepa-payment-ean13/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-barcode-mc)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/barcode`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.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-09-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - 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**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2498 tokens (~227/item across 11 items; 10 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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.

## Install

### How do I install the io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13 MCP server?

io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13 is a hosted endpoint at https://mcp.zovo.one/mcp/barcode, 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 theluckystrike-barcode-qr-code-sepa-payment-ean1 'https://mcp.zovo.one/mcp/barcode'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-barcode-qr-code-sepa-payment-ean1": {
      "url": "https://mcp.zovo.one/mcp/barcode"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-barcode-qr-code-sepa-payment-ean1": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/barcode"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-barcode-qr-code-sepa-payment-ean1]
url = "https://mcp.zovo.one/mcp/barcode"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-barcode-qr-code-sepa-payment-ean1": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/barcode",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-barcode-qr-code-sepa-payment-ean1 --url 'https://mcp.zovo.one/mcp/barcode' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-barcode-qr-code-sepa-payment-ean1:
    url: "https://mcp.zovo.one/mcp/barcode"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-barcode-qr-code-sepa-payment-ean1": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/barcode"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-barcode-qr-code-sepa-payment-ean1 -t streamable-http -u 'https://mcp.zovo.one/mcp/barcode'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-barcode-qr-code-sepa-payment-ean1": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/barcode"
    }
  }
}
```

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-09-19 (score 83, +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-09-17 (score 82, +1)

- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-15 (score 81, +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-09-13 (score 80, +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.

### 2026-09-11 (score 79, +3)

- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: unverified → 100
- [functional] The server now declares the “prompts” capability
- [functional] The server now declares the “resources” capability
- [functional] New prompt “upgrade_to_pro”
- [functional] New resource “pricing”

### 2026-09-09 (score 76, +1)

- [security] Tool “qr_create” rewrote its description, which is the text the model reads
- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [security] Tool “code_list” rewrote its description, which is the text the model reads
- [security] Tool “barcode_create” rewrote its description, which is the text the model reads
- [security] Tool “qr_wifi” rewrote its description, which is the text the model reads
- [security] Tool “license_status” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “license_activate” reworded the description of “key”

### 2026-09-08 (score 75, +39)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-09-04 (score 36)

First indexed and scored.

## MCP tools (10)

### `license_status` (~55 tokens)

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

### `qr_create` (~240 tokens)

QR code

Call this tool to turn text or a URL into a QR code: SVG inline, or a PNG at a pixel size to out_path (Pro). Returns version, module grid and payload size. Free: 20 codes a month on this server.

Input parameters:

- `error_correction` (string): L 7%, M 15% (default), Q 25%, H 30% of the code recoverable when damaged
- `format` (string): svg (default, free) or png (Pro)
- `margin` (integer): Quiet zone in modules, default 4, which is what the QR standard requires
- `out_path` (string): Name for the downloaded file, e.g. acme-code. SVG is returned inline when this is left out; a PNG always comes back as a download link valid for one hour
- `overwrite` (boolean): Replace a file of the same name already produced in this request (default false)
- `size` (integer): PNG width in pixels, 32 to 4000 (default 300). SVG scales without it
- `text` (string, required): The text or URL the code carries

### `qr_wifi` (~301 tokens)

WiFi QR code

Call this tool to make a QR code that joins a WiFi network when scanned: ssid, password and auth type, written to out_path or returned as SVG. Free: 20 codes a month. qr_create takes plain text or a URL.

Input parameters:

- `auth` (string): WPA (default when a password is given), WEP, or nopass for an open network
- `error_correction` (string): L 7%, M 15% (default), Q 25%, H 30% of the code recoverable when damaged
- `format` (string): svg (default, free) or png (Pro)
- `hidden` (boolean): True if the network does not broadcast its name
- `margin` (integer): Quiet zone in modules, default 4, which is what the QR standard requires
- `out_path` (string): Name for the downloaded file, e.g. acme-code. SVG is returned inline when this is left out; a PNG always comes back as a download link valid for one hour
- `overwrite` (boolean): Replace a file of the same name already produced in this request (default false)
- `password` (string): Passphrase. Leave out only for an open network
- `size` (integer): PNG width in pixels, 32 to 4000 (default 300). SVG scales without it
- `ssid` (string, required): Network name, exactly as it appears

### `qr_vcard` (~357 tokens)

Contact QR code

Call this tool to make a QR code that adds a contact when scanned (vCard 3.0). For your own card pass nothing: name, phone, email and address default to the shared business profile, never asked for.

Input parameters:

- `address` (string): Postal address, one line. Defaults to the shared business profile
- `email` (string): Email address. Defaults to the shared business profile
- `error_correction` (string): L 7%, M 15% (default), Q 25%, H 30% of the code recoverable when damaged
- `format` (string): svg (default, free) or png (Pro)
- `margin` (integer): Quiet zone in modules, default 4, which is what the QR standard requires
- `name` (string): Full name, for example Anna Kowalska. Defaults to the shared business profile's name; pass it only for someone else's card
- `note` (string): Free note stored on the contact
- `org` (string): Company or organisation
- `out_path` (string): Name for the downloaded file, e.g. acme-code. SVG is returned inline when this is left out; a PNG always comes back as a download link valid for one hour
- `overwrite` (boolean): Replace a file of the same name already produced in this request (default false)
- `phone` (string): Phone number, in the form it should be dialled. Defaults to the shared business profile
- `size` (integer): PNG width in pixels, 32 to 4000 (default 300). SVG scales without it
- `title` (string): Job title
- `url` (string): Website

### `qr_payment_sepa` (~435 tokens)

SEPA payment QR code

Call this tool for an EPC069-12 payment QR a euro banking app can scan. Amount and reference are enough: the beneficiary IBAN and name default to the shared business profile, never asked for.

Input parameters:

- `amount` (number): Amount in EUR, 0.01 to 999999999.99. Leave out and the payer types it
- `bic` (string): Beneficiary BIC. Optional under EPC version 002
- `currency` (string): EUR only; any other value is refused, because EPC encodes a SEPA credit transfer
- `error_correction` (string): L 7%, M 15% (default), Q 25%, H 30% of the code recoverable when damaged
- `format` (string): svg (default, free) or png (Pro)
- `iban` (string): Beneficiary IBAN. Defaults to the iban in the shared business profile (set once with the invoice server's business_set). Checked with ISO 7064 mod 97 and refused if it does not validate
- `margin` (integer): Quiet zone in modules, default 4, which is what the QR standard requires
- `name` (string): Beneficiary name, up to 70 characters. Defaults to the name in the shared business profile
- `out_path` (string): Name for the downloaded file, e.g. acme-code. SVG is returned inline when this is left out; a PNG always comes back as a download link valid for one hour
- `overwrite` (boolean): Replace a file of the same name already produced in this request (default false)
- `purpose` (string): Four-letter ISO 20022 purpose code, for example GDDS
- `reference` (string): Structured creditor reference (RF...), up to 35. Use this OR remittance, never both
- `remittance` (string): Free payment text, up to 140 characters, for example an invoice number
- `size` (integer): PNG width in pixels, 32 to 4000 (default 300). SVG scales without it

### `invoice_payment_qr` (~331 tokens)

Payment QR for an invoice

Call this tool for a SEPA payment QR from just an amount and reference: IBAN and name are read from the shared business profile, never asked for; pass invoice_id instead to take the amount from an invoice.

Input parameters:

- `amount` (number): Amount in EUR. Overrides the invoice total; required when there is no invoice to read
- `error_correction` (string): L 7%, M 15% (default), Q 25%, H 30% of the code recoverable when damaged
- `format` (string): svg (default, free) or png (Pro)
- `iban` (string): Override the IBAN in the shared business profile
- `invoice_id` (string): Invoice number, for example INV-2026-0007. Read from the invoice server's store if it is present
- `margin` (integer): Quiet zone in modules, default 4, which is what the QR standard requires
- `name` (string): Override the beneficiary name in the shared business profile
- `out_path` (string): Name for the downloaded file, e.g. acme-code. SVG is returned inline when this is left out; a PNG always comes back as a download link valid for one hour
- `overwrite` (boolean): Replace a file of the same name already produced in this request (default false)
- `reference` (string): Payment text, up to 140 characters. Defaults to the invoice number
- `size` (integer): PNG width in pixels, 32 to 4000 (default 300). SVG scales without it

### `barcode_create` (~261 tokens)

Barcode

Call this tool to draw a linear barcode (code128, ean13, ean8, upca) as SVG, or PNG to out_path. A short EAN or UPC gets its check digit computed; a wrong one is refused, never redrawn. qr_create makes QR codes.

Input parameters:

- `format` (string): svg (default, free) or png (Pro)
- `height` (integer): Bar height in the same units (default 80)
- `module_width` (integer): Width of the narrowest bar, in pixels or SVG units (default 2)
- `out_path` (string): Name for the downloaded file, e.g. acme-code. SVG is returned inline when this is left out; a PNG always comes back as a download link valid for one hour
- `overwrite` (boolean): Replace a file of the same name already produced in this request (default false)
- `symbology` (string, required): code128 for any printable ASCII, ean13 and ean8 for retail products, upca for North American retail
- `text` (boolean): Print the digits under the bars (default true)
- `value` (string, required): The data to encode. Digits only for EAN and UPC

### `barcode_batch` (~292 tokens)

Barcodes in bulk

Call this tool to draw many barcodes or QR codes at once from a list of rows, each with its own value and file name. Every row comes back as its own download link valid for one hour. Pro; the free tier does one code per call.

Input parameters:

- `format` (string): svg (default, free) or png (Pro)
- `height` (integer): Bar height in the same units (default 80)
- `items` (array, required): The rows to draw
- `module_width` (integer): Width of the narrowest bar, in pixels or SVG units (default 2)
- `out_dir` (string): Ignored on this hosted endpoint: there are no directories, and every row comes back as its own download link
- `out_path` (string): Name for the downloaded file, e.g. acme-code. SVG is returned inline when this is left out; a PNG always comes back as a download link valid for one hour
- `overwrite` (boolean): Replace a file of the same name already produced in this request (default false)
- `stop_on_error` (boolean): Stop at the first bad row instead of drawing the rest and reporting it (default false)
- `symbology` (string): Default symbology for rows that do not name one (default code128)
- `text` (boolean): Print the digits under the bars (default true)

### `code_list` (~100 tokens)

Codes generated

List the codes this server generated, newest first, with what each carried and where it went, plus how much of the free 20 a month is used. Filter by kind. It reads the register, not the files.

Input parameters:

- `kind` (string): Only rows of this kind: text, wifi, vcard, sepa, invoice, barcode or batch
- `limit` (integer): How many rows to show, newest first (default 20)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-barcode-qr-code-sepa-payment-ean13/mcp-barcode#diagnostics

## Score history

- 2026-09-20: 83
- 2026-09-19: 83
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 76
- 2026-09-09: 76
- 2026-09-08: 75
- 2026-09-07: 36
- 2026-09-06: 36
- 2026-09-05: 36
- 2026-09-04: 36

## Common questions

### What is the io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13 MCP server?

io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13 is an MCP server listed in the public MCP registry as io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13. QR codes and barcodes offline: WiFi, vCards, SEPA payment codes, Code 128, EAN-13, SVG or PNG. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/barcode).

### Is the io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13 MCP server safe to use?

io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13 scores 83 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 io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13 MCP server expose?

io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13 exposes 10 tools: license_status, license_activate, qr_create, qr_wifi, qr_vcard, and 5 more. Their descriptions and schemas cost roughly 2,448 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13 MCP server require authentication?

Yes. io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13 asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13 MCP server still maintained?

io.github.theluckystrike/barcode-qr-code-sepa-payment-ean13 is still listed as active in the MCP registry. We last reached this channel on 20 September 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://mcp.zovo.one/mcp/barcode
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/barcode
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/barcode
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-barcode-qr-code-sepa-payment-ean13/mcp-barcode.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-barcode-qr-code-sepa-payment-ean13/mcp-barcode.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-barcode-qr-code-sepa-payment-ean13/mcp-barcode