Roastify MCP Server

Generate a patron's account statement at this operator. Returns the patron's purchase history, active credit tranches, per-tool usage breakdown, and recent daily usage logs. This is the patron's spending account — not the operator's Authority tax balance. Free — no credits consumed. Proof of npub ownership is required to prevent statement-scraping of arbitrary patrons.

Generate a visual SVG infographic of your account statement. Returns the same data as account_statement, rendered as a dark-themed SVG graphic with balance hero, metrics cards, health gauge, tranche table, and tool usage breakdown. Costs 1 api_sat per call. Proof is verified by ``debit_or_deny`` before any cost is incurred.

Add a new element (text or image) to a design and commit a new version of it. The store is configuration management: the element is committed back to the SAME design_id (git tracks the diff). The new element's id comes back, so you can immediately edit a text element by id with update_design_text, or move/reorder either kind with move_elements. Placement is validated server-side and REFUSED, not warned: the element must fall inside the named panel (with a default margin — the dieline carries no real safe area) — or, when the product has no panels (Tubes / continuous wrap), inside the design sheet — and must not overlap any existing element (the collider's id is named). Typography is inherited for text, so a new text element matches the template. Image creation reuses a src already present in the design (no new asset upload) — pass `kind="image"` with `src_from` (an existing image id) or `src` that already appears on an image.

Check this operator's adoption-request status at a chosen Authority. Free. Polls the Authority MCP-to-MCP for the status of this operator's request (pending / approved / rejected / provisioned).

Check a Roastify artwork job. Free — polling never costs anything. A finished job carries ``artwork_url``; a failed one carries ``error``.

Browse the Roastify catalog: products and coffee blends together. Plan-gated items are returned with their tier marked, not hidden. Note that Roastify's catalog carries no origin, altitude, processing, or varietal data — those live only in the Merchant App UI. Roast level and decaf status come from the blend.

Check this operator's tax balance at the Authority. Returns the sats available for certifying patron credit purchases. When this balance reaches zero, patron top-ups cannot be certified and the operator must call purchase_credits on the Authority. This is the operator's own funding — not a patron balance. Free.

Check a patron's credit balance at this operator. This is the patron's spending balance — credits purchased via Lightning for tool calls at this operator. For the operator's own balance at the Authority (needed to certify patron purchases), use authority_check_balance instead. Free — no credits required. Proof of npub ownership is required to prevent anyone-with-the-registry from enumerating balances.

Check the payment status of a Lightning invoice. Call after paying the invoice from purchase_credits. Free — no credits required. Proof of npub ownership is required to prevent credit-grant front-running by an observer of the invoice ID.

Preview the effective cost of a tool call. Shows the base cost and any constraint effects (discounts, free trials, surge pricing). Free — no credits required.

Check whether a previously-cached dpop_token is still valid. Mirrors ``check_oauth_status`` for the npub-proof flow: a calling agent can ask "will my next paid call accept this dpop_token?" before burning credits on a guaranteed failure. Free, no side effects — does not evict the cache or touch relays.

Check Roastify stock for one SKU, or the whole stock list.

Delete a coupon. Cascades to all patron redemptions. Any chain step referencing the deleted coupon_id becomes a no-op (the constraint returns neutral on unknown ids) — the Studio surfaces orphan references as warnings. RESTRICTED to operator — requires proof.

Delete one of your stored designs.

Remove a single operator secret field. Deletes one key from the operator's encrypted credential blob without touching the others — the field-level counterpart to ``forget_credentials``, which wipes the whole row. Use it to retire a leftover after an SDK cutover (a Prefect key after Modal, or a stored but untemplated orphan like ``anthropic_api_key``) without taking the operator down for a full re-delivery. Stored-but-untemplated fields are first-class: the delete is keyed on what is vaulted, not on what the current template declares. Idempotent — already-absent fields report ``removed: false`` without rewriting the vault. RESTRICTED to the operator — requires proof (nsec-signed kind-27235 or a cached dpop_token phrase); patron proofs are rejected. A deletion is as destructive as a write.

