@nodatachat/mcp 1.3.23 → 1.3.25

package/README.md

@@ -32,11 +32,14 @@ That's it — **no flags**. Self‑serve: registering opens an instant free **sa
 Run the line above with no credential. The server still connects (it never fails the MCP handshake) and exposes two setup tools:
 
 - **`nodata_get_started`** — call it first. It explains what you get and the single next step.
-- **`nodata_connect`** — register once, autoload forever:
-  1. `nodata_connect` (no args) → opens the free signup in your browser (work email + company, ~30s). Your **12‑word recovery phrase** is generated **in your browser — NoData never sees it**. The page shows your org key **once**.
-  2. `nodata_connect` with `api_key: "<that key>"` → saved to `~/.nodata/credentials.json` (chmod 600).
-  3. Restart, or run `/mcp` → every later start loads your identity with nothing to retype. *Registration ≠ login.*
+- **`nodata_connect`** — connect this computer once, autoload forever. Nothing to copy:
+  1. `nodata_connect` (no args) → a page opens in your browser. Sign in (or create a free account), check the code it shows, and click **Approve**. Signing in with a work address sends this computer to your organisation: it joins at once, or waits for your admin, as the organisation chose.
+  2. On approval this computer gets its own device key, saved to `~/.nodata/credentials.json` (chmod 600). No org key is copied anywhere.
+  3. Run `/mcp` → the organisation tools appear, and every later start loads them with nothing to retype.
 
+  From a terminal it is the same: `npx -y @nodatachat/mcp@latest connect`. Only if you must use an org key: `connect --key` (or `nodata_connect` with `step: "key"`) asks for it in a terminal, not shown on screen. Never paste a key into a chat.
+
+If you create an account, its page generates a **12‑word recovery phrase in your browser — NoData never sees it**.
 Keep the 12‑word phrase somewhere safe — it is the only way back into your org, and NoData cannot reissue it.
 
 ---
@@ -114,6 +117,7 @@ Any mode except agent mode, **no account needed**, entirely on your machine. Any
 |-----|------|--------------|
 | "scan this folder" | `nodata_scan_folder` | The **whole** result — counts by type, folder and file — plus a full content‑free HTML report in `~/.nodata/reports` (every finding, never a value). |
 | "what should I do with these?" | `nodata_plan` | A **recommended policy** per file after the scan: tier (Restricted / Confidential / Internal) and action (clean copy + lock, lock, clean copy, keep); credentials also get "rotate at the source". Nothing happens until you approve, and you can change any line first. Proposing is not accepting. |
+| "the scan got it wrong" | `nodata_scan_feedback` | Tell NoData what the scan flagged that is **not** sensitive, and what kinds it **missed**. Only kind labels and counts leave your machine ("ID×2 not sensitive · phone×1 missed") — never a value, a file name or free text — and you see the exact line sent. It changes no file. |
 | "lock what it found" | `nodata_protect` | Seals the files with findings to this device's key as `<file>.ndc` — the same v3 seal and format as `nodata protect`, so `nodata open` opens it too. Local receipt with hashes. |
 | "clean copy of this file" | `nodata_redact` | A copy with every detected value replaced by `[CARD]`, `[ID]`, `[IBAN]`, `[PHONE]`, `[EMAIL]`; a personal‑data column (CSV or Excel) is replaced with one stable token per person (`[NAME-1]` …) and amounts stay whole. Excel stays Excel. Same detectors as the scan. |
 | "open this .ndc" | `nodata_open` | Opens it back next to itself, hash‑checked. |