dev.cz-agents/payqr
NPM · @CZAGENTS/PAYQR · 2 COMPONENTS
European payment QR — SPAYD (CZ/SK) & EPC/GiroCode (SEPA), plus text/WiFi/vCard. Local, free.
Available components
Last scanned (13 hours ago)
Scores higher than 46% of npm servers
Category Finance and Payments
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
- 82 of 219 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency48
- 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 20 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 930 tokens (~186/item across 5 items; 5 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 Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 5 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.
- 3 Nov 26 −6
- Stability: pass → 0.60 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 16 Oct 26 +41
- Injection markers: unverified → pass ▲ security
- Stability: unverified → 0.80 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 15 Oct 26 +5
- Source repository: unverified → pass ▲ security
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 · Analysed npm/@czagents/payqr@0.1.4
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 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| 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 219 packages
| Packages resolved | 219 |
|---|---|
| Deprecated | 1 |
| Stale | 81 |
| Tree resolution | Complete |
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 →
qr_payment ~221
Create a European payment QR code. Auto-selects SPAYD for CZ/SK IBANs and EPC/GiroCode for other SEPA IBANs.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Optional payment amount. |
| bic | string | – | Optional BIC for EPC/GiroCode line 5. Ignored with a warning for SPAYD. |
| constant_symbol | string | – | Optional Czech constant symbol for SPAYD. |
| currency | string | – | Optional ISO 4217 currency code. Defaults to CZK for SPAYD and EUR for EPC. |
| iban | string | yes | Recipient IBAN. Validated with the IBAN mod-97 checksum. |
| message | string | – | Optional payment message or EPC remittance text. |
| recipient_name | string | – | Recipient name. Required for EPC/GiroCode. |
| standard | string | – | Payment QR standard. Defaults to auto detection. |
| variable_symbol | string | – | Optional reference: goes to remittance (line 11) for EPC, to X-VS for SPAYD. |
No output schema declared.
No examples provided.
qr_read ~48
Decode a QR code from a base64 PNG/JPEG image or image data URI and classify its content.
| Name | Type | Req | Description |
|---|---|---|---|
| image_data | string | yes | Base64 image bytes or a PNG/JPEG data URI. |
No output schema declared.
No examples provided.
qr_text ~30
Create a QR code containing plain text.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text to encode in the QR code. |
No output schema declared.
No examples provided.
qr_vcard ~62
Create a QR code containing a vCard 3.0 contact.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Optional email address. | |
| name | string | yes | Contact display name. |
| org | string | – | Optional organization. |
| phone | string | – | Optional phone number. |
No output schema declared.
No examples provided.
qr_wifi ~64
Create a Wi-Fi network QR code.
| Name | Type | Req | Description |
|---|---|---|---|
| hidden | boolean | – | Whether the network SSID is hidden. |
| password | string | – | Optional Wi-Fi password. |
| security | string | – | Wi-Fi security type. |
| ssid | string | yes | Wi-Fi network name. |
No output schema declared.
No examples provided.
How do I install the dev.cz-agents/payqr MCP server?
dev.cz-agents/payqr runs locally as an npm package, launched with npx -y @czagents/payqr. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @czagents/payqr
claude mcp add dev-cz-agents-payqr -- npx -y @czagents/payqr
What is the dev.cz-agents/payqr MCP server?
dev.cz-agents/payqr is an MCP server listed in the public MCP registry as dev.cz-agents/payqr. European payment QR, SPAYD (CZ/SK) & EPC/GiroCode (SEPA), plus text/WiFi/vCard. Local, free. This page covers its npm package (@czagents/payqr).
Is the dev.cz-agents/payqr MCP server safe to use?
dev.cz-agents/payqr scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 dev.cz-agents/payqr MCP server expose?
dev.cz-agents/payqr exposes 5 tools: qr_payment, qr_text, qr_wifi, qr_vcard, qr_read. Their descriptions and schemas cost roughly 425 tokens of context every time the server is loaded.
Is the dev.cz-agents/payqr MCP server still maintained?
dev.cz-agents/payqr 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 licence is the dev.cz-agents/payqr MCP server under?
dev.cz-agents/payqr declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.