Remove a single patron credential field. Deletes one field from stored credentials without affecting other fields. Free. Proof of npub ownership is required — this is a write to the patron's sensitive credential vault.

Fetch one of your stored designs in full, with its images re-inlined.

Remove a coupon from this patron's redemption list. Cosmetic only — the coupon itself still exists at the operator, and the patron can re-redeem the same code later while the window allows. Free — requires proof of ``npub``.

Delete vaulted credentials for a specific service and npub. For operator credentials, pass the operator's own npub. For patron credentials, pass the patron's npub. Always requires proof of npub ownership — a deletion is as destructive as a write.

Generate packaging artwork from one of your saved Design Studio designs. This personalizes a template you already authored: it rewrites that design's named text and image placeholders. It cannot author a design from scratch, and the artwork it produces is NOT attached to a product — Roastify's API has no product-create or storefront-sync surface. You get an artwork URL and carry it onward yourself. Roastify renders asynchronously, so this returns a job id straight away. Check it with roastify_artwork_status, which is free.

Get one coffee blend: roast level, decaf status, and its variants.

Get one catalog product with its variants, sizes, prices, and dieline.

List the editable text layers of a stored design — the fields you can change. Returns each text layer's id, current text, `chars` (its length), font, `align`, box geometry (`fontSize`, `width`, `height`), and `z` (paint-order index in the top-level `elements` array) — but NOT the design's images, so it stays small enough to reason over in a conversation. Each layer's current text is its own label: infer its role (product name, tagline, story, recipe, tasting notes, …) from the words it holds. The same name often appears in several layers and inside longer blurbs; change every id that should carry it. Also returns `sheet` (the overall design extent), `panels` (the box's panel columns — front/back/left/right — recovered from the dieline, each with bounds; empty for single-face products like Tubes, where placement uses `sheet` instead), and a real `face` per layer/element (which panel its x-centre sits on, not the constant "sheet"; when panels is empty, layers keep their native faceId such as "wrap"). And `elements` — the NON-text elements (images, shapes, rules), each with id, type, name, bounds, `z`, and its `fill`/`stroke` colours — so a roast scale can be audited (a filled dot has a dark `fill`, an empty one none) and set with roastify_move_elements. `fonts` lists the families loaded on the design plus any family a layer already uses — pick from it when setting `fontFamily` via move_elements. Read those before judging the design: a header with no text value beneath it is NOT necessarily a defect — the value may be a graphic in `elements` (e.g. a five-dot roast scale under a ROAST header), and it tells you where NOT to place new text. Roastify's migrated format carries no visibility flag, so a layer that exists may still not print — do not report a missing value as a production error. Geometry: each layer's `x`/`y` is its top-left corner in design units (the sheet origin is its top-left). `width`/`height` are MEASURED text bounds, not fixed frames — text does not clip, it grows, so a revision that holds the line count and longest-line length keeps the footprint. `z` is paint order (lower draws first / behind); change it with roastify_move_elements `{"id", "z": "front"|"back"|N}`. Two things to respect: - A stash label states INTENT, not content: a design labeled for one coffee may still hold a donor template's words. Trust these layers, not the label. - `width` is the fixed wrap frame; `height` is the grown extent and re-measures when you edit the text. Keep each replacement within roughly ±10% of the layer's `chars`; longer copy grows the box downward and can overrun its neighbour, which the merchant then fixes by hand. `fontSize`/`width` gauge how tight a layer is; to change a label's `fontSize`, wrap frame, `align`, or `fontFamily`, use roastify_move_elements. Also returns `description` — the product's store-page prose (outside the design, syncs to Shopify), versioned with the design. Refine it and write it back with roastify_set_product_description. Pair with roastify_update_design_text to save text changes.

