BetterQR

app.betterqrPublished by betterqr.appOfficial publisherv0.2.0Updated Oct 26, 2026

Beta: read your BetterQR dynamic QR codes and per-placement scan analytics from AI agents.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Beta remote MCP server that lets an AI assistant read your BetterQR dynamic QR codes and their per-placement scan analytics.

What you can do
  • Read your BetterQR dynamic QR codes from an AI assistant
  • Retrieve per-placement scan analytics for those codes
  • No tool list is published, so exact operations are not documented; the server is described as read-only access to QR codes and scan data
When to use it
Useful if you already manage dynamic QR codes in BetterQR and want to ask an assistant about your codes or how they are being scanned, without opening the dashboard.
Requirements
A remote MCP endpoint at the provider's site, reached over streamable HTTP. OAuth sign-in with a BetterQR account is required; no environment variables or headers are declared.
Before you install
It is labeled beta, so behavior and availability may change. Access is granted through OAuth to your BetterQR account, so review the scopes requested at sign-in; scan analytics and code data are read from the provider's service.

Installation

In SourceWeft

  1. Open BetterQR in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.betterqr%2Fbetterqr/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "betterqr": {
      "type": "http",
      "url": "https://www.betterqr.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.2.0LatestOct 20, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.