GhostQR

io.github.AjshawitPublished by GitHub account Ajshawitv1.0.0Updated Oct 26, 2026

Create and update dynamic QR codes, change their destinations, and read scan analytics.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

GhostQR is a remote MCP server that lets an assistant create and update dynamic QR codes, change their destinations, and read scan analytics.

What you can do
  • Create dynamic QR codes for links or destinations
  • Update existing QR codes so their destination can be changed without reprinting
  • Read scan analytics for the codes it manages
When to use it
Useful when you want an assistant to generate QR codes for campaigns, print or packaging, and to adjust where they point later or check how often they are scanned.
Requirements
A remote MCP endpoint at ghqr.au over streamable HTTP. OAuth authentication is required, so the user must sign in to a GhostQR account through the OAuth flow. No environment variables or headers are declared.
Before you install
Access is tied to an OAuth-authorized GhostQR account, so the assistant can act on the codes in that account. Updating a code changes where real-world scans are sent, which can redirect people who already have the printed code. Scan analytics are collected by the service.

Installation

In SourceWeft

  1. Open GhostQR 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/io.github.Ajshawit%2Fghostqr/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": {
    "ghostqr": {
      "type": "http",
      "url": "https://ghqr.au/api/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. v1.0.0LatestOct 22, 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.