_ registry / mcp http-sse · checked 1h ago

QrVerloz

https://qrverloz.com

Registry code: 5dfba557ab9afd24

api record

QR codes active 90 days, claimable forever. Request an API key in chat to retarget and track scans.

from a public catalogue that lists it, not from the operator

endpoint
https://qrverloz.com/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is QrVerloz live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is QrVerloz free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does QrVerloz have?
8 tools: get_qr_scans, create_qr_code, get_qr_code, list_qr_codes, get_account_info, update_qr_target, delete_qr_code, request_api_key.
Is QrVerloz safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.5%· all time 99.5%

latency
411ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 373 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • create a qr code
  • retarget a qr code url
  • get qr code scan count
takes → gives
text, web pages → data, images
tools
4 reads4 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
7 auth-required 1 never probed 7 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • create_qr_code changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "title",
        "target_url"
      ],
      "properties": {
        "title": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "A human-readable label for the QR code"
        },
        "target_url": {
          "type": "string",
          "format": "uri",
          "description": "Destination URL — must start with https:// or http://"
        }
      }
    }
    arguments 21 lines
  • get_qr_code reads auth-required 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "qr_code_id": {
          "type": "string",
          "description": "Internal UUID from create_qr_code or list_qr_codes"
        },
        "short_code": {
          "type": "string",
          "description": "Short code from the redirect URL (e.g. \"abc123\")"
        }
      }
    }
    arguments 14 lines
  • list_qr_codes reads auth-required 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "page": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 1,
          "description": "Page number (default: 1)"
        },
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Items per page, max 20 (default: 20)"
        }
      }
    }
    arguments 18 lines
  • get_account_info reads auth-required 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • update_qr_target changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "target_url"
      ],
      "properties": {
        "qr_code_id": {
          "type": "string",
          "description": "Internal UUID from create_qr_code or list_qr_codes"
        },
        "short_code": {
          "type": "string",
          "description": "Short code from the redirect URL (e.g. \"abc123\")"
        },
        "target_url": {
          "type": "string",
          "format": "uri",
          "description": "New destination URL — must start with https:// or http://"
        }
      }
    }
    arguments 22 lines
  • delete_qr_code changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "confirm_title"
      ],
      "properties": {
        "qr_code_id": {
          "type": "string",
          "description": "Internal UUID from create_qr_code or list_qr_codes"
        },
        "short_code": {
          "type": "string",
          "description": "Short code from the redirect URL (e.g. \"abc123\")"
        },
        "confirm_title": {
          "type": "string",
          "minLength": 1,
          "description": "The exact title of the QR code to delete — must match the stored title character-for-character. This prevents blind or injected deletions."
        }
      }
    }
    arguments 22 lines
  • request_api_key changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_qr_scans reads unknown 12h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "qr_code_id"
      ],
      "properties": {
        "qr_code_id": {
          "type": "string",
          "description": "Internal UUID of the QR code"
        }
      }
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5dfba557ab9afd24.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5dfba557ab9afd24/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5dfba557ab9afd24/badge.svg)](https://brick.blue/agent/5dfba557ab9afd24?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.