Get one of your saved product designs in full, with all its variants. The coffee's IDENTITY (which blend) is not a named field — it is encoded in the variant SKU, e.g. `COF-WHB-12O-HGL-BOX` → `HGL` → the High Lakes blend. Decode the SKU before writing origin/roast copy: a product's title can say one thing while its SKU is really a different blend.

Read an npub's public Nostr profile (NIP-01 kind-0 metadata). Free, no proof — the data is already public on relays. Returns the latest metadata fields (name, display_name, about, picture, banner, nip05, website, lud16) or an empty profile if none is published.

Generate a Merkle inclusion proof that a patron's balance was included in a Bitcoin-notarized snapshot.

Report this operator's configuration readiness. Shows which operator settings are configured, which are missing, and how to deliver each missing value. For patron-level credential status, use get_patron_onboarding_status instead. Free.

List stored patron credential field names (not values). Returns the names of fields stored for a patron, plus each field's ``delivered_at`` ISO-8601 timestamp when known (null for secrets vaulted before timestamps were recorded). Values are never exposed — use this to verify which fields are configured and how old each one is. Free. Proof of npub ownership is required: the list of configured fields is itself sensitive (reveals which integrations a patron has set up).

Report a patron's credential readiness for this operator. For set-once services (eXcalibur, TheBrain), shows which patron secrets are configured and which are missing. For dynamic/OAuth2 services (Schwab), reports that no patron credentials are needed. Free. Proof of npub ownership is required because credential presence is sensitive information about the patron's setup.

Get the active pricing model for this operator. Free. If no model exists, self-initializes a scaffold with all registered tools at 0 sats. No economic data from code.

Return canonical (tool_id, mcp_name, …) for every tool the wheel exposes. The authoritative source for any client (Studio, agents, FE) that needs to know how this MCP identifies its tools. Reconcile uses this output to UUID-join against the stored pricing model — no name-based UUID derivation, no guessing. Includes both ToolIdentity-seeded tools and any UUID recorded by ``@paid_tool`` that is missing from the registry. The latter appear with ``registered: false`` (and in the top-level ``unregistered`` array) so Reconcile can flag deploy drift instead of silently reporting clean when a live tool was never seeded (#174). If the operator renames a function or rebrands a slug, the mcp_name in this output changes but tool_id stays. That's the whole point of the canonical-UUID design. Also diffs the live FastMCP wire surface against the registry. Tools exposed on the wire but absent from the registry appear in ``unregistered`` so Reconcile can flag deploy drift instead of silently under-reporting (issue #175). Free, no side effects.

List all available constraint types and their parameter schemas. Returns the type, category, description, and parameter specs for every constraint that can be used in a pricing pipeline. Free — no credits required.

List every coupon this operator has minted (newest first). Each row carries the current ``times_redeemed`` counter — the Studio renders a progress bar from this against ``total_uses``. RESTRICTED to operator — requires proof.

List a stored design's committed versions, newest first — the git history. Each version carries its `sha`, `short_sha`, `date`, commit `message`, `tag` (the version tag if one was set at Commit), and `commit_url`. Pass a version's `sha` (or `tag`) as the `ref` to roastify_fetch_design to fetch that exact version.

List your stored designs — metadata only, newest first.

List the coupons this patron has redeemed on this operator. Returns both active and exhausted redemptions with a per-row ``status`` (``active`` / ``window_closed`` / ``patron_limit`` / ``total_limit``). Free — requires proof of ``npub``.

List your own saved Roastify product designs, one page at a time. Returns has_next_page and end_cursor so you can tell a page from a complete list.

List recent Bitcoin notarization records.

Create a new operator-owned discount coupon.

Move a group of elements together and/or resize elements; commit a new version. The Designer can move only one layer at a time, so a block of layered content (a spec panel, a logo lockup) drifts out of alignment when its backing shape is moved alone. This relocks that block: name the ids and shift them as one rigid object, and separately re-centre or resize individual rectangles. The store is configuration management: the edit is committed back to the SAME design_id (git tracks the diff). Apply it onto the product with the browser courier. Nothing is validated against panel bounds here (unlike add_design_element): you are re-aligning existing, deliberately-placed content, so the caller owns the coordinates. The heavy background image is never moved unless you name its id.

Build a Merkle tree of all patron balances and submit the root to Bitcoin via OpenTimestamps. Operator-only background task. Bitcoin confirmation takes 1-6 hours. Free — no credits required.

Describe the DPYC ecosystem via the Oracle. Free.

Get the current DPYC certification tax rate. Free.

Get DPYC onboarding instructions from the Oracle. Free.

Look up a DPYC community member by npub. Free.

Get active network advisories from the Oracle. Free.

Publish a CLIENT-SIGNED kind-0 profile to relays for an npub. The wheel never holds a patron nsec. The frontend signs the kind-0 metadata event with the patron's session key or a NIP-07 extension and passes the signed event (JSON) here; the wheel verifies the signature matches the npub, then relays it to public relays. The signature is the authorization — no proof token, no key custody. Free.

Buy credits via Bitcoin Lightning. Creates a Lightning invoice. Pay it with any Lightning wallet, then call check_payment to confirm. Proof of npub ownership is required so credits land in the correct ledger. Free — no credits required to call.

Pick up credentials from the Secure Courier. Completes the CREDENTIAL-DELIVERY flow (the ownership-proof counterpart is ``receive_npub_proof``). **Call this only after the user confirms they have replied.** Deterministic, one-shot retrieval: name the response you want with ``(sender_npub, service, dpop_token)`` and the tool drains ONLY the rendezvous relay that channel was pinned to. Every popped DM with the wrong session phrase is deleted and its sender is NACK'd; the first DM with the matching phrase is accepted (ACK'd) and the scan stops. If none match, the queue is drained and a ``courier_not_found`` result is returned. Do NOT poll, loop, or retry. If a credential_card (ncred1...) is provided, it is redeemed directly without any relay access (dpop_token not required for that path). On success, the payment processor client is reinitialized from the new credentials — no server restart needed.

