cryptbrew-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port the HTTP server listens on when running with start:http (default 3040), path /mcp | 3040 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cryptbrew_aboutC | Overview of Cryptbrew: business Bitcoin invoicing and tax-ready payment tracking for SMBs. |
| cryptbrew_pricingA | Cryptbrew invoicing fees only: payment fee (1% min 10 sats) and free iOS app. Not CryptBrew Lock — use cryptbrew_lock_info for Lock. |
| cryptbrew_linksA | Official Cryptbrew invoicing URLs: website, help, support, downloads, llms.txt, API, App Store, health. |
| cryptbrew_how_it_worksA | Explain how Cryptbrew invoicing, payment forwarding, and non-custody model work. |
| cryptbrew_lock_infoC | CryptBrew Lock only (separate Mac app): lock screen, Touch ID, failed-auth photo+email, Homebrew, $9.99. Not the invoicing 1% fee. |
| cryptbrew_faqA | Answer a Cryptbrew invoicing/product FAQ. For CryptBrew Lock-only questions prefer cryptbrew_lock_info. |
| cryptbrew_healthA | Fetch live Cryptbrew API health from /payments/health and /health. |
| cryptbrew_contactA | Cryptbrew support and contact channels: email, WhatsApp, setup visits, help pages. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools target a distinct informational topic, but cryptbrew_faq, cryptbrew_about, and cryptbrew_how_it_works overlap for general 'how does it work?' queries. The pricing vs. lock_info boundary is well handled, but the broad-faq catch-all remains a misselection risk.
All tools follow a predictable cryptbrew_<topic> snake_case pattern with no mixed conventions. Names are readable and consistently structured.
The set has 8 tools, which is well-scoped for a product-information server. Each major aspect has a dedicated tool without excessive granularity.
Covers pricing, links, mechanism, Lock app, FAQ, health, contact, and overview. Minor gaps exist for terms/legal details or deeper API reference beyond the links tool, but the core informational surface is solid.