QrVerloz
Server Details
QR codes active 90 days, claimable forever. Request an API key in chat to retarget and track scans.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 8 of 8 tools scored.
Each tool has a clearly distinct purpose: creating, deleting, retrieving, listing, updating target URL, getting scan counts, account info, and requesting an API key. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern in lower_snake_case (e.g., create_qr_code, delete_qr_code, update_qr_target). No mixing of conventions.
8 tools cover the essential operations for a QR code service (CRUD, analytics, account management, API key request) without being excessive or insufficient.
Core lifecycle is well-covered: create, read, update (target), delete, list, and scans. Missing potential features like editing QR code title/description or bulk operations, but not essential for the main use case.
Available Tools
8 toolscreate_qr_codeInspect
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 | Required | Description | Default |
|---|---|---|---|
| title | Yes | A human-readable label for the QR code | |
| target_url | Yes | Destination URL — must start with https:// or http:// |
delete_qr_codeInspect
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 | Required | Description | Default |
|---|---|---|---|
| qr_code_id | No | Internal UUID from create_qr_code or list_qr_codes | |
| short_code | No | Short code from the redirect URL (e.g. "abc123") | |
| confirm_title | Yes | The exact title of the QR code to delete — must match the stored title character-for-character. This prevents blind or injected deletions. |
get_account_infoInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_qr_codeInspect
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 | Required | Description | Default |
|---|---|---|---|
| qr_code_id | No | Internal UUID from create_qr_code or list_qr_codes | |
| short_code | No | Short code from the redirect URL (e.g. "abc123") |
get_qr_scansInspect
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 | Required | Description | Default |
|---|---|---|---|
| qr_code_id | Yes | Internal UUID of the QR code |
list_qr_codesInspect
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 | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (default: 1) | |
| limit | No | Items per page, max 20 (default: 20) |
request_api_keyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
update_qr_targetInspect
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 | Required | Description | Default |
|---|---|---|---|
| qr_code_id | No | Internal UUID from create_qr_code or list_qr_codes | |
| short_code | No | Short code from the redirect URL (e.g. "abc123") | |
| target_url | Yes | New destination URL — must start with https:// or http:// |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!