Receive npub ownership confirmation from a patron. Completes the npub-OWNERSHIP-PROOF flow (the credential-delivery counterpart is ``receive_credentials``). **Call this only after the user confirms they have replied.** Deterministic, one-shot retrieval: name the response with ``(patron_npub, dpop_token)`` — the ``dpop_token`` being the value returned by ``request_npub_proof``. The tool drains ONLY the pinned rendezvous relay that challenge was published on, stopping at the DM whose phrase matches. Mismatched DMs are deleted and NACK'd (without revealing the expected phrase). If called before the user replies, their message will never be found. Do NOT poll, loop, or retry. The signed DM itself proves npub ownership (the patron's nsec signed it). On success, returns the ``dpop_token`` — the same token. The calling application MUST remember it and pass it as the ``dpop_token`` parameter on every subsequent paid tool call. The proof (a hash of the token) is stored in the vault keyed by that hash — the MCP never stores the raw token itself. Free.

Pick up patron credentials from the Secure Courier. Deterministic, one-shot retrieval: name the response with ``(sender_npub, dpop_token)`` and the tool drains ONLY the pinned rendezvous relay for that channel, stopping at the matching DM. Provide an ncred1... credential_card to redeem directly instead (dpop_token not required for that path). Do NOT poll or retry. Free.

Claim a coupon by its name (the code the operator shared). Looks up the operator's coupon by ``code``, validates the window and total cap, and records a per-patron redemption row. Subsequent paid tool calls on this MCP auto-apply the discount until ``uses_per_patron`` is exhausted. Free — no credits required. Requires proof of ``npub``. Idempotent: redeeming the same code twice returns the existing redemption.

