Skip to content

QR Code Creator MCP server

app.qrcodecreator/qr-codesqrcodecreator.appstreamable-httpv1.6.0Scanned

Free QR codes for any URL with no signup or API key, plus scan analytics. Pro makes links editable.

6 tools: 1 can delete or cancel things, 2 change things and 3 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • 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 Code Creator MCP server can do

The QR Code Creator MCP server is published by qrcodecreator.app, a domain the MCP Registry verified. It has 6 tools. It can delete or cancel things (1 tool: update_destination) and create or change data (2 tools: create_qr_code and start_pro_subscription). 3 tools only read.

1 tool can send data out of your system (create_qr_code).

The fixed checks matched 2 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 9 times since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 1.6.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

Deletes or cancels 1Claude Code: deny
  • update_destinationChanges the URL a "redirect" QR code sends people to, so a printed code can point somewhere new.No findings

    Why it is in this group

    • The name "update_destination" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Changes the URL a "redirect" QR code sends people to, so a printed code can point somewhere new. Requires Pro ($9/month) and the code's owner: signed in (OAuth) or an API key (Authorization: Bearer qrcd_...) whose owner owns the code. If the owner doesn't have Pro, it returns pro_required; if the code belongs to someone else, not_owner. The new URL gets the same safety checks as create_qr_code.

    Annotations the server declares

    • title: Change where a QR code points
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 2Claude Code: ask
  • create_qr_codeFree.Can send data out1 finding

    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.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...orts public HTTP/HTTPS links, not Wi-Fi credentials, contact cards, arbitrary text or decod..."

      What this check looks for
    Description, as the server wrote it
    Free. Creates a scannable QR code from a website URL, such as a restaurant menu, event page, business website or product link, with no account or API key required. Returns the PNG image, download links on QRCodeCreator.app for the PNG (imageUrl) and SVG (svgUrl), the SVG markup when format is "svg", and a pageUrl where the code can be viewed and downloaded for sharing or printing. Requires a destination URL; supports public HTTP/HTTPS links, not Wi-Fi credentials, contact cards, arbitrary text or decoding an existing QR image. Every code encodes a scan link (scanUrl) on QRCodeCreator.app that counts scans and forwards to the URL, so its destination can be changed later by an owner with Pro without reprinting. Signed in or with an API key, the code belongs to that account. Otherwise the result includes a claimUrl, valid for 30 days, that adds the code to the QR codes of whoever opens it on QRCodeCreator.app. Unsafe links and links to private or internal hosts are refused with an error that names the reason.

    Annotations the server declares

    • title: Create a QR code
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • start_pro_subscriptionPro costs $9/month.1 finding

    Why it is in this group

    • The name "start_pro_subscription" says "start": 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 "start_pro_subscription" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "start_pro_subscription" says "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Pro costs $9/month. Returns a checkoutUrl for the Pro subscription, with the plan and its price. Getting the link is free: it charges nothing and changes no account; a subscription starts only if a person opens the link and completes Stripe checkout in their browser. Signed in or with an API key, Pro applies to that account; otherwise it applies to the browser that completes checkout, including codes added to it with a claimUrl. If that account already has Pro, returns alreadyPro: true and no link.

    Annotations the server declares

    • title: Get a Pro checkout link
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_plan_statusFree.No findings

    Why it is in this group

    • The name "get_plan_status" says "get": a word for reading.
    Description, as the server wrote it
    Free. Signed in (OAuth) or with an API key, returns whether that account has Pro, the subscription status and when the current period ends. Otherwise, returns what the free and Pro plans include and the Pro price ($9/month).

    Annotations the server declares

    • title: Get plan status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_scan_analyticsFree.No findings

    Why it is in this group

    • The name "get_scan_analytics" says "get": a word for reading.
    Description, as the server wrote it
    Free. Returns how many times a QR code was scanned, in total and per UTC day. Needs no API key: the counts for a code can be read by anyone with its ID. If the code's owner does not have Pro ($9/month), only the last 7 days are included (historyDays in the result); with Pro, the full history is.

    Annotations the server declares

    • title: Get scan analytics
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_qr_codesFree.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
    Free. Lists the QR codes in the signed-in account (or the API key owner's), newest first, optionally only those whose name or destination URL contains a search term, such as "lunch menu" or "example.com/events". Returns each code's id, name (set on QRCodeCreator.app; null if unnamed), current destination url, createdAt, scanUrl and manageUrl, plus total and truncated. The id works with get_scan_analytics and update_destination. Needs sign-in (OAuth) or an API key, and lists only that account's codes. At most 50 codes per call.

    Annotations the server declares

    • title: List my QR codes
    • 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 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 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.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:21 UTC, unchanged since Nov 19, 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
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://qrcodecreator.app/.well-known/oauth-protected-resource/mcp
Authorization servers
https://qrcodecreator.app
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

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

    Matched text

    https://qrcodecreator.app/mcp: tools/list returned 5 tools to an anonymous client, including update_destination (destructive), create_qr_code (write), start_pro_subscription (write)

    What this check looks for

Posture changes

  1. Nov 19, 2026
    • RFC 9728 protected resource metadata: none to https://qrcodecreator.app/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://qrcodecreator.app
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Findings

Matches of fixed checks, with the text they matched.

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

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "start_pro_subscription" says "start": a word for a change.

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...orts public HTTP/HTTPS links, not Wi-Fi credentials, contact cards, arbitrary text or decod..."

    What this check looks for

History

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

  1. Tools6 changed.~6 changedView diff
  2. Tools1 added, 1 changed.+1 added~1 changedView diff
  3. PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://qrcodecreator.app/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://qrcodecreator.app; Dynamic client registration: not observed ->…View diff
    • RFC 9728 protected resource metadata: none to https://qrcodecreator.app/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://qrcodecreator.app
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes
  4. Tools3 changed.~3 changedView diff
  5. Tools1 added.+1 addedView diff
  6. Tools1 changed.~1 changedView diff
  7. Tools4 changed.~4 changedView diff
  8. Tools4 changed.~4 changedView diff
  9. Tools1 removed.−1 removedView diff
    • Removed:update_destination
  10. Tools5 changed.~5 changedView diff

Install

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

claude mcp add --transport http qr-codes https://qrcodecreator.app/mcp
claude mcp add --transport http qr-codes https://qrcodecreator.app/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-codes__get_scan_analytics",
      "mcp__qr-codes__list_qr_codes",
      "mcp__qr-codes__get_plan_status"
    ],
    "ask": [
      "mcp__qr-codes__create_qr_code",
      "mcp__qr-codes__start_pro_subscription"
    ],
    "deny": [
      "mcp__qr-codes__update_destination"
    ]
  }
}

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-codes. Review it before you use it.

