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.

QR Suisse documentation

REMOTE · WWW.QRSUISSE.CH

Search and read the QR Suisse API documentation: guides, pricing and each OpenAPI operation.

Available components

+3 this week 79 Trust /100

Last scanned (21 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Code Search and Documentation

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 Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 242 tokens (~121/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

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

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 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.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 74

    First indexed and scored.

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 21 Nov 2026 · Probed https://www.qrsuisse.ch/mcp/docs

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=qr-suisse.jcloud-ver-jpc.ik-server.com CN=YR2,O=Let's Encrypt,C=US 13 Nov 2026 11 Feb 2027 RSA 2048 SHA256-RSA 58149d586d40c8d5c2946dd7df6837e0aa0
SANs: app.qrsuisse.ch, qr-suisse.jcloud-ver-jpc.ik-server.com, qrsuisse.ch, www.qrsuisse.ch
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 secure

Validation of www.qrsuisse.ch. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ch. DS published 58745 13 Verified
qrsuisse.ch. DS published 23275 13 Verified
www.qrsuisse.ch. Verified address RRset verified with the apex keys
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
strict-transport-security max-age=63072000; includeSubDomains
content-security-policy default-src 'self'; img-src 'self' data:; script-src 'self' 'nonce-Y2Q4OWVjODktYWNiMy00Yzc1LTllOGEtYWE3M2Y5MzgyODMz' 'strict-dynamic'; style-src 'self' 'unsafe-inline'; connect-src 'self' https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com; worker-src 'self'; frame-ancestors 'none'
x-content-type-options nosniff
referrer-policy strict-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.qrsuisse.ch/mcp/docs Verified 200
http (plaintext) http://www.qrsuisse.ch/mcp/docs HTTPS enforced 301 https://www.qrsuisse.ch/mcp/docs
MCP tools · 2 exposed · ~165 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
qr_suisse_get_page ~82

Returns the full Markdown text of one page of the QR Suisse documentation (English), from a closed list: llms-txt, agents-md, auth-md, pricing-md, or api/<operationId> for an operation of the QR Suisse REST API v1.

NameTypeReqDescription
pagestringyesPage identifier, as returned by qr_suisse_search_docs.
NameTypeReqDescription
contentstringyesMarkdown text of the page.
pagestringyes–
titlestringyes–
urlstringyesPublic address of the document.

No examples provided.

qr_suisse_search_docs ~83

Keyword search in the QR Suisse documentation (English): overview (llms.txt), instructions for agents, API authentication, pricing and one page per operation of the QR Suisse REST API v1. Returns up to 5 pages, best match first.

NameTypeReqDescription
querystringyesKeywords in English, for example "create dynamic QR code" or "rate limit".
NameTypeReqDescription
resultsarrayyes–

No examples provided.

Install

How do I install the QR Suisse documentation MCP server?

QR Suisse documentation is a hosted endpoint at https://www.qrsuisse.ch/mcp/docs, 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 · www.qrsuisse.ch

# add to Claude Code
claude mcp add --transport http ch-qrsuisse-mcp-docs 'https://www.qrsuisse.ch/mcp/docs'
Common questions

What is the QR Suisse documentation MCP server?

QR Suisse documentation is an MCP server listed in the public MCP registry as ch.qrsuisse/mcp-docs. Search and read the QR Suisse API documentation: guides, pricing and each OpenAPI operation. This page covers its hosted endpoint (https://www.qrsuisse.ch/mcp/docs).

Is the QR Suisse documentation MCP server safe to use?

QR Suisse documentation scores 79 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 QR Suisse documentation MCP server expose?

QR Suisse documentation exposes 2 tools: qr_suisse_search_docs, qr_suisse_get_page. Their descriptions and schemas cost roughly 165 tokens of context every time the server is loaded.

Does the QR Suisse documentation MCP server require authentication?

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

Is the QR Suisse documentation MCP server still maintained?

QR Suisse documentation 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 did VerifyMCP test on the QR Suisse documentation MCP server?

VerifyMCP ran 13 checks on QR Suisse documentation, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.