Roastify MCP server
online · 96% uptimeRoastify Developer API MCP Service — Tollbooth DPYC monetization
0 stars
Reviews
Write oneNobody has reviewed Roastify yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Roastify tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 332ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Roastify compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 97/100
- higher than 98% of 48,255 servers
- Uptime
- 96%
- of our recent checks; the typical remote server answers 100%
- Response time
- 444 ms
- faster than 33% of 30,031 servers
Release history: 2 versions in the registry since 2026-08-24, latest 2026-10-21, typically one every 58 days.
Install Roastify in Claude Code, Cursor or VS Code
claude mcp add --transport http roastify-mcp https://roastify-mcp.fastmcp.app/mcp
What the publisher says
From the Roastify repository's README, as published. We do not edit it. Read it on GitHub
roastify-mcp
A Tollbooth DPYC operator for the Roastify Developer API. Roastify is a white-label coffee dropshipper: it roasts, prints branded packaging, and ships direct to customers.
This operator lets an AI agent read the Roastify catalog and generate packaging artwork, paid for in Bitcoin Lightning satoshis with no account, no KYC, and no subscription.
What you're building
YOU (operator, human in the loop)
│ │
│ set & tune prices │ drive credential intake
▼ ▼
┌───────────────┐ ┌──────────────────────────────────────────────┐
│ Pricing Studio│ prices │ Roastify — YOUR OPERATOR MCP │
│ (iOS) ├───────▶│ FastMCP · deployed on Horizon │
└───────────────┘ Neon │ ┌────────────────────────────────────────┐ │
│ │ roastify domain module ◀─ Roastify API │ │
Patron (Citizen) │ │ @runtime.paid_tool(FROZEN_UUID) tools │ │
+ MCP client ─────────▶│ ├────────────────────────────────────────┤ │
(Claude, etc.) npub │ │ tollbooth-dpyc SDK (the wheel) │ │
+sats │ │ ledger · vault (AES-256-GCM) · pricing │ │
│ │ /ConstraintGate · Secure Courier·audit │ │
│ └────────────────────────────────────────┘ │
└───┬─────────┬──────────┬───────────┬─────────┘
▼ ▼ ▼ ▼
Neon Postgres BTCPay▶ Onboarding roadmap
TOLLBOOTHNOSTROPERATOR_NSEC.
- Nostr keypair — generate one (nak key generate). The nsec is the only env var:
btcpaystoreid) by Nostr DM. They are vaulted, never put in the environment.
- Sponsor Authority — register; it provisions your Neon schema automatically.
- Secure Courier — deliver your BTCPay secrets (btcpayhost, btcpayapi_key,
- Set prices in Pricing Studio — see below. Tools start unpriced and uncallable.
- Deploy on Prefect Horizon — .fastmcp.yaml is ready.
Get Pricing Studio
Your tools ship unpriced, and nobody can call a paid tool that has no price. Pricing Studio (iOS) is the operator console: it reads and writes the pricing model live in Neon, so prices never live in code — see tollbooth-pricing-studio.
That indirection is the point. Dynamic per-tool pricing — surge, happy-hour, loyalty discounts, free trials for a first-time patron — is what DPYC gives you that a flat paywall never could.
Bring your own Roastify key
Every patron delivers their own Roastify API key through the Secure Courier, vaulted per npub. There is no operator-held key and no fallback path.
This follows from the domain rather than being a policy choice. Roastify scopes the catalog, saved designs, and plan tier to the merchant account behind the key — a patron on Base sees a different catalog than one on Pro. A single operator-held key would hand one merchant's world to every caller, which is a wrong answer rather than a limitation to work around. It also means this operator never holds a credential it could misuse, and revoking your key in the Merchant App severs access without involving the operator.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-10-31restoreB → Ascore 97
Roastify: common questions
- Is Roastify MCP server safe?
- Yes, by our scan: it is graded A (97/100). Read the Roastify safety report
- How do I install Roastify?
- It runs remotely at roastify-mcp.fastmcp.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Roastify need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is Roastify maintained?
- The last commit was 4 days ago (2026-10-31). The latest release is v0.23.0.
- Is Roastify up?
- 96% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Roastify compare with other MCP servers?
- safety score 97/100 (higher than 98% of 48,255 servers); uptime 96% (of our recent checks; the typical remote server answers 100%); response time 444 ms (faster than 33% of 30,031 servers). Full comparison.