dev.cz-agents/payqr

REMOTE · PAYQR.CZ-AGENTS.DEV · 2 COMPONENTS · SCANNED AUG 3

European payment QR — SPAYD (CZ/SK) & EPC/GiroCode (SEPA), plus text/WiFi/vCard. Local, free.

Available components

remote · payqr.cz-agents.dev 65 npm · @czagents/payqr 35

+4 this week 65 65 Trust /100

Trust breakdown (6 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 →

Endpoint Security57

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability67

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 1083 tokens (~180/item across 6 items; 6 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 Management23

Stability observed for 7 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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · payqr.cz-agents.dev

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http dev-cz-agents-payqr https://payqr.cz-agents.dev/mcp

# ~/.codex/config.toml

[mcp_servers.dev-cz-agents-payqr]
url = "https://payqr.cz-agents.dev/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-cz-agents-payqr": {
      "type": "remote",
      "url": "https://payqr.cz-agents.dev/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add dev-cz-agents-payqr --url https://payqr.cz-agents.dev/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  dev-cz-agents-payqr:
    url: "https://payqr.cz-agents.dev/mcp"

// mcp.json

{
  "mcpServers": {
    "dev-cz-agents-payqr": {
      "type": "http",
      "url": "https://payqr.cz-agents.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

3 Aug 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.
1 Aug 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.
31 Jul 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
30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1
- New tool “qr_payment_batch” functional
28 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
27 Jul 26 +49
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 12

First indexed and scored.

Show 7 earlier entries Hide earlier entries

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 3 Aug 2026 · Probed https://payqr.cz-agents.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=cz-agents.dev	CN=YE1,O=Let's Encrypt,C=US	14 Jun 2026	12 Sept 2026	ECDSA 256	ECDSA-SHA384	57eb48bfec168fd149d5dd562efca49d697
SANs: *.cz-agents.dev, cz-agents.dev
CN=YE1,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

DNSSEC insecure

Validation of payqr.cz-agents.dev. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
dev.	present	60074	8	Verified
cz-agents.dev.	absent			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

Header	Value
x-content-type-options	nosniff
x-frame-options	SAMEORIGIN

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://payqr.cz-agents.dev/mcp	Verified	200
http (plaintext)	http://payqr.cz-agents.dev/mcp	HTTPS enforced	301	https://payqr.cz-agents.dev/mcp

MCP tools — 6 exposed · ~511 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.

Tool Tokens

qr_payment ~221

Create a European payment QR code. Auto-selects SPAYD for CZ/SK IBANs and EPC/GiroCode for other SEPA IBANs.

Input Output Examples

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_payment_batch ~86

PAID. Create payment QR codes for a whole batch of payments in one call — e.g. an invoice run. The free qr_payment tool handles one payment per call; this one returns the whole set. Requires payment via x402; call without payment first to receive the terms.

Input Output Examples

Name	Type	Req	Description
payments	array	yes	Up to 50 payments. Each QR is generated and verified independently.

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

Name	Type	Req	Description
email	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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	12
27 Jul	61
28 Jul	61
29 Jul	62
30 Jul	63
31 Jul	63
1 Aug	64
2 Aug	64
3 Aug	65