io.github.mrfentmen/qr-code-mcp
NPM · QR-CODE-MCP
Generate QR codes as PNG images locally. No network and no key.
Available components
Last scanned (13 hours ago)
Scores higher than 56% of npm servers
Category Design and Media
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 277 of 297 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 33 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 551 tokens (~55/item across 10 items; 10 tools + 0 resources), lean.Pass
- 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 21 Nov 26 0
- Stability: 0.97 → pass security
- 20 Nov 26 0
- Stability: pass → 0.97 functional
- 15 Nov 26 0
- Package version: 1.0.0 → 1.0.3 functional
- 14 Nov 26 0
- Stability: 0.97 → pass security
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +5
- Stability: 0.77 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Source repository: fail → pass ▲ security
- Schema quality: 53 → 551 ▼ functional
- Security disclosure: unverified → fail ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 1.0.0 → 1.0.3 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 21 Nov 2026 · Analysed npm/qr-code-mcp@1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 277 packages
| Packages resolved | 277 |
|---|---|
| Deprecated | 6 |
| Stale | 114 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
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 →
echo Echo ~23
Echo back the provided text.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text to echo. |
No output schema declared.
No examples provided.
generate_qr Generate qr ~53
Generate a QR code PNG for any text or URL.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | Output file name. |
| size | number | – | Image size in pixels. |
| text | string | yes | Text or URL to encode. |
No output schema declared.
No examples provided.
health_check Health check ~17
Check if the server is running and responsive.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tools List tools ~16
List all available tools on this server.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ping Ping ~14
Ping the server to check connectivity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
qr_analyse QR payload analysis ~111
Say what a scanner will do with a payload: whether it is read as a web link, an email, a telephone number, a saved wifi network, a location, a contact card or plain text, what the scanner does with each of those, which QR encoding mode applies, and what a bare string costs in lost automation. Two payloads encode identically and behave completely differently, and the encoded image does not show which one you have.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text or URL to analyse. |
No output schema declared.
No examples provided.
qr_capacity QR capacity check ~146
Check whether a payload can be encoded as a QR code before generating it: its size in bytes, which encoding mode the encoder will pick and why, the byte ceiling at error correction L, M, Q and H with the percentage of the ceiling used, the version and module grid each level would produce, and how much the payload would have to shrink to reach a higher level. generate_qr just encodes and either succeeds or throws a bare length error, so an over-long URL gives no explanation.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | Error correction level to check against: L, M, Q or H. Default M. |
| text | string | yes | The text or URL to check. |
No output schema declared.
No examples provided.
qr_size_report QR size report ~144
Report the QR version and module grid a payload produces at a given error correction level, the module size in pixels at each of 128, 256, 512, 1024 and 2048 pixels wide, and whether each of those is large enough for a phone camera at the usual three pixels per module, plus the smallest and largest grid the payload gives across all four levels. Nothing is written to disk. generate_qr reports the PNG byte count but not the grid it had to hit.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | Error correction level: L, M, Q or H. Default M. |
| text | string | yes | The text or URL to measure. |
No output schema declared.
No examples provided.
timestamp Timestamp ~13
Get the current UTC timestamp.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
version_info Version info ~14
Get server version and metadata.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.mrfentmen/qr-code-mcp server?
io.github.mrfentmen/qr-code-mcp runs locally as an npm package, launched with npx -y qr-code-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · qr-code-mcp
claude mcp add mrfentmen-qr-code-mcp -- npx -y qr-code-mcp
What is the io.github.mrfentmen/qr-code-mcp server?
io.github.mrfentmen/qr-code-mcp is listed in the public MCP registry as io.github.mrfentmen/qr-code-mcp. Generate QR codes as PNG images locally. No network and no key. This page covers its npm package (qr-code-mcp).
Is the io.github.mrfentmen/qr-code-mcp server safe to use?
io.github.mrfentmen/qr-code-mcp scores 77 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.mrfentmen/qr-code-mcp server expose?
io.github.mrfentmen/qr-code-mcp exposes 10 tools: generate_qr, qr_capacity, qr_analyse, qr_size_report, health_check, and 5 more. Their descriptions and schemas cost roughly 551 tokens of context every time the server is loaded.
Is the io.github.mrfentmen/qr-code-mcp server still maintained?
io.github.mrfentmen/qr-code-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.mrfentmen/qr-code-mcp server under?
io.github.mrfentmen/qr-code-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.mrfentmen/qr-code-mcp server?
VerifyMCP ran 16 checks on io.github.mrfentmen/qr-code-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.