QR Branding
REMOTE · QR-BRANDING.COM · 2 COMPONENTS
Generate branded, scan-validated QR codes (manual, AI, templates, Wi-Fi, vCard, geo).
Available components
Last scanned (23 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Design and Media
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1353 tokens (~193/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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
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.
- 3 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.
- 1 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.
- 30 Oct 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.
- 28 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.
- 26 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.
- 24 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.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 0
- “qr_generate” added an optional parameter “frameStyle” cosmetic
- “qr_generate” added an optional parameter “frameText” cosmetic
- “qr_generate” added an optional parameter “frameTextColor” cosmetic
- “qr_generate” added an optional parameter “frameColor” cosmetic
- “qr_generate” reworded the description of “additionalConfig” cosmetic
- “qr_generate” dropped the optional parameter “frameShape” cosmetic
6 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
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 4 Nov 2026 · Probed https://qr-branding.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=qr-branding.com | CN=YE1,O=Let's Encrypt,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6c61e92f570096a0510a34a84ee4b03271d |
| SANs: qr-branding.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
| CN=ISRG Root X1,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 4 Jun 2015 | 4 Jun 2035 | RSA 4096 | SHA256-RSA | 8210cfb0d240e3594463e0bb63828b00 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of qr-branding.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| qr-branding.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; style-src 'unsafe-inline'; img-src 'self' data:; form-action 'self'; base-uri 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), serial=(), bluetooth=(), hid=(), magnetometer=(), gyroscope=(), accelerometer=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://qr-branding.com/mcp | Verified | 200 | |
| http (plaintext) | http://qr-branding.com/mcp | HTTPS enforced | 301 | https://qr-branding.com/mcp |
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 →
qr_build_geo Build a geo: URI QR ~67
Encode a latitude/longitude pair into a geo: URI QR. Scanning opens the location in the device's default maps app.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Latitude in decimal degrees (-90 to 90). |
| longitude | number | yes | Longitude in decimal degrees (-180 to 180). |
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | – | PDF in the stdio package only: local temp file the PDF was written to. |
| format | string | yes | File format the engine rendered: png, svg, jpg, webp or pdf. |
| mimeType | string | – | MIME type of the rendered file (the engine's contentType). |
| payload | string | yes | The payload string the engine built and the QR encodes (WIFI:..., BEGIN:VCARD..., geo:...). |
| resourceUri | string | – | PDF on the remote server only: URI of the embedded resource block that carries the file. |
| sizeBytes | integer | – | Size of the rendered file in bytes, as reported by the engine. |
No examples provided.
qr_build_vcard Build a vCard QR ~132
Encode a contact card (vCard) with first and last name, organization, phone, email and website URL into a QR. Scanning the QR adds the contact to the phone's address book.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email address. | |
| firstName | string | yes | Contact's first name. |
| lastName | string | – | Contact's last name. |
| organization | string | – | Company or organization name. |
| phone | string | – | Phone number, including country code (e.g. +1-555-867-5309). |
| url | string | – | Personal or company website URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | – | PDF in the stdio package only: local temp file the PDF was written to. |
| format | string | yes | File format the engine rendered: png, svg, jpg, webp or pdf. |
| mimeType | string | – | MIME type of the rendered file (the engine's contentType). |
| payload | string | yes | The payload string the engine built and the QR encodes (WIFI:..., BEGIN:VCARD..., geo:...). |
| resourceUri | string | – | PDF on the remote server only: URI of the embedded resource block that carries the file. |
| sizeBytes | integer | – | Size of the rendered file in bytes, as reported by the engine. |
No examples provided.
qr_build_wifi Build a Wi-Fi QR ~127
Encode Wi-Fi credentials (SSID, password, auth type, hidden flag) into a scannable Wi-Fi QR. Returns both the WIFI:... payload string and a generated QR image.
| Name | Type | Req | Description |
|---|---|---|---|
| authType | string | – | Authentication type. Defaults to "WPA". Use "nopass" for open networks. |
| hidden | boolean | – | Set true if the SSID is hidden (not broadcast). Defaults to false. |
| password | string | – | Network password. Required unless authType is "nopass". |
| ssid | string | yes | The Wi-Fi network name (SSID). |
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | – | PDF in the stdio package only: local temp file the PDF was written to. |
| format | string | yes | File format the engine rendered: png, svg, jpg, webp or pdf. |
| mimeType | string | – | MIME type of the rendered file (the engine's contentType). |
| payload | string | yes | The payload string the engine built and the QR encodes (WIFI:..., BEGIN:VCARD..., geo:...). |
| resourceUri | string | – | PDF on the remote server only: URI of the embedded resource block that carries the file. |
| sizeBytes | integer | – | Size of the rendered file in bytes, as reported by the engine. |
No examples provided.
qr_generate Generate a QR code (manual) ~466
Generate a fully branded QR code with explicit control over colors, module/finder shapes, logo, caption, and output format. Use this when the user already knows the design they want.
| Name | Type | Req | Description |
|---|---|---|---|
| additionalConfig | object | – | Escape hatch: any other QrConfig field the engine accepts (gradient stops, dot rotation, etc.). Merged on top of the structured fields above. |
| backgroundColor | string | – | Background color in hex (e.g. "#ffffff"). Use "transparent" for no background. |
| content | string | yes | The text or URL the QR will encode. Required. |
| eccLevel | string | – | Error-correction level (L=7%, M=15%, Q=25%, H=30%). Higher levels survive more damage but are denser. |
| fileFormat | string | – | Output format. Defaults to "png". |
| finderInnerShape | string | – | Shape of the inner dot of the three corner finder patterns. |
| finderOuterShape | string | – | Shape of the outer ring of the three corner finder patterns. |
| frameColor | string | – | Frame colour in hex, also the label background. Defaults to "#000000". |
| frameStyle | string | – | Call-to-action frame around the whole QR with a short label. Never covers the QR or its quiet zone. |
| frameText | string | – | Label inside the frame, max 40 characters, any language (e.g. "Scan me", "View the menu"). Defaults to "Scan me". |
| frameTextColor | string | – | Frame label colour in hex. Defaults to "#FFFFFF". |
| logoUrl | string | – | Public HTTPS URL of a logo image to embed at the center. |
| moduleShape | string | – | Shape of the small modules in the QR matrix. |
| outputHeight | integer | – | Output height in pixels (raster) or viewport units (svg). 64-4096. |
| outputWidth | integer | – | Output width in pixels (raster) or viewport units (svg). 64-4096. |
| primaryColor | string | – | Foreground/module color in hex (e.g. "#000000" or "#0a84ff"). |
| text | string | – | Optional caption rendered below the QR (e.g. a slogan). |
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | The text or URL the QR encodes, when the call set it. |
| filePath | string | – | PDF in the stdio package only: local temp file the PDF was written to. |
| format | string | yes | File format the engine rendered: png, svg, jpg, webp or pdf. |
| mimeType | string | – | MIME type of the rendered file (the engine's contentType). |
| resourceUri | string | – | PDF on the remote server only: URI of the embedded resource block that carries the file. |
| sizeBytes | integer | – | Size of the rendered file in bytes, as reported by the engine. |
No examples provided.
qr_generate_ai Generate a QR code from a prompt (AI) ~225
Generate a QR code where the QR Branding LLM picks colors and shapes from a natural-language prompt. Best for "make me a luxury gold dotted QR for a coffee brand" style requests.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The text or URL the QR will encode. |
| fileFormat | string | – | Output format. Defaults to "png". |
| logoUrl | string | – | Optional logo URL to embed at the center. |
| outputHeight | integer | – | Output height in pixels (raster) or viewport units (svg). 64-4096. |
| outputWidth | integer | – | Output width in pixels (raster) or viewport units (svg). 64-4096. |
| prompt | string | yes | Natural-language design brief. The engine's LLM will pick colors, shapes, and style hints from this. Example: "luxury gold dots for a coffee brand". |
| stylePreset | string | – | Optional style preset name (e.g. "minimal", "luxury", "playful"). Guides the LLM but does not override the design fully. |
| Name | Type | Req | Description |
|---|---|---|---|
| aiExplanation | string | – | The design model's explanation of its choices, when the engine returns one. |
| content | string | yes | The text or URL the QR encodes. |
| filePath | string | – | PDF in the stdio package only: local temp file the PDF was written to. |
| format | string | yes | File format the engine rendered: png, svg, jpg, webp or pdf. |
| mimeType | string | – | MIME type of the rendered file (the engine's contentType). |
| resourceUri | string | – | PDF on the remote server only: URI of the embedded resource block that carries the file. |
| safeModeApplied | boolean | – | True when the AI design did not scan and the engine re-rendered it in safe mode. |
| sizeBytes | integer | – | Size of the rendered file in bytes, as reported by the engine. |
No examples provided.
qr_generate_from_template Render a QR template ~203
Render one of the curated templates by id, optionally overriding the encoded content, colors, or output format/size for this specific call.
| Name | Type | Req | Description |
|---|---|---|---|
| additionalConfig | object | – | Escape hatch for any other QrConfig override the engine accepts. |
| backgroundColor | string | – | Override background color (hex). |
| content | string | – | Override what the QR encodes. Defaults to the template's built-in content. |
| fileFormat | string | – | Output format. Defaults to "png". |
| outputHeight | integer | – | Output height in pixels (raster) or viewport units (svg). 64-4096. |
| outputWidth | integer | – | Output width in pixels (raster) or viewport units (svg). 64-4096. |
| primaryColor | string | – | Override module color (hex). |
| templateId | – | yes | The template id (from qr_list_templates). May be numeric or string (e.g. "luxury-gold"). |
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | The text or URL the QR encodes, when the call set it. |
| filePath | string | – | PDF in the stdio package only: local temp file the PDF was written to. |
| format | string | yes | File format the engine rendered: png, svg, jpg, webp or pdf. |
| mimeType | string | – | MIME type of the rendered file (the engine's contentType). |
| resourceUri | string | – | PDF on the remote server only: URI of the embedded resource block that carries the file. |
| sizeBytes | integer | – | Size of the rendered file in bytes, as reported by the engine. |
No examples provided.
qr_list_templates List QR design templates ~71
List the 118 pre-designed QR templates (id, name, description, preview thumbnail URL). Filter by category if the user asks for a specific style.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter (e.g. "business", "social", "wifi"). Omit to list all 118 templates. |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | The category filter applied, if any. |
| templates | array | yes | The templates, after the optional category filter. |
| total | integer | yes | Number of templates returned. |
No examples provided.
How do I install the QR Branding MCP server?
QR Branding is a hosted endpoint at https://qr-branding.com/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.
remote · qr-branding.com
claude mcp add --transport http quartzondev-qr-branding 'https://qr-branding.com/mcp'
What is the QR Branding MCP server?
QR Branding is an MCP server listed in the public MCP registry as io.github.quartzondev/qr-branding. Generate branded, scan-validated QR codes (manual, AI, templates, Wi-Fi, vCard, geo). This page covers its hosted endpoint (https://qr-branding.com/mcp).
Is the QR Branding MCP server safe to use?
QR Branding 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 QR Branding MCP server expose?
QR Branding exposes 7 tools: qr_generate, qr_generate_ai, qr_list_templates, qr_generate_from_template, qr_build_wifi, and 2 more. Their descriptions and schemas cost roughly 1,291 tokens of context every time the server is loaded.
Does the QR Branding MCP server require authentication?
No. We connected to QR Branding without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the QR Branding MCP server still maintained?
QR Branding is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.