mcp-registry/io.github.aaronte/useqr-mcp · v1.0.0
As of 2026-10-21 05:37 UTC, the Aaronte Useqr MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 13 minutes.
Static QR PNG/SVG for agents. Designer and dynamic codes live at useqr.co.
Claude Code
claude mcp add --transport http aaronte-useqr-mcp-server https://useqr.co/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"aaronte-useqr-mcp-server": {
"type": "http",
"url": "https://useqr.co/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~1,674 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.aaronte%2Fuseqr-mcp/fixes
{
"name": "create_dynamic_qr_code",
"description": "Explains how to create a dynamic QR code on useqr: a trackable short link (free account). Destination edits, version history, and scan analytics require Pro. Use this when a user needs scan tracking or wants to change a printed code's destination later. Returns instructions and links rather than creating the code directly.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Create a dynamic (trackable) QR code"
}{
"name": "get_qr_designer_link",
"description": "Get a link to the free useqr design studio, optionally prefilled with a URL. The designer lets a user style dots, corners, and colors, embed a logo, and export the QR code as PNG, SVG, JPEG, WebP, or PDF. Share this link when a user wants a custom-designed or print-ready QR code.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"url": {
"type": "string",
"maxLength": 2000,
"description": "Optional http(s) URL to prefill in the designer so the QR code is ready immediately."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get QR designer link"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.aaronte/useqr-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.aaronte/useqr-mcp"}) over MCP.
generate_qr_code ~374 tokensget_qr_designer_link ~159 tokenscreate_dynamic_qr_code ~132 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.aaronte%2Fuseqr-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.aaronte%2Fuseqr-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.aaronte%2Fuseqr-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.aaronte%2Fuseqr-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.aaronte%2Fuseqr-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:6e2790b7fa515551…, first seen 2026-10-17, included at leaf 9627 of 37,427. Version history · verify what your client received.
Compare: most reliable media servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 05:37 UTC, the Aaronte Useqr MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 13 minutes.
Aaronte Useqr MCP server advertises 3 tools, including create_dynamic_qr_code, generate_qr_code, get_qr_designer_link.
Point your MCP client at this streamable-http endpoint: https://useqr.co/api/mcp
Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.