Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TheQRCode.io

REMOTE · MCP.THEQRCODE.IO

Free styled QR codes, no key: URL, WiFi, contact, text, email. API key adds saved codes + analytics.

Available components

0 this week 75 Trust /100

Last scanned (31 minutes ago)

Scores higher than 62% of remote servers

Reachable. Last reached 22 Nov 2026.

Category Design and Media

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 765 tokens (~255/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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 →

Changelog

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.

  • 10 Nov 26 0
    • Stability: 0.97 → pass security
  • 9 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 17 Oct 26 0
    • Stability: 0.97 → pass security
  • 16 Oct 26 0
    • Stability: pass → 0.97 functional
  • 13 Oct 26 0
    • Server version: 1.5.1 → 1.5.2 functional
  • 11 Oct 26 0
    • Stability: 0.97 → pass security
    • Server version: 1.5.0 → 1.5.1 functional
  • 9 Oct 26 0
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • Server version: 1.4.0 → 1.5.0 functional
Diagnostics

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 22 Nov 2026 · Probed https://mcp.theqrcode.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.theqrcode.io CN=YR2,O=Let's Encrypt,C=US 12 Oct 2026 10 Jan 2027 RSA 4096 SHA256-RSA 6a2db0858307354ef8d67ce61dc5d32c4e8
SANs: mcp.theqrcode.io
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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 mcp.theqrcode.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
theqrcode.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.theqrcode.io/mcp Verified 200
http (plaintext) http://mcp.theqrcode.io/mcp HTTPS enforced 301 https://mcp.theqrcode.io/mcp
MCP tools · 3 exposed · ~765 tokens

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 →

Tool Tokens
generate_qr_code ~597

Generate a QR code image. Use this whenever a user asks to create, make, or generate a QR code for a URL, website, WiFi network, contact card, email, or text. Returns a hosted image URL and a base64 data URL for inline display. Colour, size, dot and corner styling, frames and captions are free on every plan and with no key at all — offer them freely. When authenticated, the QR code is saved to the user's account and svg/pdf output becomes available.

NameTypeReqDescription
captionstring–Short text rendered under the code, e.g. 'Scan for the menu'. Forces a frame to be drawn, because the text needs a band to sit on. Free on every plan.
captionFontstring–Typeface for the caption. Defaults to 'inter' (bold sans). 'pacifico' and 'dancing-script' are scripts, 'permanent-marker' is handwritten, 'playfair-display' and 'roboto-slab' are serifs. Ignored wit…
contentstringyesThe data to encode. Examples: 'https://example.com' for url, 'WIFI:T:WPA;S:MyNetwork;P:secret;;' for wifi, plain text for text type.
cornerStylestring–Shape of the three large corner squares. Free on every plan.
darkColorstring–Hex color for dark QR modules, e.g. '#1a1a1a'. Defaults to '#000000'.
dotStylestring–Shape of the QR modules. Free on every plan, keyless sessions included.
formatstring–Output format, returned as a data URL of that type. Defaults to 'png'. svg and pdf REQUIRE an API key: vector and PDF are the most expensive render path, so they sit behind a per-key rate limit rathe…
frameStylestring–Draw a frame around the code. 'square' means no frame. Free on every plan.
lightColorstring–Hex color for the background, e.g. '#ffffff'. Defaults to '#FFFFFF'.
namestring–Display name when saving via the authenticated API. If omitted, a name is derived from type and content.
sizeinteger–Output image size in pixels (64–1024). Defaults to 256.
typestringyesQR code type. Use 'url' for web links, 'wifi' for network credentials (format: WIFI:T:WPA;S:<ssid>;P:<password>;;), 'contact' for vCard data, 'text' for arbitrary strings, 'email' for email addresses…

No output schema declared.

No examples provided.

get_analytics ~82

Get scan analytics for the authenticated user's QR codes. Optionally filter to a specific QR code by ID. Requires an authenticated API key (Developer plan).

NameTypeReqDescription
qrCodeIdstring–Filter analytics to a specific QR code ID. Omit for account-wide totals.
timeRangestring–Time range for analytics data. Defaults to '30d'.

No output schema declared.

No examples provided.

list_qr_codes ~86

List QR codes saved to the authenticated user's account. Supports pagination and filtering by type. Requires an authenticated API key (Developer plan).

NameTypeReqDescription
limitinteger–Number of QR codes per page (1–100). Defaults to 20.
pageinteger–Page number for pagination. Defaults to 1.
typestring–Filter by QR code type.

No output schema declared.

No examples provided.

Install

How do I install the TheQRCode.io MCP server?

TheQRCode.io is a hosted endpoint at https://mcp.theqrcode.io/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 · mcp.theqrcode.io

# add to Claude Code
claude mcp add --transport http io-theqrcode-qr-code-generator 'https://mcp.theqrcode.io/mcp'
Common questions

What is the TheQRCode.io MCP server?

TheQRCode.io is an MCP server listed in the public MCP registry as io.theqrcode/qr-code-generator. Free styled QR codes, no key: URL, WiFi, contact, text, email. API key adds saved codes + analytics. This page covers its hosted endpoint (https://mcp.theqrcode.io/mcp).

Is the TheQRCode.io MCP server safe to use?

TheQRCode.io scores 75 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 TheQRCode.io MCP server expose?

TheQRCode.io exposes 3 tools: generate_qr_code, list_qr_codes, get_analytics. Their descriptions and schemas cost roughly 765 tokens of context every time the server is loaded.

Does the TheQRCode.io MCP server require authentication?

No. We connected to TheQRCode.io without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the TheQRCode.io MCP server still maintained?

TheQRCode.io is still listed as active in the MCP registry. We last reached this channel on 22 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 TheQRCode.io MCP server?

VerifyMCP ran 12 checks on TheQRCode.io, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about TheQRCode.io: Authorization. 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.