sealnet-mcp 0.7.0 → 0.8.0

package/README.md

@@ -16,7 +16,7 @@ When an MCP-connected AI agent (Claude Desktop, Cursor, Cline, etc.) creates a S
 
 | Tool | Purpose |
 |------|---------|
-| `seal_share(path, mode='inbox'\|'handoff'\|'forward', expire?, max_reads?, tier?)` / `seal_share(payment)` | Create a SEAL from a local file or folder (sent as one ZIP), streamed from disk. Default: inbox once connected, else handoff; without `expire`, 1d in the inbox, 5m for a handoff, or 1d for one over 100 MB. Over 1 GB the user pays once by card (smallest tier that fits, or `tier`): the payment page goes through URL-mode elicitation, or comes back as `payment_url` and a second call with `payment` finishes the upload into the same seal |
+| `seal_share(path, mode='inbox'\|'handoff'\|'forward', expire?, max_reads?, tier?)` / `seal_share(payment)` | Create a SEAL from a local file or folder (sent as one ZIP), streamed from disk. Default: inbox once connected, else handoff; without `expire`, 1d in the inbox, 5m for a handoff, or 1d for one over 100 MB. Above the free limit the user pays once by card (smallest tier that fits, or `tier`): the payment page goes through URL-mode elicitation, or comes back as `payment_url` and a second call with `payment` finishes the upload into the same seal |
 | `seal_request(what, kind='any'\|'secret'\|'file', where_url?, wait=true, from?)` / `seal_request(request)` | Ask the user for a file or a secret without it passing through the chat. On the user's computer the `seal` CLI draws the system dialog (`seal request --local --json`); otherwise the user answers at `seal.net/i/<id>`, sealed to this server's key, shown with three words of that key; once connected the request also waits in the user's inbox (`from=owner`, or `from=anyone` for a plain link). Returns the path of a 0600 file, never the value |
 | `seal_pair(name?, wait=true)` | Connect this agent to the user's SEAL inbox, once: the user opens a page, compares three words and connects; the chat then shows the inbox's three words. After it `seal_share` sends to the inbox by default |
 | `seal_open(url\|item, mode='metadata'\|'file'\|'inline', dir?)` | Read metadata (default — no download, no counter consumption), save to disk (`file`: streamed, verified before it gets its name, 0600, returns paths) or inline parse (whitelisted MIMEs only, ≤100 KB, refuses secrets, HTML and binary). `item` is an inbox handle instead of a link |
@@ -44,7 +44,7 @@ The first start makes the key (keychain, else the file); there is no setup step.
 - `handles[]` — opaque handle → `{ seal_id, owner_token, mode, created_at }`. Each `owner_token` is full owner-capability for that seal; encrypting only `identity` and leaving tokens plain would be a security illusion.
 - `audit[]` — historical tool invocations (timestamps, handles, modes). Side-channel relevant.
 
-Several MCP hosts on one machine (Claude Desktop, Claude Code, Cursor) share the key and the state: each write re-reads the file under a lock. `serve --ephemeral` (or `SEAL_MCP_EPHEMERAL=1`) keeps nothing on disk and makes a new key each start; handles then last until restart, and seal expiry does not depend on it. A state from version 0.2 moves under the key on the first start, once.
+Several MCP hosts on one machine (Claude Desktop, Claude Code, Cursor) share the key and the state: each write re-reads the file under a lock. `serve --ephemeral` (or `SEAL_MCP_EPHEMERAL=1`) keeps nothing on disk and makes a new key each start; handles then last until restart, and seal expiry does not depend on it.
 
 ## Install + configure
 
@@ -84,7 +84,6 @@ Environment variables consumed by the CLI:
 | `SEAL_OWNER` | `serve` | The address of the user's inbox, instead of `seal_pair`: for a cloud session with nowhere to open the page |
 | `SEAL_MCP_EPHEMERAL=1` | `serve` | As `--ephemeral`: a new key each start, nothing on disk |
 | `SEAL_MCP_CONFIG_DIR` | every subcommand | Override default state directory (mirrors Rust `seal-cli`'s `SEAL_CONFIG_DIR`) |
-| `SEAL_MCP_PASSPHRASE` | `serve` | Read once, to move a state of version 0.2 |
 | `SEAL_MCP_BACKEND_URL` | `serve`, `doctor` | SEAL backend base URL (default `https://api.seal.net`) |
 | `SEAL_MCP_PUBLIC_HOST` | `serve`, `doctor` | Public origin for minted share URLs (default `https://seal.net`) |
 | `SEAL_MCP_DEBUG=1` | all | Include stack traces in fatal-error output (otherwise plain `error: <msg>`) |
@@ -110,6 +109,5 @@ pnpm test
 
 ## Source of truth
 
-- `docs/security/seal_phase1_plan.md` §"Phase 3 — MCP-оболочка"
 - `shared/contracts/seal_mcp.v1.json` (tool input/output schemas)
 - All cryptographic primitives are bundled into `dist/` from internal workspace packages — no algorithm code is duplicated and no external `@`-scoped dependencies are pulled at install time.