# io.github.lonniev/roastify-mcp (remote · roastify-mcp.fastmcp.app) Roastify Developer API MCP Service — Tollbooth DPYC monetization - Trust score: 73/100 (medium) - Change this week: +4 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-20 ## Components - remote · `roastify-mcp.fastmcp.app`: 73/100 (this document), [markdown](https://verifymcp.io/servers/lonniev-roastify-mcp/roastify-mcp.md), [page](https://verifymcp.io/servers/lonniev-roastify-mcp/roastify-mcp) ## Channel facts - Endpoint: `https://roastify-mcp.fastmcp.app/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `0.22.6` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-09-20. - **Endpoint Security**: 57/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation not fully verified: no authorisation is required to call this server, and 69 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. - HTTPS is enforced; there's no plaintext access path. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 63/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 14181 tokens (~205/item across 69 items; 69 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 90/100 - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 92/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 73% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Tool Safety**: 75/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - 0 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "roastify_forget_credentials" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. - An AI judge read all 70 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). ## Install ### How do I install the io.github.lonniev/roastify-mcp server? io.github.lonniev/roastify-mcp is a hosted endpoint at https://roastify-mcp.fastmcp.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http lonniev-roastify-mcp 'https://roastify-mcp.fastmcp.app/mcp' ``` ### Cursor ```json { "mcpServers": { "lonniev-roastify-mcp": { "url": "https://roastify-mcp.fastmcp.app/mcp" } } } ``` ### VS Code ```json { "servers": { "lonniev-roastify-mcp": { "type": "http", "url": "https://roastify-mcp.fastmcp.app/mcp" } } } ``` ### Codex ```toml [mcp_servers.lonniev-roastify-mcp] url = "https://roastify-mcp.fastmcp.app/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "lonniev-roastify-mcp": { "type": "remote", "url": "https://roastify-mcp.fastmcp.app/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add lonniev-roastify-mcp --url 'https://roastify-mcp.fastmcp.app/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: lonniev-roastify-mcp: url: "https://roastify-mcp.fastmcp.app/mcp" ``` ### Netclaw ```json { "McpServers": { "lonniev-roastify-mcp": { "Transport": "http", "Url": "https://roastify-mcp.fastmcp.app/mcp" } } } ``` ### Vellum ```bash assistant mcp add lonniev-roastify-mcp -t streamable-http -u 'https://roastify-mcp.fastmcp.app/mcp' ``` ### Other ```json { "mcpServers": { "lonniev-roastify-mcp": { "type": "http", "url": "https://roastify-mcp.fastmcp.app/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-09-20 (score 73, +1) No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-18 (score 72, +1) No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-16 (score 71, +1) No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-15 (score 70, +10) - [security improvement] Transport: fail → pass ### 2026-09-14 (score 60, −9) - [security regression] Transport: pass → fail ### 2026-09-12 (score 69, +1) No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-10 (score 68, +1) No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-07 (score 67, +1) - [functional] MCP protocol: Implements a current MCP spec version (2026-07-28). - [functional] MCP protocol version: 2025-11-25 → 2026-07-28 - [functional] Server version: 3.4.7 → 4.0.3 - [cosmetic] Tool “roastify_account_statement” changed its title: Roastify Account Statement - [cosmetic] Tool “roastify_account_statement_infographic” changed its title: Roastify Account Statement Infographic - [cosmetic] Tool “roastify_add_design_element” changed its title: Roastify Add Design Element - [cosmetic] Tool “roastify_adoption_status” changed its title: Roastify Adoption Status - [cosmetic] Tool “roastify_artwork_status” changed its title: Roastify Artwork Status - [cosmetic] Tool “roastify_browse_catalog” changed its title: Roastify Browse Catalog - [cosmetic] Tool “roastify_check_authority_balance” changed its title: Roastify Check Authority Balance - [cosmetic] Tool “roastify_check_balance” changed its title: Roastify Check Balance - [cosmetic] Tool “roastify_check_payment” changed its title: Roastify Check Payment - [cosmetic] Tool “roastify_check_price” changed its title: Roastify Check Price - [cosmetic] Tool “roastify_check_proof_status” changed its title: Roastify Check Proof Status - [cosmetic] Tool “roastify_check_stock” changed its title: Roastify Check Stock - [cosmetic] Tool “roastify_delete_coupon” changed its title: Roastify Delete Coupon - [cosmetic] Tool “roastify_delete_design” changed its title: Roastify Delete Design - [cosmetic] Tool “roastify_delete_operator_credential” changed its title: Roastify Delete Operator Credential - [cosmetic] Tool “roastify_delete_patron_credential” changed its title: Roastify Delete Patron Credential - [cosmetic] Tool “roastify_fetch_design” changed its title: Roastify Fetch Design - [cosmetic] Tool “roastify_forget_coupon” changed its title: Roastify Forget Coupon - [cosmetic] Tool “roastify_forget_credentials” changed its title: Roastify Forget Credentials - [cosmetic] Tool “roastify_generate_artwork” changed its title: Roastify Generate Artwork - [cosmetic] Tool “roastify_get_blend” changed its title: Roastify Get Blend - [cosmetic] Tool “roastify_get_catalog_product” changed its title: Roastify Get Catalog Product - [cosmetic] Tool “roastify_get_design_text” changed its title: Roastify Get Design Text - [cosmetic] Tool “roastify_get_my_product” changed its title: Roastify Get My Product - [cosmetic] Tool “roastify_get_nostr_profile” changed its title: Roastify Get Nostr Profile - [cosmetic] Tool “roastify_get_notarization_proof” changed its title: Roastify Get Notarization Proof - [cosmetic] Tool “roastify_get_operator_onboarding_status” changed its title: Roastify Get Operator Onboarding Status - [cosmetic] Tool “roastify_get_patron_credential_fields” changed its title: Roastify Get Patron Credential Fields - [cosmetic] Tool “roastify_get_patron_onboarding_status” changed its title: Roastify Get Patron Onboarding Status - [cosmetic] Tool “roastify_get_pricing_model” changed its title: Roastify Get Pricing Model - [cosmetic] Tool “roastify_list_canonical_identities” changed its title: Roastify List Canonical Identities - [cosmetic] Tool “roastify_list_constraint_types” changed its title: Roastify List Constraint Types - [cosmetic] Tool “roastify_list_coupons” changed its title: Roastify List Coupons - [cosmetic] Tool “roastify_list_design_versions” changed its title: Roastify List Design Versions - [cosmetic] Tool “roastify_list_designs” changed its title: Roastify List Designs - [cosmetic] Tool “roastify_list_my_coupons” changed its title: Roastify List My Coupons - [cosmetic] Tool “roastify_list_my_products” changed its title: Roastify List My Products - [cosmetic] Tool “roastify_list_notarizations” changed its title: Roastify List Notarizations - [cosmetic] Tool “roastify_mint_coupon” changed its title: Roastify Mint Coupon - [cosmetic] Tool “roastify_move_elements” changed its title: Roastify Move Elements - [cosmetic] Tool “roastify_notarize_ledger” changed its title: Roastify Notarize Ledger - [cosmetic] Tool “roastify_oracle_about” changed its title: Roastify Oracle About - [cosmetic] Tool “roastify_oracle_get_tax_rate” changed its title: Roastify Oracle Get Tax Rate - [cosmetic] Tool “roastify_oracle_how_to_join” changed its title: Roastify Oracle How To Join - [cosmetic] Tool “roastify_oracle_lookup_member” changed its title: Roastify Oracle Lookup Member - [cosmetic] Tool “roastify_oracle_network_advisory” changed its title: Roastify Oracle Network Advisory - [cosmetic] Tool “roastify_publish_nostr_profile” changed its title: Roastify Publish Nostr Profile - [cosmetic] Tool “roastify_purchase_credits” changed its title: Roastify Purchase Credits - [cosmetic] Tool “roastify_receive_credentials” changed its title: Roastify Receive Credentials - [cosmetic] Tool “roastify_receive_npub_proof” changed its title: Roastify Receive Npub Proof - [cosmetic] Tool “roastify_receive_patron_credentials” changed its title: Roastify Receive Patron Credentials - [cosmetic] Tool “roastify_redeem_coupon” changed its title: Roastify Redeem Coupon - [cosmetic] Tool “roastify_report_issue” changed its title: Roastify Report Issue - [cosmetic] Tool “roastify_request_adoption” changed its title: Roastify Request Adoption - [cosmetic] Tool “roastify_request_credential_channel” changed its title: Roastify Request Credential Channel - [cosmetic] Tool “roastify_request_npub_proof” changed its title: Roastify Request Npub Proof - [cosmetic] Tool “roastify_request_patron_credentials” changed its title: Roastify Request Patron Credentials - [cosmetic] Tool “roastify_reset_pricing_model” changed its title: Roastify Reset Pricing Model - [cosmetic] Tool “roastify_restore_credits” changed its title: Roastify Restore Credits - [cosmetic] Tool “roastify_restore_neon_schema” changed its title: Roastify Restore Neon Schema - [cosmetic] Tool “roastify_service_status” changed its title: Roastify Service Status - [cosmetic] Tool “roastify_session_status” changed its title: Roastify Session Status - [cosmetic] Tool “roastify_set_pricing_model” changed its title: Roastify Set Pricing Model - [cosmetic] Tool “roastify_set_product_description” changed its title: Roastify Set Product Description - [cosmetic] Tool “roastify_stash_design” changed its title: Roastify Stash Design - [cosmetic] Tool “roastify_update_coupon” changed its title: Roastify Update Coupon - [cosmetic] Tool “roastify_update_design_text” changed its title: Roastify Update Design Text - [cosmetic] Tool “roastify_update_operator_credential” changed its title: Roastify Update Operator Credential - [cosmetic] Tool “roastify_update_patron_credential” changed its title: Roastify Update Patron Credential ## MCP tools (69) ### `roastify_check_balance` (~209 tokens) Roastify Check Balance 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. Input parameters: - `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr ' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL… - `npub` (string, required): The Nostr public key (npub1...) whose balance to check. ### `roastify_purchase_credits` (~199 tokens) Roastify Purchase Credits 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. Input parameters: - `amount_sats` (integer): Satoshis to purchase (default 1000). - `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr ' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL… - `npub` (string, required): The Nostr public key (npub1...) the credits will fund. ### `roastify_check_payment` (~195 tokens) Roastify Check Payment 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. Input parameters: - `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr ' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL… - `invoice_id` (string, required): The invoice ID returned by purchase_credits. - `npub` (string, required): The Nostr public key (npub1...) that purchased the invoice. ### `roastify_restore_credits` (~234 tokens) Roastify Restore Credits 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. Input parameters: - `dpop_token` (string, required): A kind-27235 Nostr event signed by the OPERATOR's nsec for this tool. Patron proofs are rejected. - `invoice_id` (string, required): The BTCPay invoice ID to verify and credit. - `patron_npub` (string, required): The patron's npub whose ledger receives the grant. ### `roastify_account_statement` (~223 tokens) Roastify Account Statement 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. Input parameters: - `days` (integer): Number of days of daily usage history to include (default 30). - `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr ' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL… - `npub` (string, required): The patron's Nostr public key (npub1...). ### `roastify_account_statement_infographic` (~223 tokens) Roastify Account Statement Infographic 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. Input parameters: - `days` (integer): Number of days of daily usage history to include (default 30). - `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr ' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL… - `npub` (string, required): The Nostr public key (npub1...) whose statement to render. ### `roastify_report_issue` (~348 tokens) Roastify Report Issue 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. Input parameters: - `body` (string, required): The details — which tool, what was wrong, what you expected. - `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr ' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL… - `npub` (string, required): Your Nostr public key (npub1...); the report's author of record. - `title` (string, required): One-line summary of the problem. - `tool_name` (string): Optional: the specific tool the report is about (e.g. "schwab_get_option_chain"). ### `roastify_service_status` (~21 tokens) Roastify Service Status Check the health and configuration of this service. Free. ### `roastify_get_operator_onboarding_status` (~57 tokens) Roastify Get Operator Onboarding Status 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. ### `roastify_get_patron_onboarding_status` (~138 tokens) Roastify Get Patron Onboarding Status 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. Input parameters: - `dpop_token` (string, required): A kind-27235 Nostr event signed by patron_npub for this tool. - `patron_npub` (string, required): The patron's Nostr public key (npub1...). ### `roastify_session_status` (~286 tokens) Roastify Session Status 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. Input parameters: - `patron_npub` (string): Optional. If supplied, the response includes an ``upstream_oauth`` block with the patron's stored OAuth token expiry (runtime-derived from vault state) so a client can refresh proactively rather than… ### `roastify_request_credential_channel` (~251 tokens) Roastify Request Credential Channel 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. Input parameters: - `sender_npub` (string): Required. The npub to send the template to. - `service` (string): Required. The credential service name (e.g., from get_operator_onboarding_status or get_patron_onboarding_status). ### `roastify_receive_credentials` (~323 tokens) Roastify Receive Credentials 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. Input parameters: - `credential_card` (string): Optional. An ncred1... card to redeem directly (bypasses the relay drain; dpop_token not needed). - `dpop_token` (string): Required. The session phrase returned by request_credential_channel for this exact channel. - `sender_npub` (string): Required. The npub that sent the credentials. - `service` (string): Required. The credential service name (must match the service used in request_credential_channel). ### `roastify_forget_credentials` (~196 tokens) Roastify Forget Credentials 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. Input parameters: - `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr ' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL… - `npub` (string, required): The Nostr public key (npub1...) whose credentials to forget. - `service` (string, required): The credential service to forget. ### `roastify_request_patron_credentials` (~46 tokens) Roastify Request Patron Credentials Open a Secure Courier channel for patron credential delivery. Sends a welcome DM with a credential template to the patron. Free. Input parameters: - `sender_npub` (string) ### `roastify_receive_patron_credentials` (~123 tokens) Roastify Receive Patron Credentials 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. Input parameters: - `credential_card` (string) - `dpop_token` (string) - `sender_npub` (string) ### `roastify_update_patron_credential` (~218 tokens) Roastify Update Patron Credential 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. Input parameters: - `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr ' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL… - `field` (string, required): The credential field name to set. - `npub` (string, required): The patron's Nostr public key (npub1...). - `value` (string, required): The value to store. ### `roastify_update_operator_credential` (~182 tokens) Roastify Update Operator Credential 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. Input parameters: - `dpop_token` (string, required): Operator proof for this tool. - `field` (string, required): The operator credential field to set. Must be declared in the operator's credential template. - `value` (string, required): The value to store. ### `roastify_delete_patron_credential` (~185 tokens) Roastify Delete Patron Credential 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. Input parameters: - `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr ' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL… - `field` (string, required): The credential field name to remove. - `npub` (string, required): The patron's Nostr public key (npub1...). ### `roastify_delete_operator_credential` (~227 tokens) Roastify Delete Operator Credential 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. Input parameters: - `dpop_token` (string, required): Operator proof for this tool. - `field` (string, required): The operator credential field to remove (templated or not). ### `roastify_get_patron_credential_fields` (~234 tokens) Roastify Get Patron Credential Fields 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). Input parameters: - `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr ' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL… - `npub` (string, required): The patron's Nostr public key (npub1...). ### `roastify_request_npub_proof` (~488 tokens) Roastify Request Npub Proof 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. Input parameters: - `patron_npub` (string): Required. The patron's npub to request proof from. - `reason` (string): Optional. A human-readable purpose for the request ("I'm working on your request XYZ and need the Operator to do ABC for you"). Signed into the provenance attestation and shown in the DM, so the reci… - `verify_at` (string): Optional. A free-form statement of WHERE you (the initiating agent) already showed this proof's one-time code to the user — a URL, or "your Claude.ai conversation", "the Grok session". The OAuth 2.0… ### `roastify_receive_npub_proof` (~310 tokens) Roastify Receive Npub Proof 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. Input parameters: - `dpop_token` (string): Required. The dpop_token returned by request_npub_proof. - `patron_npub` (string): Required. The patron's npub to receive proof from. ### `roastify_check_proof_status` (~138 tokens) Roastify Check Proof Status 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. Input parameters: - `dpop_token` (string): Required. The dpop_token phrase returned by ``request_npub_proof`` / ``receive_npub_proof``. - `patron_npub` (string): Required. The patron's npub (npub1...). ### `roastify_oracle_how_to_join` (~25 tokens) Roastify Oracle How To Join Get DPYC onboarding instructions from the Oracle. Free. ### `roastify_oracle_get_tax_rate` (~24 tokens) Roastify Oracle Get Tax Rate Get the current DPYC certification tax rate. Free. ### `roastify_oracle_lookup_member` (~33 tokens) Roastify Oracle Lookup Member Look up a DPYC community member by npub. Free. Input parameters: - `npub` (string, required) ### `roastify_oracle_about` (~22 tokens) Roastify Oracle About Describe the DPYC ecosystem via the Oracle. Free. ### `roastify_oracle_network_advisory` (~25 tokens) Roastify Oracle Network Advisory Get active network advisories from the Oracle. Free. ### `roastify_check_authority_balance` (~73 tokens) Roastify Check Authority Balance 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. ### `roastify_get_pricing_model` (~51 tokens) Roastify Get Pricing Model 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. ### `roastify_set_pricing_model` (~68 tokens) Roastify Set Pricing Model 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. Input parameters: - `dpop_token` (string) - `model_json` (string, required) ### `roastify_reset_pricing_model` (~81 tokens) Roastify Reset Pricing Model 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). Input parameters: - `dpop_token` (string) ### `roastify_request_adoption` (~193 tokens) Roastify Request Adoption 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. Input parameters: - `authority_npub` (string, required): npub of the Authority to request adoption from. - `dpop_token` (string): operator-npub ownership proof (inline kind-27235 or cached token). - `note` (string): optional message for the Authority owner. - `service_url` (string): this operator's MCP endpoint (advertised to the Authority). ### `roastify_adoption_status` (~70 tokens) Roastify Adoption Status 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). Input parameters: - `authority_npub` (string, required) - `dpop_token` (string) ### `roastify_restore_neon_schema` (~148 tokens) Roastify Restore Neon Schema 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). Input parameters: - `dpop_token` (string) ### `roastify_list_canonical_identities` (~250 tokens) Roastify List Canonical Identities 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. ### `roastify_get_nostr_profile` (~88 tokens) Roastify Get Nostr Profile 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. Input parameters: - `npub` (string) ### `roastify_publish_nostr_profile` (~150 tokens) Roastify Publish Nostr Profile 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. Input parameters: - `npub` (string): The patron's Nostr public key the event must be signed by. - `signed_event` (string): A JSON-encoded, client-signed kind-0 event. ### `roastify_check_price` (~180 tokens) Roastify Check Price 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. Input parameters: - `dpop_token` (string) - `npub` (string) - `tool_id` (string, required): Either the tool's UUID (from the pricing model) or a bare capability string (e.g. ``"deal_scenario"``). FE callers usually have the capability name; this resolves both so the FE doesn't need to deriv… - `tool_kwargs` (string): Optional JSON object with tool call parameters for ad valorem / categorical-multiplier pricing preview (e.g. '{"amount_sats": 5000}' or '{"difficulty": "sovereign", "mode": "live"}'). ### `roastify_list_constraint_types` (~51 tokens) Roastify List Constraint Types 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. ### `roastify_mint_coupon` (~152 tokens) Roastify Mint Coupon Create a new operator-owned discount coupon. Input parameters: - `discount_percent` (number, required): Percentage off the base price (0-100). - `dpop_token` (string) - `name` (string, required): The catchy code patrons type to redeem (operator-scoped uniqueness). - `total_uses`: Aggregate cap across all patrons (default None = unlimited). - `uses_per_patron`: How many tool calls one patron can claim the discount on (default 1; pass null/None for unlimited within the window). - `valid_from` (string, required): ISO-8601 datetime when the coupon becomes active. - `valid_until` (string, required): ISO-8601 datetime when the coupon expires. ### `roastify_list_coupons` (~71 tokens) Roastify List Coupons 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. Input parameters: - `dpop_token` (string) ### `roastify_update_coupon` (~167 tokens) Roastify Update Coupon 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. Input parameters: - `clear_total_uses` (boolean) - `clear_uses_per_patron` (boolean) - `coupon_id` (string, required) - `discount_percent` - `dpop_token` (string) - `name` - `total_uses` - `uses_per_patron` - `valid_from` - `valid_until` ### `roastify_delete_coupon` (~82 tokens) Roastify Delete Coupon 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. Input parameters: - `coupon_id` (string, required) - `dpop_token` (string) ### `roastify_redeem_coupon` (~134 tokens) Roastify Redeem Coupon 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. Input parameters: - `code` (string, required) - `dpop_token` (string) - `npub` (string, required) ### `roastify_list_my_coupons` (~89 tokens) Roastify List My Coupons 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``. Input parameters: - `dpop_token` (string) - `npub` (string, required) ### `roastify_forget_coupon` (~88 tokens) Roastify Forget Coupon 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``. Input parameters: - `coupon_id` (string, required) - `dpop_token` (string) - `npub` (string, required) ### `roastify_notarize_ledger` (~54 tokens) Roastify Notarize Ledger 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. ### `roastify_get_notarization_proof` (~70 tokens) Roastify Get Notarization Proof Generate a Merkle inclusion proof that a patron's balance was included in a Bitcoin-notarized snapshot. Input parameters: - `notarization_id` (string, required): The notarization record ID. - `npub` (string, required): The patron's Nostr public key (npub1...). ### `roastify_list_notarizations` (~52 tokens) Roastify List Notarizations List recent Bitcoin notarization records. Input parameters: - `limit` (integer): Maximum records to return (default 20). - `status` (string): Optional filter (e.g., 'submitted', 'confirmed'). ### `roastify_browse_catalog` (~111 tokens) Roastify Browse Catalog 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. Input parameters: - `dpop_token` (string) - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. ### `roastify_get_catalog_product` (~74 tokens) Roastify Get Catalog Product Get one catalog product with its variants, sizes, prices, and dieline. Input parameters: - `dpop_token` (string) - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. - `product_id` (string, required): The catalog product id from browse_catalog. ### `roastify_get_blend` (~73 tokens) Roastify Get Blend Get one coffee blend: roast level, decaf status, and its variants. Input parameters: - `blend_id` (string, required): The blend id from browse_catalog. - `dpop_token` (string) - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. ### `roastify_list_my_products` (~118 tokens) Roastify List My Products 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. Input parameters: - `cursor` (string): Page cursor from a previous call's end_cursor. Omit for page 1. - `dpop_token` (string) - `limit` (integer): Items per page (1-100, default 20). - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. ### `roastify_get_my_product` (~154 tokens) Roastify Get My Product 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. Input parameters: - `dpop_token` (string) - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. - `product_id` (string, required): Your product id from list_my_products. ### `roastify_check_stock` (~75 tokens) Roastify Check Stock Check Roastify stock for one SKU, or the whole stock list. Input parameters: - `dpop_token` (string) - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. - `sku` (string): A variant SKU. Omit to get the full stock list. ### `roastify_generate_artwork` (~252 tokens) Roastify Generate Artwork 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. Input parameters: - `client_req_id` (string): Your own idempotency key. Reusing it makes a repeated request safe — Roastify will not generate the artwork twice. - `dpop_token` (string) - `fields` (array, required): Placeholders to rewrite, each {"fieldId": "placeholder_title", "type": "text"|"image", "value": "..."}. An image value must be an https:// URL. - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. - `product_id` (string, required): A saved design's id, from list_my_products. ### `roastify_artwork_status` (~93 tokens) Roastify Artwork Status Check a Roastify artwork job. Free — polling never costs anything. A finished job carries ``artwork_url``; a failed one carries ``error``. Input parameters: - `dpop_token` (string) - `job_id` (string, required): The job id returned by roastify_generate_artwork. - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. ### `roastify_stash_design` (~431 tokens) Roastify Stash Design 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. Input parameters: - `commit_message` (string): A specific description of WHAT changed and WHY — write a real commit message, not a placeholder like 'save this' or 'update'. Required. - `description` (string): The product's store-page description at stash time, versioned with the design so Fetch can re-apply it to a target product. - `design` (object, required): The full Roastify design JSON object (elements/faceBackgrounds…). - `design_id` (string): Optional explicit folder id. Omit and the id is the slug of the label, so re-stashing the same design commits a new version in place instead of creating a duplicate. - `dpop_token` (string) - `label` (string): Your name for this design, e.g. "Ethiopian — light". - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. - `product_id` (string): The Roastify product id it came from, for your reference. - `source_title` (string): The product's title at stash time, for your reference. - `version_tag` (string): The NEXT semver version (MAJOR.MINOR.PATCH like 1.2.3, no 'v'); check roastify_list_design_versions and increment. Required; reusing one is refused. ### `roastify_fetch_design` (~117 tokens) Roastify Fetch Design Fetch one of your stored designs in full, with its images re-inlined. Input parameters: - `design_id` (string, required): The id from roastify_stash_design or roastify_list_designs. - `dpop_token` (string) - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. - `ref` (string): Optional git ref (a commit sha or version tag) to fetch a specific version — from roastify_list_design_versions. Omit for the latest. ### `roastify_list_design_versions` (~141 tokens) Roastify List Design Versions 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. Input parameters: - `design_id` (string, required): The id from roastify_list_designs. - `dpop_token` (string) - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. ### `roastify_list_designs` (~54 tokens) Roastify List Designs List your stored designs — metadata only, newest first. Input parameters: - `dpop_token` (string) - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. ### `roastify_delete_design` (~65 tokens) Roastify Delete Design Delete one of your stored designs. Input parameters: - `design_id` (string, required): The id from roastify_list_designs. - `dpop_token` (string) - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. ### `roastify_get_design_text` (~828 tokens) Roastify Get Design Text 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 no… Input parameters: - `design_id` (string, required): The id from roastify_list_designs. - `dpop_token` (string) - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. ### `roastify_update_design_text` (~378 tokens) Roastify Update Design Text 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. Input parameters: - `commit_message` (string): A specific description of WHAT changed and WHY — a real commit message, not a placeholder like 'save this' or 'update'. Required. - `design_id` (string, required): The design to edit, from roastify_list_designs. - `dpop_token` (string) - `edits` (object, required): A map of {layer_id: new_text}, using ids from roastify_get_design_text. Include every layer that should change, including ones that repeat a value or embed it in a longer blurb. A JSON object string… - `label` (string): Rename the design (optional). Defaults to keeping its current label. - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. - `version_tag` (string): The NEXT semver version (MAJOR.MINOR.PATCH, e.g. 1.3.0, no 'v') — call roastify_list_design_versions and increment. Required; reusing one is refused. ### `roastify_add_design_element` (~780 tokens) Roastify Add Design Element 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. Input parameters: - `client_req_id` (string): Your idempotency key. - `commit_message` (string): A specific description of WHAT changed and WHY — a real commit message, not a placeholder like 'save this' or 'update'. Required. - `design_id` (string, required): The design to add to, from roastify_list_designs. - `dpop_token` (string) - `face` (string): The panel to place it on — one of the `panels` from get_design_text (e.g. "right"). On multi-panel boxes the element must fall inside that panel; face is required there. On single-face products (Tube… - `height` (integer): Image frame height in design units (kind="image" only). Defaults to the donor image's height when src_from is set. - `kind` (string): "text" (default) or "image". - `label` (string): Rename the design (optional). Defaults to keeping its current label. - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. - `position`: Where to place it. Either absolute {"x": N, "y": M} (top-left in design units), or relative to an existing element: {"below"|"above"|"rightOf"|"leftOf": "layer_id", "gap": G}. Relative is best when t… - `src` (string): An image src already present in this design (kind="image"); alternative to src_from. New uploads are refused — only reuse an asset already on the design. - `src_from` (string): Existing IMAGE element id whose src to copy (kind="image"). - `style_from` (string): An existing TEXT layer id (from get_design_text) whose font, size, weight, colour, alignment, and leading the new text element inherits. Required when kind="text". - `text` (string): The element's text (\n for line breaks). Required when kind="text". - `version_tag` (string): The NEXT semver version (MAJOR.MINOR.PATCH, e.g. 1.3.0, no 'v') — call roastify_list_design_versions and increment. Required; reusing one is refused. - `width` (integer): The text box (wrap) width, or the image frame width, in design units. Defaults to the panel width minus margins for text; required for images when not defaulting from the donor. ### `roastify_move_elements` (~730 tokens) Roastify Move Elements 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. Input parameters: - `commit_message` (string): A specific description of WHAT changed and WHY — a real commit message, not a placeholder like 'save this' or 'update'. Required. - `design_id` (string, required): The design to edit, from roastify_list_designs. - `dpop_token` (string) - `edits` (array, required): A list of geometry edits, each one of: - group shift: {"ids": ["a", "b", ...], "dx": N, "dy": M} — add the same delta to every listed element's x/y (design units; +dy is down, +dx is right). Use… - `label` (string): Rename the design (optional). Defaults to keeping its current label. - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. - `version_tag` (string): The NEXT semver version (MAJOR.MINOR.PATCH, e.g. 1.3.0, no 'v') — call roastify_list_design_versions and increment. Required; reusing one is refused. ### `roastify_set_product_description` (~333 tokens) Roastify Set Product Description 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). Input parameters: - `commit_message` (string): A specific description of WHAT changed and WHY — a real commit message, not a placeholder like 'save this' or 'update'. Required. - `description` (string, required): The new store-page description prose. - `design_id` (string, required): The design to edit, from roastify_list_designs. - `dpop_token` (string) - `label` (string): Rename the design (optional). Defaults to keeping its current label. - `npub` (string): Required. Your Nostr public key (npub1...) for credit billing. - `version_tag` (string): The NEXT semver version (MAJOR.MINOR.PATCH, e.g. 1.3.0, no 'v') — call roastify_list_design_versions and increment. Required; reusing one is refused. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lonniev-roastify-mcp/roastify-mcp#diagnostics ## Score history - 2026-09-20: 73 - 2026-09-19: 72 - 2026-09-18: 72 - 2026-09-17: 71 - 2026-09-16: 71 - 2026-09-15: 70 - 2026-09-14: 60 - 2026-09-13: 69 - 2026-09-12: 69 - 2026-09-11: 68 - 2026-09-10: 68 - 2026-09-09: 67 - 2026-09-08: 67 - 2026-09-07: 67 - 2026-09-06: 66 - 2026-09-05: 66 - 2026-09-04: 65 - 2026-09-03: 65 - 2026-09-02: 64 - 2026-09-01: 64 - 2026-08-31: 63 - 2026-08-30: 63 - 2026-08-29: 62 - 2026-08-28: 62 - 2026-08-27: 61 - 2026-08-26: 61 - 2026-08-25: 60 - 2026-08-24: 60 ## Common questions ### What is the io.github.lonniev/roastify-mcp server? io.github.lonniev/roastify-mcp is listed in the public MCP registry as io.github.lonniev/roastify-mcp. Roastify Developer API MCP Service, Tollbooth DPYC monetization. This page covers its hosted endpoint (https://roastify-mcp.fastmcp.app/mcp). ### Is the io.github.lonniev/roastify-mcp server safe to use? io.github.lonniev/roastify-mcp scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the io.github.lonniev/roastify-mcp server expose? io.github.lonniev/roastify-mcp exposes 69 tools: roastify_check_balance, roastify_purchase_credits, roastify_check_payment, roastify_restore_credits, roastify_account_statement, and 64 more. Their descriptions and schemas cost roughly 12,352 tokens of context every time the server is loaded. ### Does the io.github.lonniev/roastify-mcp server require authentication? No. We connected to io.github.lonniev/roastify-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the io.github.lonniev/roastify-mcp server still maintained? io.github.lonniev/roastify-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://roastify-mcp.fastmcp.app/mcp - Repository: https://github.com/lonniev/roastify-mcp - Changelog RSS feed: https://verifymcp.io/servers/lonniev-roastify-mcp/roastify-mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/lonniev-roastify-mcp/roastify-mcp.json - HTML version of this page: https://verifymcp.io/servers/lonniev-roastify-mcp/roastify-mcp