
QR Code Generator API
io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 24, 2026
Generate QR codes from text or URLs. Returns base64 PNG. x402 micropayment.
Overview
Remote MCP endpoint that generates QR codes from text or URLs and returns base64 PNG images, paid per call via x402 USDC micropayments.
- What you can do
- Generate a QR code image from text, a URL, or any string data
- Set the QR code size in modules, with a default of 21
- Receive the result as base64 PNG data in a JSON response with width and height
- When to use it
- Useful when an assistant needs to produce a shareable QR code, such as a link, payment code, Wi-Fi connection code, vCard or event ticket, without running any local tooling. It is a single-purpose service, so it only makes sense if you already accept pay-per-call crypto payments.
- Requirements
- A remote MCP endpoint added by URL to the client config; no API key or signup. Payment is per call in USDC on the Base L2 network through the x402 protocol, so an x402-aware client with a funded wallet is needed to complete the 402 challenge and retry.
Installation
In SourceWeft
- Open QR Code Generator API in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via SSE. 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.Br0ski777%2Fqr-code/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"qr-code-generator-api": {
"type": "sse",
"url": "https://qr-code.api.klymax402.com/mcp"
}
}
}README
QR Code Generator API
[MCP Server] [x402] [License: MIT]
Generate QR codes from text or URLs -- base64 PNG output, configurable size. Fast and lightweight. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Quickstart -- MCP
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
Quickstart -- HTTP (x402)
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
Tools
utility_generate_qr_code
Use this when you need to generate a QR code from text, a URL, or any string data. Returns base64 image data in JSON.
Parameters
Example response:
When to use: generating shareable links, payment QR codes, Wi-Fi connection codes, vCard contact sharing, and event ticket barcodes.
Not for: screenshots (use capture_screenshot), PDFs (use document_generate_pdf).
Example agent prompts
- "Generate a QR code from text, a URL, or any string data"
Payment
- Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
- Network: Base L2 (
eip155:8453) - Asset: USDC
- Facilitator: Coinbase CDP (primary), PayAI (fallback)
- Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)
Part of klymax402
100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
Source: README.md at commit 34205b9
Tools
0Version history
1- v1.1.0LatestSep 16, 2026
Score
50% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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
- License10 pts