Qrblox
REMOTE · API.QRBLOX.COM · 2 COMPONENTS
Create and track QR codes, audio codes, menus, and scan analytics for a Qrblox merchant.
Available components
Last scanned (11 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1363 tokens (~97/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://api.qrblox.com/mcp/v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.qrblox.com | CN=YR1,O=Let's Encrypt,C=US | 2 Nov 2026 | 31 Jan 2027 | RSA 2048 | SHA256-RSA | 52ba706bbc8cde78d44020daad37f159beb |
| SANs: api.qrblox.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.qrblox.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| qrblox.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="Qrblox MCP", resource_metadata="https://api.qrblox.com/.well-known/oauth-protected-resource"
Bearer realm="Qrblox MCP", resource_metadata="https://api.qrblox.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Protected resource metadata
| Document | https://api.qrblox.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.qrblox.com/mcp/v1 |
| Authorisation server | https://api.qrblox.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.qrblox.com/mcp/v1 | Verified | 200 | |
| http (plaintext) | http://api.qrblox.com/mcp/v1 | HTTPS enforced | 308 | https://api.qrblox.com/mcp/v1 |
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 →
qrblox.analytics.scan_summary ~42
Summarize recent scan activity for a merchant workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Lookback window in days, from 1 to 365. |
No output schema declared.
No examples provided.
qrblox.audio.create ~67
Create a draft audio code payload that can later be published as a near-ultrasonic sharing experience.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign | string | – | Optional campaign name. |
| payloadText | string | yes | Text or URL payload to encode. |
| title | string | yes | Human-readable audio code name. |
No output schema declared.
No examples provided.
qrblox.challenge.create ~86
Create a draft scan challenge, streak, game, or loyalty campaign.
| Name | Type | Req | Description |
|---|---|---|---|
| challengeType | string | yes | – |
| description | string | – | Optional description. |
| endsAt | string | – | Optional ISO end date. |
| name | string | yes | Challenge name. |
| rewardText | string | – | Optional reward copy. |
| startsAt | string | – | Optional ISO start date. |
No output schema declared.
No examples provided.
qrblox.menu.add_item ~72
Add an item to a section in an existing merchant menu.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional item description. |
| menuId | string | yes | Menu id. |
| name | string | yes | Item name. |
| price | number | – | Optional price. |
| sectionName | string | yes | Section name. |
No output schema declared.
No examples provided.
qrblox.menu.create ~60
Create a merchant menu that can be connected to QR codes, audio codes, and scan experiences.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional description. |
| locationId | string | – | Optional merchant location id. |
| name | string | yes | Menu name. |
No output schema declared.
No examples provided.
qrblox.menu.list ~34
List recent menus for the merchant.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum records to return, up to 100. |
No output schema declared.
No examples provided.
qrblox.merchant.get_profile ~25
Get the merchant workspace attached to this user or API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
qrblox.ping ~26
Confirm that the Qrblox MCP server is reachable for the authenticated merchant.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
qrblox.qr.create ~292
Create a finished QR code: returns a hosted PNG (qrImageUrl) plus, for dynamic codes, a qrb.dev dynamic link you can re-point later. Options: template wraps the code in a Qrblox hex frame; boostFrame renders a scan-to-earn reward frame (scans through the Qrblox app award boosted points); scanBeepSound makes the Qrblox app play that sound on every scan (forces dynamic). Plain calls with none of these return a simple static code.
| Name | Type | Req | Description |
|---|---|---|---|
| boostFrame | string | – | Scan-to-earn reward frame (3X/5X boosted points), rendered server-side. Overrides template. |
| campaign | string | – | Optional campaign name. |
| destinationUrl | string | yes | The URL the QR code should open. |
| dynamic | boolean | – | Encode a qrb.dev dynamic link instead of the raw URL — re-pointable later, trackable per scan. |
| scanBeepSound | string | – | Sound the Qrblox app plays when anyone scans this code (coin ding = mariocoin). Forces dynamic. |
| tags | array | – | – |
| template | string | – | Qrblox hex frame: hexSeal (candy hexagon + QRBLOX wordmark) or soundSeal (dashed ring + SOUND CODE label; forces dynamic). |
| title | string | yes | Human-readable name for the QR code. |
No output schema declared.
No examples provided.
qrblox.qr.get_analytics ~121
Per-code scan report from the Qrblox analytics pipeline: total scans, daily counts, and every scan with date and city/state. Works for dynamic codes and app-scanned codes (last 365 days max).
| Name | Type | Req | Description |
|---|---|---|---|
| codeId | string | – | Merchant record id returned by qr.create / qr.list. |
| days | number | – | Lookback window in days, 1-365 (default 30). |
| uniqueQRCodeID | string | – | Cross-platform id (the trailing part of the qrb.dev/qr/... link). |
No output schema declared.
No examples provided.
qrblox.qr.list ~36
List recent QR codes for the merchant.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum records to return, up to 100. |
No output schema declared.
No examples provided.
qrblox.qr.update ~154
Edit an existing QR code: re-point the destination URL (dynamic codes redirect immediately, no reprint), change the scan sound, or rename it. Identify the code by codeId (from qr.create/qr.list) or uniqueQRCodeID.
| Name | Type | Req | Description |
|---|---|---|---|
| codeId | string | – | Merchant record id returned by qr.create / qr.list. |
| destinationUrl | string | – | New destination URL (dynamic codes only take effect on print). |
| scanBeepSound | string | – | New scan sound, or 'none' to remove it. |
| title | string | – | New display name. |
| uniqueQRCodeID | string | – | Cross-platform id (the trailing part of the qrb.dev/qr/... link). |
No output schema declared.
No examples provided.
qrblox.voice_agent.lookup ~63
Look up a business in the Qrblox Voice Agent Phone Book by website domain — returns their confirmed AI voice agent phone number if registered.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Business website domain, like example.com (protocol, www, and paths are stripped). |
No output schema declared.
No examples provided.
qrblox.voice_agent.register ~127
Register a business's AI voice agent phone number and domain in the Qrblox Voice Agent Phone Book directory (free; creates a backlink page at qrblox.com/d/<domain> once approved).
| Name | Type | Req | Description |
|---|---|---|---|
| businessName | string | yes | Business name as it should appear in the phone book. |
| domain | string | yes | Business website domain, like example.com. |
| string | yes | Contact email — receives the confirmation once the claim is approved. | |
| voiceAgentPhone | string | yes | Phone number of the business's AI voice agent, like +12025551234. |
No output schema declared.
No examples provided.
How do I install the Qrblox MCP server?
Qrblox is a hosted endpoint at https://api.qrblox.com/mcp/v1, 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 · api.qrblox.com
claude mcp add --transport http com-qrblox-mcp 'https://api.qrblox.com/mcp/v1'
What is the Qrblox MCP server?
Qrblox is an MCP server listed in the public MCP registry as com.qrblox/mcp. Create and track QR codes, audio codes, menus, and scan analytics for a Qrblox merchant. This page covers its hosted endpoint (https://api.qrblox.com/mcp/v1).
Is the Qrblox MCP server safe to use?
Qrblox scores 85 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 Qrblox MCP server expose?
Qrblox exposes 14 tools: qrblox.ping, qrblox.voice_agent.lookup, qrblox.voice_agent.register, qrblox.merchant.get_profile, qrblox.qr.list, and 9 more. Their descriptions and schemas cost roughly 1,205 tokens of context every time the server is loaded.
Does the Qrblox MCP server require authentication?
Yes. Qrblox asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Qrblox MCP server still maintained?
Qrblox is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Qrblox MCP server?
VerifyMCP ran 13 checks on Qrblox, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.