QR Branding MCP server
io.github.quartzondev/qr-brandingquartzondevstreamable-httpv0.2.8Scanned
Generate branded, scan-validated QR codes (manual, AI, templates, Wi-Fi, vCard, geo).
11 tools: 8 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 1
- 4 findings
Tools listed without sign-in. Remote posture
With Anlyon
8 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the QR Branding MCP server can do
The QR Branding MCP server is published by the GitHub account quartzondev. It has 11 tools. It can create or change data (8 tools: qr_generate, qr_scan_check, qr_generate_ai, qr_poster and 4 more), but cannot delete data. 3 tools only read.
2 tools bring in text other people can write (qr_list_templates and qr_list_ai_providers); 1 tool can send data out of your system (qr_build_vcard).
The fixed checks matched 4 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.
Last scanned Nov 14, 2026, version 0.2.8.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
11 tools
Changes things 8Claude Code: ask
qr_build_geoEncode a latitude/longitude pair into a geo: URI QR.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Encode a latitude/longitude pair into a geo: URI QR. Scanning opens the location in the device's default maps app. Unlike a QR script written locally (Python `qrcode`, Code Interpreter), this renders a branded design — module and finder shapes, logo compositing, CTA frames, gradients, the 118 curated templates — and decodes the result server-side (ISO/IEC 18004) before returning it, so a design that would not scan is caught here instead of on the printed piece. Local code can only draw a flat square matrix and cannot verify it.
Annotations the server declares
- title: Build a geo: URI QR
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
qr_build_vcardEncode a contact card (vCard) with first and last name, organization, phone, email and website URL into a QR.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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. Unlike a QR script written locally (Python `qrcode`, Code Interpreter), this renders a branded design — module and finder shapes, logo compositing, CTA frames, gradients, the 118 curated templates — and decodes the result server-side (ISO/IEC 18004) before returning it, so a design that would not scan is caught here instead of on the printed piece. Local code can only draw a flat square matrix and cannot verify it.
Annotations the server declares
- title: Build a vCard QR
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
qr_build_wifiEncode Wi-Fi credentials (SSID, password, auth type, hidden flag) into a scannable Wi-Fi QR.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "Encode Wi-Fi credentials (SSID, password, auth type, hidden flag..."
Description, as the server wrote it 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. Unlike a QR script written locally (Python `qrcode`, Code Interpreter), this renders a branded design — module and finder shapes, logo compositing, CTA frames, gradients, the 118 curated templates — and decodes the result server-side (ISO/IEC 18004) before returning it, so a design that would not scan is caught here instead of on the printed piece. Local code can only draw a flat square matrix and cannot verify it.
Annotations the server declares
- title: Build a Wi-Fi QR
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
qr_generateGenerate a fully branded QR code with explicit control over colors, module/finder shapes, logo, caption, and output format.1 finding
Why it is in this group
- The name "qr_generate" says "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "qr_generate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "qr_generate" says "generate": a word for a change.
Description, as the server wrote it 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. Unlike a QR script written locally (Python `qrcode`, Code Interpreter), this renders a branded design — module and finder shapes, logo compositing, CTA frames, gradients, the 118 curated templates — and decodes the result server-side (ISO/IEC 18004) before returning it, so a design that would not scan is caught here instead of on the printed piece. Local code can only draw a flat square matrix and cannot verify it.
Annotations the server declares
- title: Generate a QR code (manual)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
qr_generate_aiGenerate a QR code where the QR Branding LLM picks colors and shapes from a natural-language prompt.No findings
Why it is in this group
- The name "qr_generate_ai" says "generate": a word for a change.
Description, as the server wrote it 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. This is the one thing local code cannot do at all: a design model picks the palette, module and finder shapes, gradients and framing from the prompt, and the rendered code is then decoded server-side (ISO/IEC 18004) so a stylish result is still a scannable one.
Annotations the server declares
- title: Generate a QR code from a prompt (AI)
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
qr_generate_from_templateRender one of the curated templates by id, optionally overriding the encoded content, colors, or output format/size for this specific call.1 finding
Why it is in this group
- The name "qr_generate_from_template" says "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "qr_generate_from_template" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "qr_generate_from_template" says "generate": a word for a change.
Description, as the server wrote it Render one of the curated templates by id, optionally overriding the encoded content, colors, or output format/size for this specific call. Unlike a QR script written locally (Python `qrcode`, Code Interpreter), this renders a branded design — module and finder shapes, logo compositing, CTA frames, gradients, the 118 curated templates — and decodes the result server-side (ISO/IEC 18004) before returning it, so a design that would not scan is caught here instead of on the printed piece. Local code can only draw a flat square matrix and cannot verify it.
Annotations the server declares
- title: Render a QR template
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
qr_posterWrap one QR design in a print-ready poster: a4/a5/a6/letter trim, four layouts (minimal, band, card, tent), headline, instruction line, footer, optional logo, 3 mm bleed and crop m…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Wrap one QR design in a print-ready poster: a4/a5/a6/letter trim, four layouts (minimal, band, card, tent), headline, instruction line, footer, optional logo, 3 mm bleed and crop marks. Returns a vector PDF by default (ready for a print shop) or a png preview at 36-300 dpi. Useful for a table card, a shop window or a hotel desk. The design fields are the same qr_generate takes; fileFormat is the poster's own format, not the code's.
Annotations the server declares
- title: Render a print-ready poster around one QR
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
qr_scan_checkRun the print check on a design before it goes to the printer: the engine renders it and decodes it under 13 simulated conditions (small print, distance, blur, dim light, low contr…1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "qr_scan_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.
Description, as the server wrote it Run the print check on a design before it goes to the printer: the engine renders it and decodes it under 13 simulated conditions (small print, distance, blur, dim light, low contrast, glare, noise, rotation) and returns the same report the builder's scan panel shows, plus the minimum print size at table, wall and street distance. Call it after qr_generate when the result is going to be printed. fileFormat/outputWidth/outputHeight are ignored: the check renders its own bitmap.
Annotations the server declares
- title: Check that a QR design will scan
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 3Show 3 read-only tools
qr_get_templateFetch one of the 118 curated templates together with its full design config (module and finder shapes, colours, frame, caption).No findings
Why it is in this group
- The name "qr_get_template" says "get": a word for reading.
Description, as the server wrote it Fetch one of the 118 curated templates together with its full design config (module and finder shapes, colours, frame, caption). Use it when the user liked a template but wants changes: read the config here, then pass it to qr_generate with their tweaks. qr_generate_from_template renders the template as-is.
Annotations the server declares
- title: Read a curated template's design
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
qr_list_ai_providersList the LLM providers the engine accepts for bring-your-own-key AI designs (POST /api/qr/ai/generate), with each provider id, its default model and the recommended model ids.Reads text others writeNo findings
Why it is in this group
- The name "qr_list_ai_providers" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "post": it reads posts, which other people can write.
Description, as the server wrote it List the LLM providers the engine accepts for bring-your-own-key AI designs (POST /api/qr/ai/generate), with each provider id, its default model and the recommended model ids. Any model id your provider offers works; the list is a recommendation, not an allowlist. qr_generate_ai does not need this: it uses the managed path with our keys.
Annotations the server declares
- title: List the LLM providers for bring-your-own-key AI
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
qr_list_templatesList the 118 pre-designed QR templates (id, name, description, preview thumbnail URL).Reads text others writeNo findings
Why it is in this group
- The name "qr_list_templates" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it List the 118 pre-designed QR templates (id, name, description, preview thumbnail URL). Filter by category if the user asks for a specific style.
Annotations the server declares
- title: List QR design templates
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:10 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://qr-branding.com/.well-known/oauth-protected-resource
- Authorization servers
- https://qr-branding.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://qr-branding.com/mcp: tools/list returned 11 tools to an anonymous client, including qr_generate (write), qr_scan_check (write), qr_generate_ai (write), qr_poster (write), qr_generate_from_template (write) and 3 more
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 6 to 8
- RFC 9728 protected resource metadata: none to https://qr-branding.com/.well-known/oauth-protected-resource
- Authorization servers: none to https://qr-branding.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Findings
Matches of fixed checks, with the text they matched.
- Warnqr_generate
The server marks "qr_generate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "qr_generate" says "generate": a word for a change.
- Warnqr_scan_check
The server marks "qr_scan_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.
The server marks "qr_generate_from_template" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "qr_generate_from_template" says "generate": a word for a change.
- Infoqr_build_wifi
The description mentions "credentials".
What this check looks forMatched text
description: "Encode Wi-Fi credentials (SSID, password, auth type, hidden flag..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 8; RFC 9728 protected resource metadata: none -> https://qr-branding.com/.well-known/oauth-protected-resource; Authorization servers: none -> https://qr-bran…View diff
- Tools that change things, listed without credentials: 6 to 8
- RFC 9728 protected resource metadata: none to https://qr-branding.com/.well-known/oauth-protected-resource
- Authorization servers: none to https://qr-branding.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Tools1 added.+1 addedView diff
- Added:qr_list_ai_providersOnly reads
Tools2 added.+2 addedView diff
- Added:qr_get_templateOnly reads
- Added:qr_posterChanges things
Tools1 added.+1 addedView diff
- Added:qr_scan_checkChanges things
Tools6 changed.~6 changedView diff
- Changed:qr_build_geoChanges thingsdescription
- Changed:qr_build_vcardChanges thingsdescription
- Changed:qr_build_wifiChanges thingsdescription
- Changed:qr_generateChanges thingsdescription
- Changed:qr_generate_aiChanges thingsdescription
- Changed:qr_generate_from_templateChanges thingsdescription
Install
Pinned to version 0.2.8. Values in angle brackets are yours to fill in.
claude mcp add --transport http qr-branding https://qr-branding.com/mcpclaude mcp add --transport http qr-branding https://qr-branding.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__qr-branding__qr_get_template",
"mcp__qr-branding__qr_list_templates",
"mcp__qr-branding__qr_list_ai_providers"
],
"ask": [
"mcp__qr-branding__qr_generate",
"mcp__qr-branding__qr_scan_check",
"mcp__qr-branding__qr_generate_ai",
"mcp__qr-branding__qr_poster",
"mcp__qr-branding__qr_generate_from_template",
"mcp__qr-branding__qr_build_wifi",
"mcp__qr-branding__qr_build_vcard",
"mcp__qr-branding__qr_build_geo"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as qr-branding. Review it before you use it.
Capability tags behind 3 rules
- mcp__qr-branding__qr_list_templates untrusted-input
- mcp__qr-branding__qr_build_vcard outbound
- mcp__qr-branding__qr_list_ai_providers untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.quartzondev/qr-branding/verify?hash=98ac3aa769e059a50a53c972bfdcd04062213b0d9d81bb1a506286e266a7588f" | jq -e '.changed == false'Pinned hash 98ac3aa769e0, from Nov 14, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.quartzondev/qr-branding/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.quartzondev/qr-branding)Source: MCP Registry · repository. Synced Nov 14, 2026, 00:17 UTC.
QR Branding MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the QR Branding MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 8 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the QR Branding MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the QR Branding MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the QR Branding MCP server have?
- 11 tools: 8 write, 3 read. qr_generate, qr_scan_check, qr_generate_ai, qr_poster, qr_generate_from_template, qr_build_wifi, qr_build_vcard, qr_build_geo and 3 more.
Does the QR Branding MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the QR Branding MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): qr_build_vcard.
Has the QR Branding MCP server changed its tools?
- Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.