Dynamic QR Codes

com.getdynamicqrPublished by getdynamicqr.comOfficial publisherv1.0.0Updated Oct 24, 2026

Create dynamic QR codes and re-point ones already printed, with bot-filtered scan analytics.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an assistant create dynamic QR codes, change where existing printed codes point, and read bot-filtered scan analytics.

What you can do
This remote server connects an assistant to a dynamic QR code service. It is described as letting you create dynamic QR codes, re-point codes that have already been printed, and view scan analytics that filter out bot traffic. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you manage QR codes for campaigns, packaging, or signage and want to change their destination after printing without reissuing them, or want scan statistics reported through an assistant.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's address. Authentication is OAuth and required, so the user must sign in to the provider's account; no environment variables or headers are declared.
Before you install
Requires an OAuth sign-in to the provider account. Re-pointing a printed code changes where real-world scanners are sent, so confirm destinations before applying changes. Scan analytics are collected by the third-party provider.

Installation

In SourceWeft

  1. Open Dynamic QR Codes 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.getdynamicqr%2Fqr-codes/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": {
    "dynamic-qr-codes": {
      "type": "http",
      "url": "https://mcp.getdynamicqr.com/"
    }
  }
}

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. v1.0.0LatestSep 16, 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.