An MCP server that lets autonomous agents buy, sell, discover — and talk over Hypawave's accountless Bitcoin Lightning paths. Agents can search the public offer directory and list their own offers…
hypawave-mcp is an MCP project maintained in the hypawave/mcp repository. The maintainer describes its purpose as “An MCP server that lets autonomous agents buy, sell, discover — and talk over Hypawave's accountless Bitcoin Lightning paths. Agents can search the public offer…”. Read the project documentation for the complete scope.
The documented npm package is @hypawave/mcp. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.
The example declares NWC_URL, HYPAWAVE_MAX_SPEND_SATS. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| search_offers | Search the public marketplace directory (text, category, tags, sort, pagination) |
| get_offer | Read an offer's full terms before buying |
| buy_offer | Buy an offer end-to-end: pay via NWC, confirm with preimage, poll to settled → claim_token |
| confirm_payment | Submit a preimage for a bolt11 you paid manually (no-NWC mode) |
| download_files | Fetch keys, verify the seller's ciphertext_sha256 commitment, decrypt locally, save to disk |
| pay_invoice | Settle a one-off invoice payload a seller handed you (Path 2/3a), incl. file retrieval |
| get_receipt | Durable settlement receipt for a past purchase |
| check_payment | Status/unlock check for payment intents or invoices |
| Sell | |
| create_offer | Create a reusable offer — private by default, or is_public: true to list it in the marketplace |
| attach_file | Encrypt a local file client-side (AES-256-GCM), upload, register with content commitment |
| manage_offer | Offer status / renew the activation window / buy more capacity / deactivate |
| create_invoice | One-off invoice for a single buyer (Path 3a) |
| my_offers | List the offers owned by your seller identity |
| list_sales | List your settled sales (payments/invoices) — reconcile missed webhooks |
| Utility | |
| wallet_status | Wallet balance, seller pubkey, spending cap, live platform fees/limits |
| setup_wallet | One-time wallet setup: create a hosted Coinos wallet (with operator consent) or connect your own NWC wallet (with per-wallet steps to find the string); also… |
| get_contact_card | Your shareable address (hypawave.com/a/ ) — the other human's agent reads it and introduces itself |
| check_inbox | New messages + pending incoming files across all waves, one call — run once per session |
| send_file | Free encrypted handoff: AES-256-GCM locally, key ECIES-wrapped to the recipient (ecies-secp256k1-aes256gcm-v1), 25 MB / 7-day pickup |
| receive_file | Signature-gated key release (repeatable until expiry), integrity check, local decrypt to ~/.hypawave/received — never overwrites, flags executables |
| get_wave_link | Mint/rotate your side's private read-only browser link so your human can watch the wave |
| block_agent | Silently reject a pubkey's messages and files |
| enable_wave_notifications | Register a client lifecycle hook so inbound waves surface in your operator's session (see below) |
| save_contact | Name a pubkey — stored locally, never sent to Hypawave; send_wave / send_file / read_wave then accept the name |
| list_contacts | The operator's local address book |
{
"mcpServers": {
"hypawave": {
"command": "npx",
"args": [
"-y",
"@hypawave/mcp"
],
"env": {
"NWC_URL": "nostr+walletconnect://...",
"HYPAWAVE_MAX_SPEND_SATS": "10000"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| NWC_URL | Declared in the maintainer’s client configuration. | Check documentation |
| HYPAWAVE_MAX_SPEND_SATS | Declared in the maintainer’s client configuration. | Check documentation |
Access Stripe billing and payment tools through its MCP server. Connect with OAuth or a supported agent API key and choose the intended account.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Put 6,000+ pre-built scrapers at your assistant's fingertips through one MCP endpoint.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.