QrVerloz
REMOTE · QRVERLOZ.COM · SCANNED SEP 20
QR codes active 90 days, claimable forever. Request an API key in chat to retarget and track scans.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 936 tokens (~117/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_qr_code" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the QrVerloz MCP server?
QrVerloz is a hosted endpoint at https://qrverloz.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · qrverloz.com
claude mcp add --transport http neoshrek-qrverloz-mcp 'https://qrverloz.com/api/mcp'
{
"mcpServers": {
"neoshrek-qrverloz-mcp": {
"url": "https://qrverloz.com/api/mcp"
}
}
} {
"servers": {
"neoshrek-qrverloz-mcp": {
"type": "http",
"url": "https://qrverloz.com/api/mcp"
}
}
} [mcp_servers.neoshrek-qrverloz-mcp] url = "https://qrverloz.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"neoshrek-qrverloz-mcp": {
"type": "remote",
"url": "https://qrverloz.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add neoshrek-qrverloz-mcp --url 'https://qrverloz.com/api/mcp' --transport streamable-http
mcp_servers:
neoshrek-qrverloz-mcp:
url: "https://qrverloz.com/api/mcp" {
"McpServers": {
"neoshrek-qrverloz-mcp": {
"Transport": "http",
"Url": "https://qrverloz.com/api/mcp"
}
}
} assistant mcp add neoshrek-qrverloz-mcp -t streamable-http -u 'https://qrverloz.com/api/mcp'
{
"mcpServers": {
"neoshrek-qrverloz-mcp": {
"type": "http",
"url": "https://qrverloz.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://qrverloz.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=qrverloz.com | CN=WE1,O=Google Trust Services,C=US | 12 Aug 2026 | 10 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | ca9b45582c161dcb0e9df51d768af1c9 |
| SANs: qrverloz.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of qrverloz.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| qrverloz.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://js.stripe.com https://cloud.umami.is; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://*.digitaloceanspaces.com https://*.cdn.digitaloceanspaces.com https://images.unsplash.com https://plus.unsplash.com; font-src 'self' data:; connect-src 'self' https://api.stripe.com https://q.stripe.com https://cloud.umami.is https://api-gateway.umami.dev; frame-src https://js.stripe.com; frame-ancestors 'none'; object-src 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://qrverloz.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://qrverloz.com/api/mcp | HTTPS enforced | 301 | https://qrverloz.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_qr_code ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| target_url | string | yes | Destination URL — must start with https:// or http:// |
| title | string | yes | A human-readable label for the QR code |
No output schema declared.
No examples provided.
delete_qr_code ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_title | string | yes | The exact title of the QR code to delete — must match the stored title character-for-character. This prevents blind or injected deletions. |
| qr_code_id | string | – | Internal UUID from create_qr_code or list_qr_codes |
| short_code | string | – | Short code from the redirect URL (e.g. "abc123") |
No output schema declared.
No examples provided.
get_account_info ~53
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_qr_code ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| qr_code_id | string | – | Internal UUID from create_qr_code or list_qr_codes |
| short_code | string | – | Short code from the redirect URL (e.g. "abc123") |
No output schema declared.
No examples provided.
get_qr_scans ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| qr_code_id | string | yes | Internal UUID of the QR code |
No output schema declared.
No examples provided.
list_qr_codes ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Items per page, max 20 (default: 20) |
| page | integer | – | Page number (default: 1) |
No output schema declared.
No examples provided.
request_api_key ~130
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
update_qr_target ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| qr_code_id | string | – | Internal UUID from create_qr_code or list_qr_codes |
| short_code | string | – | Short code from the redirect URL (e.g. "abc123") |
| target_url | string | yes | New destination URL — must start with https:// or http:// |
No output schema declared.
No examples provided.
What is the QrVerloz MCP server?
QrVerloz is an MCP server listed in the public MCP registry as io.github.neoshrek/qrverloz-mcp. QR codes active 90 days, claimable forever. Request an API key in chat to retarget and track scans. This page covers its hosted endpoint (https://qrverloz.com/api/mcp).
Is the QrVerloz MCP server safe to use?
QrVerloz scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the QrVerloz MCP server expose?
QrVerloz exposes 8 tools: create_qr_code, get_qr_code, list_qr_codes, get_qr_scans, update_qr_target, and 3 more. Their descriptions and schemas cost roughly 936 tokens of context every time the server is loaded.
Does the QrVerloz MCP server require authentication?
No. We connected to QrVerloz without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the QrVerloz MCP server still maintained?
QrVerloz is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.