File a field report about this service as a GitHub issue on the operator's repo. Found a tool's metadata or response wrong or confusing? Report it where the tool lives. The **author of record is your npub** — no npub / no proof, no issue — and it is stamped into the issue so the report is attributed to you, not the operator. Costs a small fee (a free write to an issue tracker would be abused). The report is PUBLIC and goes to the maintainers' normal triage; nothing is verified here. Returns the filed issue's repo, number, and url. If this operator has not enabled field reports, returns an "issue reporting not configured" situation and you are not charged.

Ask a chosen Authority to adopt this operator (deferred courtship). RESTRICTED to the operator — requires proof the caller controls this operator's npub. Resolves the Authority's MCP endpoint from the community registry, mints an inline ownership proof with this operator's nsec, and delivers the request MCP-to-MCP. The Authority records it as pending; its owner approves on their own time. Poll ``adoption_status`` for progress; the operator flips to ``ready`` once the Authority provisions it.

Open a Secure Courier channel for credential delivery. This is the CREDENTIAL-DELIVERY flow — use it to hand over a service secret (API keys, tokens). To merely prove you control an npub (the usual answer to a ``proof_required`` error), use ``request_npub_proof`` instead. Note: dynamic/OAuth2 services (e.g. Schwab) need NO couriered secret — check ``service_status`` first. Sends a welcome DM with a credential template. The recipient must read the DM in their Nostr client, fill in the fields, and reply manually. **This is a human-in-the-loop flow.** After calling this tool, STOP and tell the user what to do. Wait for the user to confirm they have replied before calling ``receive_credentials``. Do NOT poll or retry — each ``receive_credentials`` call destructively drains the relay mailbox.

Request npub ownership proof from a patron via Nostr DM. This is the npub-OWNERSHIP-PROOF flow — use it when a call returns ``proof_required``. It proves the caller controls an npub; it does NOT deliver any service secret. To hand an operator its API keys or OAuth secrets, use ``request_credential_channel`` instead. Sends a challenge DM that the patron must sign and reply to using their Nostr client. **This is a human-in-the-loop flow.** After calling this tool, STOP and tell the user to check their Nostr client and reply to the challenge. Wait for the user to confirm they have replied before calling ``receive_npub_proof``. Do NOT poll or retry — each ``receive_npub_proof`` call destructively drains the relay mailbox. **Returns** a ``dpop_token`` — the demonstrated-proof-of-possession token that the calling application MUST remember and pass as the ``dpop_token`` parameter on every subsequent paid tool call. The MCP does not retain this value across restarts. **Lifecycle:** The cached proof expires after the patron's chosen duration. When it expires, call ``request_npub_proof`` again for a fresh challenge, then wait for the user, then call ``receive_npub_proof``. Free.

Open a Secure Courier channel for patron credential delivery. Sends a welcome DM with a credential template to the patron. Free.

Erase all pricing models and restore a viable default. Deletes every stored model, then self-initializes a fresh one from the tool registry — all tools at 0 sats with proper UUIDs. Returns the new model. RESTRICTED to operator — requires proof (nsec-signed).

Credit a patron's ledger from a BTCPay-settled invoice. **RESTRICTED to the operator** — the operator owns the books and is the only party who can issue a manual credit grant. Patrons who believe they paid but never got credits must escalate to the operator's support, who then invokes this tool on their behalf. Use cases: cold-start vault races during check_payment, ncred delivery hiccups, patrons closing Top-Off sheets before settle, any infrastructure incident that left an invoice settled at BTCPay but uncredited on the operator's ledger. Idempotent — if the invoice is already credited (in the patron's ``credited_invoices``), returns success with credits_granted=0.

