@saihm/mcp-server-pro 0.1.0 → 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +16 -0
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -82,6 +82,22 @@ Non-2xx responses throw `SaihmEndpointError` with `status` and a typed `code` (e
82
82
  | Authenticated sharing | Grantee public keys are pinned out-of-band and verified before any secret is bound to them. |
83
83
  | Erasure | Destroying the endpoint-side wrapped DEK crypto-shreds the cell. |
84
84
 
85
+ ## Where sealed cells are stored
86
+
87
+ This client seals cells and hands the ciphertext to whatever operator endpoint
88
+ you point `SAIHM_ENDPOINT_URL` at; **that operator chooses and configures the
89
+ durable storage backend** — typically a local IPFS / Kubo node first, then a
90
+ Filecoin deep-archive provider (e.g. Pinata, Synapse, or Lighthouse). Storage
91
+ is operator-configured **by design**: the protocol never locks anyone to a
92
+ single provider. If you run your own endpoint, provisioning that backend is
93
+ your responsibility — see your operator deployment guide.
94
+
95
+ Prefer not to run storage at all? **Join SAIHM** at <https://saihm.coti.global>
96
+ and use the hosted **non-custodial** operator, which provides durable storage
97
+ for you. Because this client seals every cell locally, the hosted operator
98
+ only ever stores **ciphertext** and never holds your keys — managed storage
99
+ without giving up custody (a paid hosted service).
100
+
85
101
  ## License
86
102
 
87
103
  Apache-2.0 © SAIHM
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@saihm/mcp-server-pro",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "description": "SAIHM production thin-client. Seals client-side via @saihm/client-pro (ML-DSA-65 identity, per-cell AES-256-GCM DEK wrapped under a client KEK, ML-KEM-768 authenticated sharing) and POSTs opaque ciphertext to the blind, non-custodial SAIHM /mcp endpoint. The master secret, KEK, and plaintext never leave this process. Apache-2.0.",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",