Roastify MCP

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 bal

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.

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.

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, patro

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.

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). Th

Check the health and configuration of this service. Free.

No parameter schema on file.

Echo what the client sent with this request. Free. Reports the URL path and query, the headers, the cookies and the MCP request `_meta`. Values are SHA-256 fingerprints, so nothing a client sends is repeated back; equal fingerprints mean equal values. Call it from two conversations and compare: a value that stays the same within one and changes between them identifies the conversation.

No parameter schema on file.

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.

No parameter schema on file.

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.

Check operator readiness. Returns the operator lifecycle state and clear guidance on what to do next. Free. Lifecycle states: - ready: Vault AND pricing model verified on this call. Proceed with tool calls — this is the answer the moment the vault is up. - warming_up: Persistence could not be reached on this call (a transient failure, seen, not assumed). Retry; the next call completes the b

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 wit

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 poppe

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.

Open a Secure Courier channel for patron credential delivery. Sends a welcome DM with a credential template to the patron. 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.

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.

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 echo

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.

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

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 fiel

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 cl

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 ON

Check whether a proof grant 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. Expiry is read from the grant itself; the only store consulted is the patron's revocation watermark. Free, no side effects — touches no relay.

Get DPYC onboarding instructions from the Oracle. Free.

No parameter schema on file.

Get the current DPYC certification tax rate. Free.

No parameter schema on file.

Look up a DPYC community member by npub. Free.

Describe the DPYC ecosystem via the Oracle. Free.

No parameter schema on file.

Get active network advisories from the Oracle. Free.

No parameter schema on file.

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.

No parameter schema on file.

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.

No parameter schema on file.

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.

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).

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 ``

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).

Prepare this operator's database schema again, ignoring the breadcrumb. Diagnostic / recovery tool for when Neon keeps answering 4xx and the operator suspects a table or grant is missing. Every statement is idempotent, so a clean re-run is harmless; the breadcrumb is rewritten at the end. Returns one step per concern, with Neon's own error text inline for any that failed. RESTRICTED to operator

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 mi

No parameter schema on file.

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.

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.

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.

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.

No parameter schema on file.

Create a new operator-owned discount coupon. The coupon owns its binding: `tool_ids` names the tools it discounts, and re-pricing a tool never touches it. A coupon bound to no tool discounts nothing, however many patrons redeem it.

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.

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). tool_ids replaces the coupon's binding — tool ids or MCP tool names, ["*"] for every paid tool, []` t

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.

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 exis

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`.

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`.

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.

No parameter schema on file.

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

List recent Bitcoin notarization records.

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.

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

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

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.

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.

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

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 yoursel

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

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 familie

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

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.

Delete one of your stored designs.

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

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 conten

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

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 con

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 poin