sealnet-mcp 0.9.0 → 0.10.0

package/README.md

@@ -25,7 +25,7 @@ When an MCP-connected AI agent (Claude Desktop, Cursor, Cline, etc.) creates a S
 | `seal_list()` | List SEALs created by **this MCP server only** (scope: `state.json`; never reveals user's CLI seals) |
 | `seal_revoke(handle)` | Revoke by opaque handle (model never learns raw `seal_id`) |
 
-With SEAL Pro workload credentials (`sealpro agent enroll`, or `SEALPRO_WORKLOAD_ID`, `SEALPRO_WORKLOAD_SEED` and `SEALPRO_BASE_URL`) three tools appear: `seal_pro_secret_use(secret, version?)` saves a secret your organisation granted to this agent to a 0600 file and returns its path, never the value; `seal_pro_secret_request(secret, reason, ttl_seconds?)` asks a person for one, for a while, and waits for the decision; `seal_pro_file_get(seal, file?, dir?)` saves the files of a room whose key a person granted this agent, 0600 and digest-checked, and returns their paths.
+With `sealfs` on PATH holding a SEAL Pro workload enrolled under this server's key (`sealfs enroll` with the same `SEAL_SEED`) four tools appear, `sealfs` doing the work: `seal_pro_secret_use(secret, version?)` saves a secret your organisation granted to this agent to a 0600 file and returns its path, never the value; `seal_pro_secret_request(secret, reason, ttl_seconds?)` asks a person for one, for a while, and waits for the decision; `seal_pro_file_get(seal, file?, dir?)` saves the files of a room whose key a person granted this agent, 0600 and digest-checked, and returns their paths; `seal_pro_run(command, secrets, cwd?, timeout?)` runs a program with granted secrets in its environment, every value replaced in the output that comes back.
 
 Large transfers report `notifications/progress` when the host sends a `progressToken`. Where the host supports URL-mode elicitation, `seal_request` and `seal_pair` show the page link through it and wait in one call; otherwise they return the link and a second call waits.