Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.

Is lnx-qr 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.

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

lnx-qr

https://qr.lnx.net

Registry code: af3824717bb0e7c7

api record

LNX QR makes designed QR codes: twelve tested styles, fifteen frames with a call to action such as "SCAN ME", and custom colors. Use create_qr_code when the user wants a QR code for a website, menu, business card, flyer, product, event or contact. Show the returned image and give the user png_url (print size) and edit_url (to fine-tune it in the LNX QR studio).

endpoint: https://qr.lnx.net/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 lnx-qr live?: Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is lnx-qr free to use?: Not measured yet.
What tools does lnx-qr have?: 1 tool: create_qr_code.
Is lnx-qr 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

98.3%

90 days 98.9%· all time 98.9%

latency

317ms

last good check

priced tools

of 1 tools

_ answered our checks, 90 days 278 checks · signed record

2026-11-13 22:46 degraded → live
2026-11-12 13:17 live → degraded· timeout after 20000ms
2026-10-20 16:37 degraded → live
2026-10-20 14:16 live → degraded· timeout after 20000ms
2026-10-12 10:40 degraded → live

_ what it is for

topic: media generation images
used for: create a styled qr code for a link
make a qr code with a call-to-action frame
takes → gives: text → images
tools: 1 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

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 1 tools

1 never probed 0 of 1 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 unknown never probed

Creates a styled QR code for a link, text, email address or phone number and returns the image, a print-size PNG link and a link to edit it in the LNX QR studio. Choose a style and an optional frame with a short call to action (e.g. "SCAN FOR MENU").

mcp-tool

{
  "type": "object",
  "required": [
    "content"
  ],
  "properties": {
    "color": {
      "type": "string",
      "description": "Optional hex color for the code itself, e.g. #1e3a8a; overrides the style's colors. Must be dark."
    },
    "frame": {
      "enum": [
        "none",
        "outline",
        "label-bottom",
        "label-top",
        "button",
        "solid-card",
        "corners",
        "ticket",
        "tag",
        "minimal",
        "phone",
        "bubble",
        "double",
        "banner",
        "arrow"
      ],
      "type": "string",
      "description": "Frame around the code. none (default) or outline have no text; label-bottom, label-top, button, solid-card, ticket, tag, bubble, banner, arrow, corners, minimal, phone, double show frame_text."
    },
    "style": {
      "enum": [
        "classic",
        "rounded",
        "dots",
        "violet",
        "peach",
        "forest",
        "sand",
        "sky",
        "sunset",
        "rose",
        "ink-dots",
        "mint"
      ],
      "type": "string",
      "description": "Design. classic = plain black squares; rounded / dots = soft black shapes; violet, peach, forest, sunset = color gradients; sand, sky, rose, mint = single brand-like colors; ink-dots = black dots."
    },
    "content": {
      "type": "string",
      "description": "What the code opens: a URL, a text, an email address or a phone number (max 900 characters)."
    },
    "background": {
      "type": "string",
      "description": "Optional hex background color, e.g. #ffffff. Must be light."
    },
    "email_body": {
      "type": "string",
      "description": "email only: prefilled message."
    },
    "frame_font": {
      "enum": [
        "Inter",
        "Bebas Neue",
        "Oswald",
        "Playfair Display",
        "Archivo Black",
        "Righteous",
        "Space Mono"
      ],
      "type": "string"
    },
    "frame_text": {
      "type": "string",
      "description": "Call to action shown in the frame, max 24 characters, e.g. \"SCAN ME\", \"SCAN FOR MENU\"."
    },
    "content_type": {
      "enum": [
        "url",
        "text",
        "email",
        "phone"
      ],
      "type": "string",
      "description": "url (default), text, email (opens a new email) or phone (starts a call)."
    },
    "email_subject": {
      "type": "string",
      "description": "email only: prefilled subject."
    }
  }
}

arguments 93 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.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
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.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id af3824717bb0e7c7.

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

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/af3824717bb0e7c7/badge.svg)](https://brick.blue/agent/af3824717bb0e7c7?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

50%

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

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.

_ also on lnx.net 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

lnx.net lnx mcp · 2 tools