HonestQR
REMOTE · QR.ZALIZE.COM
Generate static QR codes (URL, WiFi, vCard, pixel art) and decode QR images. Codes never expire.
Available components
Last scanned (23 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Design and Media
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 9 Oct 26 +1
- DNSSEC: fail → pass ▲ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 5 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
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 4 Nov 2026 · Probed https://qr.zalize.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zalize.com | CN=WE1,O=Google Trust Services,C=US | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a1d6c25991800a960e78f2eebbd26ea8 |
| SANs: zalize.com, qr.zalize.com, *.qr.zalize.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of qr.zalize.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| zalize.com. | present | 2371 | 13 | Verified |
| qr.zalize.com. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://qr.zalize.com/mcp | HTTP error | 404 | |
| http (plaintext) | http://qr.zalize.com/mcp | HTTPS enforced | 301 | https://qr.zalize.com/mcp |
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 →
decode_qr Decode QR code ~66
Decode a QR code from a PNG image (base64). Returns the raw payload and its detected content type (url, wifi, vcard, sms, geo, event, ...).
| Name | Type | Req | Description |
|---|---|---|---|
| image_base64 | string | yes | Base64-encoded PNG image (data URI prefix allowed) |
No output schema declared.
No examples provided.
generate_pixel_art_qr Generate pixel-art QR code ~301
Generate an artistic QR code with pixel art embedded via a halftone technique: pixel text (up to 8 Latin characters/digits) or one of the built-in pixel icons, plus optional gradient color themes. The QR stays fully scannable (error correction H + server-side decode verification). Use list_icons and list_themes to see available options.
| Name | Type | Req | Description |
|---|---|---|---|
| bg | string | – | Background hex color, default #ffffff |
| data | string | – | Payload for type url (the link) or text (free text) |
| event | object | – | Calendar event fields (type event) |
| fg | string | – | Foreground hex color, default #0f172a |
| format | string | – | – |
| geo | object | – | Coordinates (type geo) |
| icon | string | – | Pixel icon id from list_icons (used when text is not given) |
| size | integer | – | Approximate PNG size in px |
| sms | object | – | SMS fields (type sms) |
| text | string | – | Pixel text to embed (A-Z, 0-9, basic punctuation) |
| theme | string | – | Theme id from list_themes. Overrides fg/bg. |
| type | string | yes | QR content type |
| vcard | object | – | Contact card fields (type vcard) |
| object | – | WhatsApp fields (type whatsapp) | |
| wifi | object | – | Wi-Fi credentials (type wifi) |
No output schema declared.
No examples provided.
generate_qr Generate QR code ~274
Generate a scannable QR code (PNG or SVG) for a URL, plain text, Wi-Fi login, contact card (vCard), SMS, WhatsApp, map location, or calendar event. Every result is decode-verified server-side before it is returned. Free, no API key. Powered by HonestQR (https://qr.zalize.com).
| Name | Type | Req | Description |
|---|---|---|---|
| bg | string | – | Background hex color, default #ffffff |
| data | string | – | Payload for type url (the link) or text (free text) |
| ecLevel | string | – | Error correction level |
| event | object | – | Calendar event fields (type event) |
| fg | string | – | Foreground hex color, default #0f172a |
| format | string | – | – |
| geo | object | – | Coordinates (type geo) |
| size | integer | – | Approximate PNG size in px |
| sms | object | – | SMS fields (type sms) |
| theme | string | – | Theme id from list_themes (colors + optional gradient). Overrides fg/bg. |
| type | string | yes | QR content type |
| vcard | object | – | Contact card fields (type vcard) |
| object | – | WhatsApp fields (type whatsapp) | |
| wifi | object | – | Wi-Fi credentials (type wifi) |
No output schema declared.
No examples provided.
list_icons List pixel icons ~34
List the built-in pixel icon ids for generate_pixel_art_qr, with an ASCII preview of each 16x16 icon.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_themes List QR color themes ~30
List the available color themes (solid and gradient) for generate_qr and generate_pixel_art_qr.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the HonestQR MCP server?
HonestQR is a hosted endpoint at https://qr.zalize.com/mcp, 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 · qr.zalize.com
claude mcp add --transport http com-zalize-qr-honestqr 'https://qr.zalize.com/mcp'
What is the HonestQR MCP server?
HonestQR is an MCP server listed in the public MCP registry as com.zalize.qr/honestqr. Generate static QR codes (URL, WiFi, vCard, pixel art) and decode QR images. Codes never expire. This page covers its hosted endpoint (https://qr.zalize.com/mcp).
Is the HonestQR MCP server safe to use?
HonestQR scores 24 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 HonestQR MCP server expose?
HonestQR exposes 5 tools: generate_qr, generate_pixel_art_qr, decode_qr, list_themes, list_icons. Their descriptions and schemas cost roughly 705 tokens of context every time the server is loaded.
Does the HonestQR MCP server require authentication?
Its publisher declares no required credentials for HonestQR. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the HonestQR MCP server still maintained?
HonestQR is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.