Re-run ``ensure_schema()`` on every NeonVault this operator uses. Diagnostic / recovery tool for the case where the Neon HTTP SQL API is returning persistent 4xx errors and the operator suspects the schema isn't there or grants are wrong. Idempotent — uses ``CREATE TABLE IF NOT EXISTS`` so a successful re-run is harmless. Returns the per-step result. If any step raises, surfaces the Neon error message inline (0.31.0 reads the SQL error body that earlier wheels swallowed behind ``raise_for_status``). RESTRICTED to operator — requires proof (nsec-signed).

Check the health and configuration of this service. Free.

Check operator readiness. Returns the operator lifecycle state and clear guidance on what to do next. Free. Lifecycle states: - ready: Operator is warm and fully operational — vault AND pricing model verified. Proceed with tool calls. - warming_up: Operator is initializing (cold start). Try a tool call — it will warm up on demand. - misconfigured: Persistence rejected a query with a permanent SQL error (permission denied, missing relation). Paid tools will fail until the operator repairs the database — retrying does not help. - quota_exceeded: The persistence provider (Neon) answered HTTP 402 — the operator's database has exhausted its compute/storage quota, so the books are locked for billing. Paid tools fail; retrying does NOT help. The operator's Authority must restore capacity (upgrade the plan or wait for the quota reset). Free tools remain available. - not_registered: Operator has no Authority relationship yet. Call register_operator first. - no_identity: Operator nsec is not configured. Deployment issue.

Set the active pricing model. RESTRICTED to operator. Requires a valid proof (Schnorr-signed kind-27235 event) proving the caller holds the operator's nsec.

Set the product's store-page DESCRIPTION on a stored design, committed in place. The description is the product's store-page prose — it lives OUTSIDE the design artwork and, on Roastify, syncs to Shopify. It is versioned WITH the design in your git library: read the current one from `roastify_get_design_text` (its `description` field — Roastify's own auto-generated copy is a helpful starting point), refine it, and write it back here. This commits a new version of the SAME design_id (git tracks the diff); it does NOT touch Roastify. The browser courier applies it onto the product on the next Fetch (skipped there if Shopify has locked the field).

Store a Roastify design JSON in your library (a commit in your GitHub repo). The browser courier reads a saved product's design and calls this to shuttle it up. On the way in, the design's fonts[] is REPAIRED — Roastify's own schema migration leaves a lossy fonts[] (a dropped family, a bad weight), so a stashed design would otherwise carry that damage; the repair rebuilds fonts[] from the families the text actually uses so it renders in its intended fonts. Only the load list changes; the text and its fonts are untouched. Inline images are de-duplicated. This does NOT touch Roastify.

Patch a coupon's editable fields. Pass only the fields you want to change. To set a cap to unlimited (NULL in the schema), pass ``clear_uses_per_patron=true`` or ``clear_total_uses=true``. Renaming the code is allowed — existing patron redemption rows survive (they key on coupon id). RESTRICTED to operator — requires proof.

Apply text edits to a stored design and commit a new version of it. The store is configuration management: the edit is committed back to the SAME design_id (git tracks the diff), not saved as a new file. Apply it onto a product with the browser courier. Only the words change — fonts, layout, and images are preserved, and the heavy image is never moved (the design keeps referencing the same content-addressed assets). The box does not resize, so keep each new text within roughly ±10% of the character count of the layer it replaces (see `chars` from get_design_text); longer copy overflows and the merchant fixes it by hand.

Add or update a single operator secret field. Merges into the operator's stored credentials without touching the others — the field-level counterpart to re-delivering the whole bundle over Secure Courier. Use it to rotate one secret (a reissued ``btcpay_api_key``, say) without restating the six you did not change, where any field omitted from a courier reply is destroyed. The value is never echoed back. RESTRICTED to the operator — requires proof (nsec-signed kind-27235 or a cached dpop_token phrase); patron proofs are rejected.

Add or update a single patron credential field. Merges into existing stored credentials without affecting other fields. Useful for setting an account identifier after OAuth, changing a default brain, etc. Free. Proof of npub ownership is required — this is a write to the patron's sensitive credential vault.