QrVerloz MCP server
io.github.neoshrek/qrverloz-mcpneoshrekstreamable-httpv1.0.0Scanned
QR codes active 90 days, claimable forever. Request an API key in chat to retarget and track scans.
8 tools: 1 can delete or cancel things, 3 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 2
- No 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.
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 QrVerloz MCP server can do
The QrVerloz MCP server is published by the GitHub account neoshrek. It has 8 tools. It can delete or cancel things (1 tool: delete_qr_code) and create or change data (3 tools: create_qr_code, update_qr_target and request_api_key). 4 tools only read.
2 tools can send data out of your system (create_qr_code and update_qr_target).
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 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.
8 tools
Deletes or cancels 1Claude Code: deny
delete_qr_codePermanently delete a QR code and its scan history.No findings
Why it is in this group
- The name "delete_qr_code" says "delete": a word for removing or ending something.
- The description says "Permanently delete".
Description, as the server wrote it Permanently delete a QR code and its scan history. This action cannot be undone. To prevent accidental or injected deletions, you MUST supply confirm_title — the exact title of the code as returned by get_qr_code or list_qr_codes. If the title does not match the stored record, the deletion is refused. Always call get_qr_code or list_qr_codes first to retrieve the exact title before calling this tool. Requires authentication.
Changes things 3Claude Code: ask
create_qr_codeCreate a new QR code.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 new QR code. Authenticated users (API key required) get a permanent short URL that can be retargeted at any time without reprinting the physical QR image — limits are set by the account plan. Anonymous users receive a one-time data URI image that is not stored and cannot be updated. On success the result is a pre-formatted markdown table — display it exactly as received, do not reformat or summarise.
request_api_keyGet a free API token — no account or email required.No findings
Why it is in this group
- The name "request_api_key" says "request": a word for a change.
Description, as the server wrote it Get a free API token — no account or email required. The token gives you up to 5 QR codes that can be updated at any time. IMPORTANT LIFETIME WARNING: the token expires after 90 days, and QR codes are permanently deleted ~90 days after that (~180 days total). To keep codes alive permanently, claim a free account at https://qrverloz.com/claim — this must be done before the token expires. Save the returned token: it is shown only once. Add it to your MCP client config under Authorization: Bearer, then call create_qr_code.
update_qr_targetChange the destination URL of a QR code without touching the printed image.Can send data outNo findings
Why it is in this group
- The name "update_qr_target" says "update": 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 Change the destination URL of a QR code without touching the printed image. Print once, redirect anywhere — forever. Accepts either the internal qr_code_id or the short_code from the redirect URL. On success the result is a pre-formatted markdown table — display it exactly as received, do not reformat or summarise. Requires authentication.
Only reads 4Show 4 read-only tools
get_account_infoGet your account details: current plan, QR code usage, and which features are available.No findings
Why it is in this group
- The name "get_account_info" says "get": a word for reading.
Description, as the server wrote it Get your account details: current plan, QR code usage, and which features are available. Use this before create_qr_code to check remaining capacity, or to confirm which features are active on your plan. Requires authentication.
get_qr_codeLook up a single QR code by its internal ID or short code.No findings
Why it is in this group
- The name "get_qr_code" says "get": a word for reading.
Description, as the server wrote it Look up a single QR code by its internal ID or short code. Returns a pre-formatted markdown table with fields: Title, ID, Short Code, Short URL, Destination, Status, Created, QR Code Link. Display the table exactly as received — do not reformat or summarise. Requires authentication.
get_qr_scansGet the total lifetime scan count for a QR code.No findings
Why it is in this group
- The name "get_qr_scans" says "get": a word for reading.
Description, as the server wrote it Get the total lifetime scan count for a QR code. Returns a pre-formatted markdown table with fields: Title, ID, Short Code, Short URL, Destination, Status, Created, QR Code Link, Total Scans. Display the table exactly as received — do not reformat or summarise. Requires authentication.
list_qr_codesList all QR codes in your account.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 all QR codes in your account. Returns one pre-formatted markdown table per QR code with fields: Title, ID, Short Code, Short URL, Destination, Status, Created, QR Code Link. Display each table exactly as received — do not reformat or summarise. Requires authentication.
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.
Looked at Nov 20, 2026, 19:08 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
- 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://qrverloz.com/api/mcp: tools/list returned 8 tools to an anonymous client, including delete_qr_code (destructive), create_qr_code (write), update_qr_target (write), request_api_key (write)
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.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http qrverloz https://qrverloz.com/api/mcpclaude mcp add --transport http qrverloz https://qrverloz.com/api/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__qrverloz__get_qr_code",
"mcp__qrverloz__list_qr_codes",
"mcp__qrverloz__get_qr_scans",
"mcp__qrverloz__get_account_info"
],
"ask": [
"mcp__qrverloz__create_qr_code",
"mcp__qrverloz__update_qr_target",
"mcp__qrverloz__request_api_key"
],
"deny": [
"mcp__qrverloz__delete_qr_code"
]
}
}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 qrverloz. Review it before you use it.
Capability tags behind 2 rules
- mcp__qrverloz__create_qr_code outbound
- mcp__qrverloz__update_qr_target 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.neoshrek/qrverloz-mcp/verify?hash=7bc72b7b44181f6645b52a9c9c1ee1c6804aa0420c72a266ebf5312d095bd37e" | jq -e '.changed == false'Pinned hash 7bc72b7b4418, from Nov 20, 2026, 04: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.neoshrek/qrverloz-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.neoshrek/qrverloz-mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:42 UTC.
QrVerloz MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the QrVerloz MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 4 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 QrVerloz MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: delete_qr_code.
Can the QrVerloz 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 QrVerloz MCP server have?
- 8 tools: 1 destructive, 3 write, 4 read. delete_qr_code, create_qr_code, update_qr_target, request_api_key, get_qr_code, list_qr_codes, get_qr_scans and get_account_info.
Does the QrVerloz MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the QrVerloz 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_target.
Has the QrVerloz MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.