Endpoints: 28,729MCP servers: 18,413Payout addresses: 2,071Paid calls: 1,539Letters: 14Defects: 1,323counted 4 min ago
teppi

Server definition

Hash
sha256:17b2b9cd5413290eca082b4395a37a0d0a310652a8e22c3164a304b2b2f25793
What it is
What a remote MCP server returned when asked what it offers: 8 tools

The blob, as servednamed by its sha256

{ "instructions": "qart.uk makes QR codes where the artwork IS the code — every image is decoded by a real QR detector before it is offered, so what you get is artwork that already scanned. Three ways to get one: a free pool of finished codes anyone with an account can claim and point at their URL, a paid Studio that generates custom ones from prepaid credits, and a single finished QR bought outright over x402 with no account at all (buy_qr_outright).\n\nTHE ONE THING TO GET RIGHT WHEN CHOOSING A RAIL: whether the finished code can be RE-POINTED after it is printed. That is a property of the payload, not of the product, and only two paths give it to you. A claimed pool code (claim_pool_code) and a Studio run started with payloadKind 'qart_code' both encode a short qart.uk/_ link, so the owner retargets it for free and every copy already printed follows. EVERYTHING ELSE encodes the payload verbatim into the pixels and can never be re-pointed: a Studio run on any other payloadKind — including the default 'url' — and buy_qr_outright. Verbatim is not a defect (such a code keeps working with no dependency on us staying up) but it is permanent, so say which kind you are making before anything goes to print.\n\nWithout credentials you can resolve a scanned code, browse the free pool, work out how a payload will encode, get the raw QR module matrix, read the credit price list, and buy a single finished QR outright. Signed in through OAuth you additionally get the tools your granted scopes allow — call tools/list to see what you actually have, and whoami if you are unsure who you are acting for.\n\nClaiming pool codes, shuffling the storefront, and running the Studio are all on this server, gated by scope. A Studio run is a long job: starting one reserves credits, images stream in one at a time, and the poll that imports them is also the GPU heartbeat — keep calling poll_studio_run until the run is terminal or it soft-stops and refunds. Retargeting an existing code takes effect instantly on anything already printed, so confirm the destination with the user first.\n\nTwo things not to do. Do not ask the user for their session cookie: it is an unscoped 30-day credential and this server will not accept it anyway. And if a claim fails with \"not in your gallery\", the code came from the anonymous free-pool shelf (browse_free_pool) — claims are gated to your own storefront, which browse_my_pool shows.", "tools": [ { "description": "List the QR artwork currently claimable for free on qart.uk, one per style, with a preview image URL for each. This is the ANONYMOUS shelf — the same selection every signed-out visitor sees, and these codes are what a guest can claim. Use it to show someone what is available or to describe the styles on offer. If you are acting for a signed-in account and want codes THAT account can actually claim, use browse_my_pool instead — the two storefronts differ, and a code from here may 403 on a claim.", "inputSchema": { "additionalProperties": false, "properties": {}, "type": "object" }, "name": "browse_free_pool", "outputSchema": null }, { "description": "How to buy ONE finished QR artwork with no account at all, paying from your own wallet over x402. Returns the live price and the exact request to make. \n\nThis is the right tool when you have a wallet but no qart.uk account: get_credit_packs buys CREDITS, which still need an account to spend, and the Studio tools all require an OAuth token. This path requires neither — you GET https://qart.uk/api/v1/qr?url=..., it answers 402, you retry with a PAYMENT-SIGNATURE header, and the PNG comes back in the response body.\n\nYou are charged ONLY if a real QR detector decodes the image: settlement runs after the scan verdict, so a request that produces nothing scannable is never settled and costs you nothing. Pay in USDC on Base — you do not need ETH, because the facilitator submits the transaction.\n\nCannot be performed through MCP itself: a payment rides in an HTTP header and there is nowhere to put one here. This tool tells you the call; you make it.", "inputSchema": { "additionalProperties": false, "properties": { "size": { "description": "Pixel size. 1024 costs more. Defaults to 768.", "enum": [ 768, 1024 ], "type": "integer" }, "url": { "description": "The https destination you want the QR to encode. Optional — without it you get the price and the call shape.", "type": "string" } }, "type": "object" }, "name": "buy_qr_outright", "outputSchema": null }, { "description": "Explain how qart.uk works: scan verification, retargeting a printed code, the free claim pool and its daily allowances, Studio pricing, and what happens to credits when a run is stopped or fails. Use this before guessing at product details — pricing and allowances change and this returns the current text.", "inputSchema": { "additionalProperties": false, "properties": { "topic": { "description": "Which aspect to explain. Defaults to overview.", "enum": [ "overview", "free-pool", "studio", "pricing", "retargeting" ], "type": "string" } }, "type": "object" }, "name": "explain_qart", "outputSchema": null }, { "description": "What Studio credits cost: the packs on sale, their price in USD, and roughly how many images each buys. Anonymous — this is a price list. Read it rather than quoting a price from memory; packs change.\n\nAn agent that runs out mid-task can top up WITHOUT a human, paying from its OWN wallet: POST /api/qart/x402/credits?pack=... with a qart:purchase bearer token. The money comes from the application's wallet, never the user's card. Stripe checkout (POST /api/qart/checkout) remains human-only; hand the user the purchase URL for that.", "inputSchema": { "additionalProperties": false, "properties": {}, "type": "object" }, "name": "get_credit_packs", "outputSchema": null }, { "description": "The complete parameter contract for qart.uk's dithered photo QR recipe — an error-diffused technique (after andrew-t) that dithers a photograph into the space around each QR module, so the finished 1-bit image reads as a picture and still scans.\n\nTHIS TOOL GENERATES NOTHING. There is no API for the technique and no endpoint that will run it for you: it is a browser-side generator, and this tool returns the parameters, ranges, defaults and algorithm order so that YOU can implement it or instruct someone who will. Pair it with get_qr_matrix, which supplies the module grid and the function-pattern map the algorithm needs.\n\nIt also returns the honest limits, which matter before anyone prints anything: no scan verdict is computed anywhere in this path, error correction wants to stay at H, and stricter detectors (zbar) reject output that phone-grade detectors accept. Treat a dithered code as untested until someone scans the actual printed sheet.", "inputSchema": { "additionalProperties": false, "properties": {}, "type": "object" }, "name": "get_dither_qr_parameters", "outputSchema": null }, { "description": "Return the actual QR MODULE GRID for a payload — the black/white matrix, plus a per-module map of which modules are function patterns (finder, separator, timing, alignment, format info, version info, dark module) and which carry data. Both come back as one row string per row. Costs nothing, mints nothing, stores nothing.\n\nUse this when you are going to RENDER or transform a QR yourself: dithering a photo into it, drawing it as an SVG, laying it out for print, or reasoning about which modules are safe to alter. The function-pattern map is the point — any technique that paints over a QR has to know which modules a scanner uses to FIND the code (finder, timing, alignment) versus which merely carry bits.\n\nDo NOT use it to check whether a payload fits — preview_qr_encoding is smaller and answers that. Do NOT use it to get a qart.uk product: this is a plain standards QR, with no artwork, no scan verdict and no alias behind it. The matrix is canonical and untransformed: invert, rotation, mirror and any subpixel scaling are yours to apply afterwards.", "inputSchema": { "additionalProperties": false, "properties": { "address": { "description": "For 'vcard': postal address.", "type": "string" }, "allDay": { "description": "For 'event': all-day (DATE values).", "type": "boolean" }, "amount": { "description": "For 'paypal': optional amount.", "type": "string" }, "auth": { "description": "For 'wifi': security type. Defaults to WPA.", "enum": [ "WPA", "WEP", "nopass" ], "type": "string" }, "body": { "description": "For 'mailto': message body.", "type": "string" }, "description": { "description": "For 'event': description.", "type": "string" }, "ecc": { "description": "Error correction level. Defaults to H, which is what any paint-over-the-code technique needs.", "enum": [ "L", "M", "Q", "H" ], "type": "string" }, "email": { "description": "Email address, for 'vcard'/'mecard'/'mailto'.", "type": "string" }, "end": { "description": "For 'event': end datetime.", "type": "string" }, "handle": { "description": "For social kinds (instagram, twitter, youtube, facebook, tiktok, linkedin, paypal): handle or profile URL.", "type": "string" }, "hidden": { "description": "For 'wifi': hidden network.", "type": "boolean" }, "lat": { "description": "For 'geo': latitude.", "type": "number" }, "lng": { "description": "For 'geo': longitude.", "type": "number" }, "location": { "description": "For 'event': location.", "type": "string" }, "mask": { "description": "Which of the 8 standard mask patterns to apply. 'auto' (default) picks the lowest-penalty one, exactly as the encoder in the browser does. All 8 are legal and scan identically; they differ only in how the light and dark modules are laid out, which is worth pinning when you are fitting a picture to the grid.", "enum": [ "auto", "0", "1", "2", "3", "4", "5", "6", "7" ], "type": "string" }, "message": { "description": "For 'sms'/'whatsapp': message text.", "type": "string" }, "name": { "description": "For 'vcard'/'mecard': full name.", "type": "string" }, "org": { "description": "For 'vcard': organization.", "type": "string" }, "password": { "description": "For 'wifi': network password.", "type": "string" }, "payloadKind": { "description": "What the code should contain. Defaults to url.", "enum": [ "url", "qart_code", "text", "wifi", "vcard", "mecard", "mailto", "tel", "sms", "geo", "whatsapp", "telegram", "event", "instagram", "twitter", "youtube", "facebook", "tiktok", "linkedin", "paypal" ], "type": "string" }, "phone": { "description": "Phone number, for 'vcard'/'mecard'/'tel'/'sms'/'whatsapp'.", "type": "string" }, "ssid": { "description": "For 'wifi': network name.", "type": "string" }, "start": { "description": "For 'event': start datetime (YYYY-MM-DDTHH:MM).", "type": "string" }, "subject": { "description": "For 'mailto': subject line.", "type": "string" }, "text": { "description": "For 'text': the literal text.", "type": "string" }, "title": { "description": "For 'vcard': job title. For 'event': event title.", "type": "string" }, "url": { "description": "For 'url': the destination. For 'vcard'/'mecard': the website.", "type": "string" }, "username": { "description": "For 'telegram': username or t.me URL.", "type": "string" }, "version": { "description": "Force a QR version (1-40, size 21-177 modules). Omit for the smallest that fits. Pinning BELOW the fit is impossible and is raised to the fit, matching the Studio.", "maximum": 40, "minimum": 1, "type": "integer" } }, "type": "object" }, "name": "get_qr_matrix", "outputSchema": null }, { "description": "Work out how a payload will encode as a QR code, without creating anything. Returns the exact string the pixels would carry, its byte length, the QR version and module count required, the capacity remaining at that version, and any warnings. Costs nothing and mints nothing.\n\nUse this to answer questions like \"will this URL fit at error correction level H\" or \"how much does a long Wi-Fi password cost me in QR density\". Higher ECC survives damage better but needs more modules for the same data; more modules print smaller and get harder to scan.\n\npayloadKind 'qart_code' sizes the RETARGETABLE variant instead: the pixels carry a 16-byte qart.uk/_ link rather than your data, which is usually several versions smaller. Compare the two before committing to a print.\n\nThis returns metadata only, never the module grid. For the actual black/white matrix, call get_qr_matrix.", "inputSchema": { "additionalProperties": false, "properties": { "allDay": { "description": "For 'event': all-day (DATE values).", "type": "boolean" }, "amount": { "description": "For 'paypal': optional amount.", "type": "string" }, "description": { "description": "For 'event': description.", "type": "string" }, "ecc": { "description": "Error correction level, lowest to highest. Defaults to the Studio default if omitted.", "enum": [ "L", "M", "Q", "H" ], "type": "string" }, "email": { "description": "For payloadKind 'vcard': email address.", "type": "string" }, "end": { "description": "For 'event': end datetime.", "type": "string" }, "fields": { "description": "Payload fields for the kind. Flat sibling properties (url, phone, handle, …) are also accepted, matching get_qr_matrix.", "type": "object" }, "handle": { "description": "For social kinds: handle or profile URL.", "type": "string" }, "location": { "description": "For 'event': location.", "type": "string" }, "message": { "description": "For 'sms'/'whatsapp': message text.", "type": "string" }, "name": { "description": "For payloadKind 'vcard': full name.", "type": "string" }, "password": { "description": "For payloadKind 'wifi': network password.", "type": "string" }, "payloadKind": { "description": "What the code should contain. 'qart_code' sizes the retargetable variant — a 16-byte qart.uk/_ link instead of your data. whatsapp/telegram/event/social kinds assemble a standard URL or VCALENDAR; they are verbatim, not retargetable.", "enum": [ "url", "qart_code", "text", "wifi", "vcard", "mecard", "mailto", "tel", "sms", "geo", "whatsapp", "telegram", "event", "instagram", "twitter", "youtube", "facebook", "tiktok", "linkedin", "paypal" ], "type": "string" }, "phone": { "description": "Phone, for vcard/mecard/tel/sms/whatsapp.", "type": "string" }, "ssid": { "description": "For payloadKind 'wifi': network name.", "type": "string" }, "start": { "description": "For 'event': start datetime (YYYY-MM-DDTHH:MM).", "type": "string" }, "text": { "description": "For payloadKind 'text': the literal text.", "type": "string" }, "title": { "description": "For 'event': title. For 'vcard': job title.", "type": "string" }, "url": { "description": "For payloadKind 'url': the destination.", "type": "string" }, "username": { "description": "For 'telegram': username or t.me URL.", "type": "string" }, "version": { "description": "Force a QR version (size). Omit to use the smallest that fits.", "maximum": 40, "minimum": 1, "type": "integer" } }, "required": [ "payloadKind" ], "type": "object" }, "name": "preview_qr_encoding", "outputSchema": null }, { "description": "Resolve a scanned qart.uk code to the URL it currently points at. Accepts the alias ('_ab12cde'), or a full qart.uk URL to pull it out of. Returns targetUrl, or disabledReason if the owner retired it. This does not count as a scan and will not affect the owner's statistics. Only the '_' code class resolves here; older qart.uk links of other shapes are not in this pool.", "inputSchema": { "additionalProperties": false, "properties": { "code": { "description": "The code to resolve — '_ab12cde', '/_ab12cde', or 'https://qart.uk/_ab12cde'.", "type": "string" } }, "required": [ "code" ], "type": "object" }, "name": "resolve_qart_code", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:17b2b9cd5413290eca082b4395a37a0d0a310652a8e22c3164a304b2b2f25793 | sha256sum