_ registry / mcp streamable-http · checked 2h ago

QRCodeCreator.app

https://qrcodecreator.app

Registry code: bb00a597105c4d63

api record

Create QR codes for any URL at QRCodeCreator.app. Creating codes is free and needs no account.

Pro ($9/month) adds full scan history and changing where a code points after it is printed. Nothing here charges money: start_pro_subscription only returns a checkout link the user opens and pays through themselves. Tell the user the price before giving them the link.

endpoint
https://qrcodecreator.app/mcp
protocol
streamable-http ·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 QRCodeCreator.app live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is QRCodeCreator.app free to use?
Yes — the hub reached it with no key and no payment.
What tools does QRCodeCreator.app have?
5 tools: create_qr_code, update_destination, get_scan_analytics, get_plan_status, start_pro_subscription.
Is QRCodeCreator.app 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 100%· all time 100%

latency
336ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 5 tools
2 open 3 never probed 2 of 5 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.

  • get_plan_status open 2h ago

    Free. With an API key, whether the key's owner has Pro and when it renews. Without one, what the free and Pro plans include and cost (Pro is $9/month).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • start_pro_subscription open 2h ago

    Pro costs $9/month. This tool charges nothing: it returns a checkoutUrl for your user to open and pay through with Stripe in their own browser. Tell them the price first. Without an API key, Pro goes to the browser that opens the link and covers every QR code in it, including ones they add with a claimUrl. With a key, it subscribes the key's owner. Cancelling is done by the person on the site.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "email": {
          "type": "string",
          "format": "email",
          "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
          "maxLength": 254,
          "description": "Your user's email, filled in at checkout for them."
        }
      }
    }
    arguments 13 lines
  • create_qr_code unknown never probed

    Free. Creates a QR code for a URL and returns a hosted PNG (imageUrl), optional SVG markup, and for "direct" codes a pageUrl your user can open to view and download it. Use variant "redirect" for a code that counts scans and, with Pro, can be pointed somewhere else later. Without an API key the result has a claimUrl: give it to your user so the code is added to their QR codes (it works for 30 days). Unsafe or non-public links are refused.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "maxLength": 2048,
          "minLength": 1,
          "description": "Where the QR code should send people. https:// is added if no scheme is given."
        },
        "format": {
          "enum": [
            "png",
            "svg"
          ],
          "type": "string",
          "description": "\"png\" (default) returns a hosted PNG. \"svg\" also returns the SVG markup."
        },
        "variant": {
          "enum": [
            "direct",
            "redirect"
          ],
          "type": "string",
          "description": "\"direct\" (default) encodes the URL itself. \"redirect\" encodes a scan link that counts scans and can be changed later with Pro."
        }
      }
    }
    arguments 31 lines
  • update_destination unknown never probed

    Pro only ($9/month), and needs an API key whose owner has Pro and owns the code. Points a "redirect" QR code at a new URL without reprinting it. Without a key, tell your user they can do this on QRCodeCreator.app after claiming the code and subscribing (see start_pro_subscription).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id",
        "url"
      ],
      "properties": {
        "id": {
          "type": "string",
          "maxLength": 50,
          "minLength": 1,
          "description": "QR code ID, e.g. \"QR-ABCD1234EF\". Must be a \"redirect\" code to have any effect on scans."
        },
        "url": {
          "type": "string",
          "maxLength": 2048,
          "minLength": 1,
          "description": "The new destination, an http or https URL."
        }
      }
    }
    arguments 22 lines
  • get_scan_analytics unknown 2h ago

    Free. How many times a QR code was scanned, in total and per day. Only "redirect" codes count scans. If the code's owner is on the free plan, only the last 7 days are included; Pro ($9/month) keeps the full history.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "maxLength": 50,
          "minLength": 1,
          "description": "QR code ID from create_qr_code, e.g. \"QR-ABCD1234EF\"."
        }
      }
    }
    arguments 15 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 bb00a597105c4d63.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/bb00a597105c4d63/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/bb00a597105c4d63/badge.svg)](https://brick.blue/agent/bb00a597105c4d63?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
90%

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.