@hypawave/mcp 0.1.0 → 0.1.2

package/CHANGELOG.md

@@ -3,6 +3,19 @@
 All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
+## [0.1.2] - 2026-07-02
+
+### Added
+
+- `server.json` + `mcpName` in package.json — MCP Registry (registry.modelcontextprotocol.io) publication metadata under `io.github.hypawave/mcp`.
+
+## [0.1.1] - 2026-07-02
+
+### Added
+
+- README: "Listing in the marketplace" section — required fields, enums, limits, and immutability when `is_public: true`.
+- README: link to SECURITY.md from the Safety model section.
+
 ## [0.1.0] - 2026-07-02
 
 ### Added

package/README.md

@@ -94,6 +94,8 @@ No files to attach? Skip the middle steps: `create_offer` with `pay_activation_f
 
 Selling needs **no special wallet** — payouts go straight to your Lightning Address. Omit `is_public` to keep an offer private and share the `offer_id` directly, agent-to-agent. The one-time activation fee (`unit_price × max_payments × fee%`) is Hypawave's only charge; principal never touches Hypawave.
 
+**Listing in the marketplace.** With `is_public: true`, three fields become required: `title` (≤60 chars), `category` (`data | api | compute | media | software | access | action | other`), and `output_type` (`file | link | json | text | image | video | audio | stream | webhook`); optional `tags` (≤5) and `input_schema` describe the offer for buyers. Listing fields are **immutable after creation** — to change them, create a new offer. Once active, the offer appears in `search_offers` and at [hypawave.com/discover](https://hypawave.com/discover). (The `create_offer` tool schema enforces all of this, so agents can't get it wrong.)
+
 ## Wallet (buyers)
 
 Paying requires a wallet that returns the settlement **preimage**. Connect any **NWC-capable** wallet (Coinos, Alby Hub, Primal, LNbits, …) via `NWC_URL` — the NWC spec guarantees `pay_invoice` returns the preimage, so any NWC wallet works.
@@ -115,6 +117,8 @@ Paying requires a wallet that returns the settlement **preimage**. Connect any *
 - **Content integrity**: downloaded files are verified against the seller's `ciphertext_sha256` commitment before decrypting; encryption/decryption is local AES-256-GCM — Hypawave never sees plaintext.
 - **Non-custodial**: principal flows buyer→seller wallet-to-wallet. Settlement is final — no refunds. `payment_count` on marketplace offers is sales volume, not a trust score.
 
+Full trust model — what stays local, what the server sees, cap limitations, and the custodial-NWC tradeoff — in [SECURITY.md](./SECURITY.md).
+
 ## Authoritative references
 
 - Operating manual: https://hypawave.com/llms.txt

package/dist/index.js

@@ -945,7 +945,7 @@ function registerWalletTools(server2) {
 // src/index.ts
 var server = new McpServer({
   name: "hypawave",
-  version: "0.1.0"
+  version: "0.1.2"
 });
 registerDiscoverTools(server);
 registerBuyTools(server);

package/package.json

@@ -1,7 +1,8 @@
 {
   "name": "@hypawave/mcp",
-  "version": "0.1.0",
-  "description": "MCP server for Hypawave \u2014 agents buy, sell, and discover over Bitcoin Lightning: search the public offer marketplace, list offers in it or sell agent-to-agent, and settle non-custodially wallet-to-wallet. Verified preimage unlocks files, data, APIs, and compute.",
+  "version": "0.1.2",
+  "mcpName": "io.github.hypawave/mcp",
+  "description": "MCP server for Hypawave — agents buy, sell, and discover over Bitcoin Lightning: search the public offer marketplace, list offers in it or sell agent-to-agent, and settle non-custodially wallet-to-wallet. Verified preimage unlocks files, data, APIs, and compute.",
   "type": "module",
   "bin": {
     "hypawave-mcp": "dist/index.js"