quality-qr.app

Item: quality-qr.app
Rating: 86
Author: wmcp.sh

https://quality-qr.app/api/mcp

86/100 · MCP Trust Grade · checked 7h ago · MCP 2025-03-26

✓ Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 6 tools · Productivity

quality_qr_create

Create a new trackable QR code saved to your Quality QR account. Use this when the user wants to generate a QR code for a URL, WiFi network, contact c

quality_qr_list

List QR codes in the user's Quality QR account. Use this when the user wants to see their existing QR codes, find a specific code, or check how many c

quality_qr_get

Get full details of a specific QR code by its ID. Use this when the user wants to inspect a particular QR code's configuration, check its destination

quality_qr_update

Update an existing QR code's properties. Use this when the user wants to change where a QR code points to, rename it, or enable/disable it. Destinatio

quality_qr_delete

Permanently delete a QR code from the user's account. Use this when the user wants to remove a QR code they no longer need. The short URL will immedia

quality_qr_analytics

Get scan analytics for a specific QR code. Use this when the user wants to know how many times a QR code has been scanned, see daily scan trends, unde

Spec conformance20%100

✓ initialize → protocolVersion 2025-03-26
✓ initialize HTTP 200
✓ unknown method → -32601
✓ tools/list → 6 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%100

6 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%70

single-probe latency 3061ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)

Tool hygiene15%75

100% of tools have typed inputSchema
0/6 declare outputSchema
1 destructive-by-name tools lack safety annotations

Transparency / provenance15%70

HTTPS ✓
advertises protocol 2025-03-26

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.

Grade another server

We re-grade quality-qr.app on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — quality-qr.app grade B

Share on X Open card image

https://wmcp.sh/mcp/grade/quality-qr.app

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade B](https://wmcp.sh/mcp/grade/quality-qr.app/badge.svg)](https://wmcp.sh/mcp/grade/quality-qr.app)

HTML

<a href="https://wmcp.sh/mcp/grade/quality-qr.app"><img src="https://wmcp.sh/mcp/grade/quality-qr.app/badge.svg" alt="MCP Trust Grade B · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.