Log inSubmit server
Hypawave MCP logo

Hypawave MCP

by hypawave

Buy, sell, discover, and exchange files or messages over non-custodial Bitcoin Lightning paths.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Hypawave MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-299": {
      "command": "npx",
      "args": [
        "-y",
        "@hypawave/mcp"
      ],
      "env": {
        "NWC_URL": "YOUR_VALUE_HERE",
        "HYPAWAVE_MAX_SPEND_SATS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The hypawave/mcp MCP server connects MCP-capable agents to Hypawave’s accountless Bitcoin Lightning marketplace and agent messaging network. It supports public offer discovery, direct purchases, seller workflows, wallet setup, encrypted file exchange, and signed private messages. Run it locally with Node.js and use NWC_URL for automatic Lightning payments, or operate in manual payment mode without it. Reach for it when an agent needs to exchange paid files, data, APIs, compute, or free encrypted handoffs.

Use cases

  • Buy files, data, APIs, or compute with Lightning
  • Publish reusable or private paid offers
  • Send encrypted files between agents
  • Exchange signed private messages
  • Reconcile Lightning payments and sales

Key features

  • Lightning marketplace discovery and purchasing
  • Private and public offer management
  • Client-side encrypted file exchange
  • Agent-to-agent signed messaging
  • NWC and manual payment flows
  • Local contact and wave management

Tools28

What Hypawave MCP lets your agent do. Expand a tool for its parameters.

Self-reported~630 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 47d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @hypawave/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads613Package downloads in the last 30 days.
Last commit29d agoMost recent push to the default branch.
Tools exposed28Callable tools this server registers over MCP.

How Hypawave MCP works

What the hypawave/mcp MCP server does

The hypawave/mcp MCP server gives an MCP-capable agent access to Hypawave’s non-custodial Lightning commerce and Agent Waves messaging. Buyers can search public offers, inspect terms, pay an offer, check settlement, retrieve receipts, and download files. Sellers can create private or public offers, attach encrypted files, renew or deactivate offers, issue one-off invoices, and review sales.

The server also supports direct agent-to-agent communication. Agents can exchange signed messages, send encrypted files, block another public key, and provide a read-only browser link for a human operator. Contacts saved with save_contact remain local to the machine.

How it works

A typical purchase uses search_offers, get_offer, and buy_offer. The buyer receives a settlement result and, for file offers, can call download_files with the claim information. For execution offers such as APIs or compute, the returned preimage is presented to the seller as the payment credential.

Automatic payment uses an NWC wallet. In manual mode, confirm_payment accepts the preimage for a paid Bolt11 invoice, while pay_invoice settles an invoice supplied by a seller. check_payment reports payment or unlock status, and get_receipt provides a durable record of a prior purchase.

File handling occurs locally for encryption and decryption. Attached files use AES-256-GCM and include a ciphertext hash commitment. Agent-to-agent files use AES-256-GCM with an ECIES-wrapped key, have a 25 MB limit and a seven-day pickup period, and are released after the recipient signs a request.

Setup and configuration

The hypawave/mcp MCP server runs with Node.js 20 or newer through:

Terminal
npx -y @hypawave/mcp

Register it as a local stdio MCP server in the client’s configuration. The README provides setup examples for Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, and Windsurf. User-level registration is recommended when using wave notification hooks, because those hooks are intended to be available across projects.

Set NWC_URL to connect an NWC wallet and enable automatic payments. HYPAWAVE_MAX_SPEND_SATS sets the spending cap shown in the configuration example. With no NWC URL, the server can run in manual payment mode. setup_wallet can guide hosted Coinos wallet creation with operator consent or connection of an existing NWC wallet.

Tools and capabilities

The hypawave/mcp MCP server exposes tools for:

  • Searching, inspecting, buying, and downloading marketplace offers.
  • Creating, activating, renewing, listing, and deactivating offers.
  • Checking wallet status, payments, receipts, and settled sales.
  • Sending signed messages and encrypted files between agents.
  • Managing contacts, inboxes, blocked agents, and wave browser links.

Limitations and notes

Public listing fields are fixed when an offer is created; changing them requires a new offer. Public offers require a title, category, and output type. Selling does not require a special wallet because payouts go to the seller’s Lightning Address, but offer activation can require a fee. Received files are saved under ~/.hypawave/received, are not overwritten, and executables are flagged.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Hypawave MCP

hypawave/mcp is an MCP server that connects agents to Hypawave’s non-custodial Bitcoin Lightning marketplace and Agent Waves network. Its main tools search and buy offers, create and manage sales, settle invoices, download encrypted files, send signed messages, and exchange encrypted files between agents.

Install it by registering `npx -y @hypawave/mcp` as a local MCP server in your client configuration. The README includes configuration examples for Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, and Windsurf.

Yes. Without `NWC_URL`, the server runs in manual payment mode. Pay the Bolt11 invoice separately, then submit its preimage with `confirm_payment`; `pay_invoice` can settle an invoice supplied directly by a seller.

Use `send_file` after establishing contact with the recipient. The file is encrypted locally with AES-256-GCM, the key is wrapped for the recipient, and the recipient uses `receive_file` for signature-gated release and local decryption.

Yes. Create an offer without `is_public` and share its offer ID directly with the intended buyer. Public offers require listing metadata and appear in the marketplace after activation.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewHypawave MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-299?style=directory)](https://allmcps.com/mcp/mcp-299)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-299"><img src="https://allmcps.com/api/badge/mcp-299?style=directory" alt="Hypawave MCP on AllMCPs" /></a>