QRsome – QR codes for agents

com.qrsomePublished by qrsome.comOfficial publisherv0.4.7Updated Oct 24, 2026

Branded QR codes for AI agents: static or dynamic, re-pointable after printing, with scan counts.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

A remote MCP server that lets an assistant create branded QR codes, static or dynamic, with dynamic codes re-pointable after printing and scan counts.

What you can do
Create branded QR codes, choosing between static and dynamic types. Re-point a dynamic code to a new destination after it has been printed. Check scan counts for codes. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Useful when an assistant needs to generate QR codes for print or marketing material and you want the flexibility to change a code's destination later or track how often it is scanned.
Requirements
A remote endpoint at qrsome.com reached over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared.
Before you install
Access requires OAuth sign-in to a third-party service, so account data is shared with that provider. Dynamic codes depend on the provider staying available, and scan counts are collected by the service.

Installation

In SourceWeft

  1. Open QRsome – QR codes for agents 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/com.qrsome%2Fqrsome/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": {
    "qrsome-qr-codes-for-agents": {
      "type": "http",
      "url": "https://qrsome.com/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.4.7LatestOct 24, 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.