Connect-MCP

io.github.lonniev/roastify-mcp

io.github.lonniev/roastify-mcp · v0.22.6

Roastify Developer API MCP Service — Tollbooth DPYC monetization

MCPremoteno credentials

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 70 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

A 100/100

What it does: 70 tools · 37 read, 33 write (incl. delete/pay) · Developer tools, E-commerce

Test call roastify_service_status: worked (831 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +20
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://roastify-mcp.fastmcp.app/mcp

Tools

70 tools listed at last check
  • 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 re
  • 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.
  • 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.
  • 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
  • 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
  • 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`` be
  • 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 attribute
  • roastify_service_status Check the health and configuration of this service. Free.
  • roastify_request_echo 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
  • 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 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 beca
  • roastify_session_status 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 rea
  • 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 servi
  • 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,
  • 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.
  • 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.
  • 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 ins
  • 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 credenti
  • 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
  • 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.
  • 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 stor
  • 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 config
  • 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_
  • 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_
  • roastify_check_proof_status 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
  • roastify_oracle_how_to_join Get DPYC onboarding instructions from the Oracle. Free.
  • roastify_oracle_get_tax_rate Get the current DPYC certification tax rate. Free.
  • roastify_oracle_lookup_member Look up a DPYC community member by npub. Free.
  • roastify_oracle_about Describe the DPYC ecosystem via the Oracle. Free.
  • roastify_oracle_network_advisory Get active network advisories from the Oracle. Free.
  • 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
  • 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 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.
  • 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).
  • 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 re
  • 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).
  • roastify_restore_neon_schema 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 o
  • 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 g
  • 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.
  • 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
  • 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.
  • 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 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.
  • 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.
  • 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). ``tool_ids``
  • 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.
  • 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 credi
  • 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``.
  • 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``.
  • 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 Generate a Merkle inclusion proof that a patron's balance was included in a Bitcoin-notarized snapshot.
  • roastify_list_notarizations List recent Bitcoin notarization records.
  • 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 fro
  • roastify_get_catalog_product Get one catalog product with its variants, sizes, prices, and dieline.
  • roastify_get_blend Get one coffee blend: roast level, decaf status, and its variants.
  • 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.
  • 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 on
  • roastify_check_stock Check Roastify stock for one SKU, or the whole stock list.
  • 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
  • roastify_artwork_status Check a Roastify artwork job. Free — polling never costs anything. A finished job carries ``artwork_url``; a failed one carries ``error``.
  • 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),
  • roastify_fetch_design Fetch one of your stored designs in full, with its images re-inlined.
  • 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
  • roastify_list_designs List your stored designs — metadata only, newest first.
  • roastify_delete_design Delete one of your stored designs.
  • 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, s
  • 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 im
  • 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,
  • 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
  • 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_d

Badge

Connect-MCP badge for io.github.lonniev/roastify-mcp

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.lonniev/roastify-mcp.svg)](https://clawy.uk/mcp/s/io.github.lonniev/roastify-mcp)

Repository