Capability tags behind 1 rule
  • mcp__qr-codes__create_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/app.qrcodecreator/qr-codes/verify?hash=f7e711b6645865a8444f0f08fe6dbb5dcb138a4dad6dc627d5c1e8932767e5db" | jq -e '.changed == false'

Pinned hash f7e711b66458, from Nov 21, 2026, 17:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.qrcodecreator/qr-codes/changes.xml

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

Badge

Anlyon Radar badge for app.qrcodecreator/qr-codes
[![Anlyon Radar](https://radar.anlyon.com/badge/app.qrcodecreator/qr-codes.svg)](https://radar.anlyon.com/servers/app.qrcodecreator/qr-codes)

Source: MCP Registry. Synced Nov 21, 2026, 18:17 UTC.

QR Code Creator MCP server: questions and answers

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

Is the QR Code Creator MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 2 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 Code Creator MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: update_destination.

Can the QR Code Creator 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 Code Creator MCP server have?

6 tools: 1 destructive, 2 write, 3 read. update_destination, create_qr_code, start_pro_subscription, get_scan_analytics, list_qr_codes and get_plan_status.

Does the QR Code Creator MCP server need sign-in or OAuth?

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

Does the QR Code Creator 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): create_qr_code.

Has the QR Code Creator MCP server changed its tools?

Yes, 9 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.