Skip to content

qr: QR codes that never expire MCP server

io.github.mandymozart/qrmandymozartstreamable-httpv1.0.0Scanned

Free dynamic QR codes that never expire: retarget later, styles, scan stats. No API key needed.

6 tools: 4 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 4 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 2
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

4 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.
Govern this server →

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: QR codes that never expire MCP server can do

The qr: QR codes that never expire MCP server is published by the GitHub account mandymozart. It has 6 tools. It can create or change data (4 tools: create_qr_code, update_qr_code, get_qr_code_stats and create_qr_codes_bulk), but cannot delete data. 2 tools only read.

2 tools can send data out of your system (create_qr_code and update_qr_code).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.0.0.

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.

6 tools

Changes things 4Claude Code: ask
  • create_qr_codeCreate a dynamic QR code for a link.Can send data outNo findings

    Why it is in this group

    • The name "create_qr_code" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.target_url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Create a dynamic QR code for a link. The code never expires and its target can be changed later. Returns the short URL, PNG/SVG image URLs and the QR image. Without an API key it also returns an edit_url: give that to the user, it is their only way to change the code later.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_qr_codes_bulkCreate several codes at once, optionally in a new campaign (e.g.No findings

    Why it is in this group

    • The name "create_qr_codes_bulk" says "create": a word for a change.
    Description, as the server wrote it
    Create several codes at once, optionally in a new campaign (e.g. one code per poster location). Needs an API key; the maximum per call depends on the plan.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • get_qr_code_statsScans, daily unique visitors, scans per day, top cities and devices of a code.1 finding

    Why it is in this group

    • The name "get_qr_code_stats" says "get": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "get_qr_code_stats" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "get_qr_code_stats" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Scans, daily unique visitors, scans per day, top cities and devices of a code. Anonymous and privacy-friendly (no IPs, no cookies).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • update_qr_codeChange the target URL (or title, or pause/activate) of an existing code.Can send data outNo findings

    Why it is in this group

    • The name "update_qr_code" says "update": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.

    What it can reach

    • outboundThe input takes a URL (input.target_url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Change the target URL (or title, or pause/activate) of an existing code. Printed copies keep working and now lead to the new target. Needs the API key of the owner or the edit_url of an anonymous code.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • get_limitsShows the current plan (anonymous, free or pro) and its quotas.No findings

    Why it is in this group

    • The name "get_limits" says "get": a word for reading.
    Description, as the server wrote it
    Shows the current plan (anonymous, free or pro) and its quotas.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_qr_codesList the codes of the account behind the API key, newest first, with scan counts.No findings

    Why it is in this group

    • The name "list_qr_codes" says "list": a word for reading.
    Description, as the server wrote it
    List the codes of the account behind the API key, newest first, with scan counts. Needs an API key.

    Annotations the server declares

    • readOnlyHint: 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 or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:20 UTC, unchanged since Nov 20, 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
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://qr.viennastruggle.at/mcp: tools/list returned 6 tools to an anonymous client, including create_qr_code (write), update_qr_code (write), get_qr_code_stats (write), create_qr_codes_bulk (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "get_qr_code_stats" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "get_qr_code_stats" says "get": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http qr https://qr.viennastruggle.at/mcp
claude mcp add --transport http qr https://qr.viennastruggle.at/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__qr__list_qr_codes",
      "mcp__qr__get_limits"
    ],
    "ask": [
      "mcp__qr__create_qr_code",
      "mcp__qr__update_qr_code",
      "mcp__qr__get_qr_code_stats",
      "mcp__qr__create_qr_codes_bulk"
    ],
    "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. Review it before you use it.

Capability tags behind 2 rules
  • mcp__qr__create_qr_code outbound
  • mcp__qr__update_qr_code outbound

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.mandymozart/qr/verify?hash=d5e653c818d266334ad367118f24f888047647da334214be85d4906c9b18a797" | jq -e '.changed == false'

Pinned hash d5e653c818d2, from Nov 20, 2026, 12: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.mandymozart/qr/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.mandymozart/qr
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.mandymozart/qr.svg)](https://radar.anlyon.com/servers/io.github.mandymozart/qr)

Source: MCP Registry · repository. Synced Nov 20, 2026, 12:17 UTC.

qr: QR codes that never expire MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the qr: QR codes that never expire MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 1 finding 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: QR codes that never expire 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: QR codes that never expire 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: QR codes that never expire MCP server have?

6 tools: 4 write, 2 read. create_qr_code, update_qr_code, get_qr_code_stats, create_qr_codes_bulk, list_qr_codes and get_limits.

Does the qr: QR codes that never expire MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the qr: QR codes that never expire MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_qr_code and update_qr_code.

Has the qr: QR codes that never expire MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.