Skip to content

Pretty QR MCP server

com.pretty-qr/pretty-qrpretty-qr.comstreamable-httpv1.0.1Scanned

Create branded QR codes from AI assistants: templates, styled PNG/SVG, and editor links.

4 tools: 3 change things and 1 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

3 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 Pretty QR MCP server can do

The Pretty QR MCP server is published by pretty-qr.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (3 tools: create_qr_code, create_file_upload and open_in_editor), but cannot delete data. 1 tool only reads.

1 tool brings in text other people can write (list_templates).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 2026, version 1.0.1.

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.

4 tools

Changes things 3Claude Code: ask
  • create_file_uploadStart hosting a photo, video, audio file or PDF for a hosted file QR code (up to 10 files per account).No findings

    Why it is in this group

    • The name "create_file_upload" says "create": a word for a change.
    Description, as the server wrote it
    Start hosting a photo, video, audio file or PDF for a hosted file QR code (up to 10 files per account). Returns a one-time upload_url (valid 30 minutes) and the file_url the file will have. Upload the raw file with the returned curl command, then call create_qr_code with content set to file_url. Counts as one QR API request.
  • create_qr_codeMake the QR code file Download makes in the Pretty QR editor: a 2048 px PNG or an SVG.No findings

    Why it is in this group

    • The name "create_qr_code" says "create": a word for a change.
    Description, as the server wrote it
    Make the QR code file Download makes in the Pretty QR editor: a 2048 px PNG or an SVG. Counts as one QR API request.
  • open_in_editorSave the design to the account of the API key and return a link that opens it in the Pretty QR editor.No findings

    Why it is in this group

    • The name "open_in_editor" says "open": a word for a change.
    Description, as the server wrote it
    Save the design to the account of the API key and return a link that opens it in the Pretty QR editor. Counts as one QR API request.
Only reads 1Show 1 read-only tool
  • list_templatesThe Pretty QR templates: id, name, description and a preview image URL.Reads text others writeNo findings

    Why it is in this group

    • The name "list_templates" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    The Pretty QR templates: id, name, description and a preview image URL.

    Annotations the server declares

    • readOnlyHint: true

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

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
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 21, 2026, 19:22 UTC, unchanged since Nov 21, 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://pretty-qr.com/.well-known/oauth-protected-resource/api/mcp
Authorization servers
https://pretty-qr.com/api/auth
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
yes
  • WarnThe whole server

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

    Matched text

    https://pretty-qr.com/api/mcp: tools/list returned 4 tools to an anonymous client, including create_qr_code (write), create_file_upload (write), open_in_editor (write)

    What this check looks for

Posture changes

  1. Nov 21, 2026
    • RFC 9728 protected resource metadata: none to https://pretty-qr.com/.well-known/oauth-protected-resource/api/mcp
    • Authorization servers: none to https://pretty-qr.com/api/auth
    • Dynamic client registration: not observed to no
    • Client ID metadata documents: not observed to yes

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

  1. PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://pretty-qr.com/.well-known/oauth-protected-resource/api/mcp; Authorization servers: none -> https://pretty-qr.com/api/auth; Dynamic client registration: not observ…View diff
    • RFC 9728 protected resource metadata: none to https://pretty-qr.com/.well-known/oauth-protected-resource/api/mcp
    • Authorization servers: none to https://pretty-qr.com/api/auth
    • Dynamic client registration: not observed to no
    • Client ID metadata documents: not observed to yes

Install

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

claude mcp add --transport http pretty-qr https://pretty-qr.com/api/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http pretty-qr https://pretty-qr.com/api/mcp --header 'Authorization: <your-authorization>'

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__pretty-qr__list_templates"
    ],
    "ask": [
      "mcp__pretty-qr__create_qr_code",
      "mcp__pretty-qr__create_file_upload",
      "mcp__pretty-qr__open_in_editor"
    ],
    "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 pretty-qr. Review it before you use it.

Capability tags behind 1 rule
  • mcp__pretty-qr__list_templates 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/com.pretty-qr/pretty-qr/verify?hash=a3a49c249b61cde1eee559c1a2ffbc93e452fe57f1b01207959068a214ba67fa" | jq -e '.changed == false'

Pinned hash a3a49c249b61, from Nov 14, 2026, 20:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.pretty-qr/pretty-qr/changes.xml

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

Badge

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

Source: MCP Registry. Synced Nov 14, 2026, 20:17 UTC.

Pretty QR MCP server: questions and answers

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

Is the Pretty QR MCP server safe?

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

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

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

4 tools: 3 write, 1 read. create_qr_code, create_file_upload, open_in_editor and list_templates.

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

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

Does the Pretty QR MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Pretty QR MCP server changed its tools?

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