useqr-mcp

io.github.aaronte/useqr-mcpaarontestreamable-httpv1.0.0Scanned 22 hours ago

Static QR PNG/SVG for agents. Designer and dynamic codes live at useqr.co.

3 tools: 2 change things and 1 only read.

Reads private data · 0
Reads text others write · 1
Can send data out · 1
No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

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.

3 tools

Changes things 2Creates or changes something that can be changed back.Claude Code: ask

create_dynamic_qr_codeExplains how to create a dynamic QR code on useqr: a trackable short link (free account).No findings
Why it is in this group
- The name "create_dynamic_qr_code" says "create": a word for a change.
Description, as the server wrote it
Explains how to create a dynamic QR code on useqr: a trackable short link (free account). Destination edits, version history, and scan analytics require Pro. Use this when a user needs scan tracking or wants to change a printed code's destination later. Returns instructions and links rather than creating the code directly.
generate_qr_codeGenerate a scannable QR code image (PNG or SVG) for a URL or any text.No findings
Why it is in this group
- The name "generate_qr_code" says "generate": a word for a change.
Description, as the server wrote it
Generate a scannable QR code image (PNG or SVG) for a URL or any text. Free, no account needed, and the code never expires. Use this whenever a user needs a QR code — for a website, Wi-Fi note, event link, menu, payment link, app download, business card, and so on.

Only reads 1Looks things up and changes nothing.Show 1 read-only tool

get_qr_designer_linkGet a link to the free useqr design studio, optionally prefilled with a URL.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "get_qr_designer_link" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it
Get a link to the free useqr design studio, optionally prefilled with a URL. The designer lets a user style dots, corners, and colors, embed a logo, and export the QR code as PNG, SVG, JPEG, WebP, or PDF. Share this link when a user wants a custom-designed or print-ready QR code.

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 write1: Brings in text someone else can write: web pages, inbound email, messages, issues and comments.; get_qr_designer_link
Can send data out1: Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.; get_qr_designer_link

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 Oct 22, 2026, 14:55 UTC, unchanged since Oct 22, 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: 2
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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
Matched text
https://useqr.co/api/mcp: tools/list returned 3 tools to an anonymous client, including generate_qr_code (write), create_dynamic_qr_code (write)
What this check looks for

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.

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

All changes to this server

Install

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

claude mcp add --transport http useqr https://useqr.co/api/mcp

claude mcp add --transport http useqr https://useqr.co/api/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": [],
    "ask": [
      "mcp__useqr__generate_qr_code",
      "mcp__useqr__get_qr_designer_link",
      "mcp__useqr__create_dynamic_qr_code"
    ],
    "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 useqr. Review it before you use it.

Capability tags behind 1 rule

mcp__useqr__get_qr_designer_link untrusted-input, outbound

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://anlyon.dev/api/v1/servers/io.github.aaronte/useqr-mcp/verify?hash=bc948083f7dda4a6d81dfb2e721883421f2b44b7ec1e18068adfa030cfed3643" | jq -e '.changed == false'

Pinned hash bc948083f7dd, from Oct 21, 2026, 19:05 UTC.

Watch

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

https://anlyon.dev/servers/io.github.aaronte/useqr-mcp/changes.xml

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

Badge

[![anlyon.dev](https://anlyon.dev/badge/io.github.aaronte/useqr-mcp.svg)](https://anlyon.dev/servers/io.github.aaronte/useqr-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:22 UTC.