Skip to content
mcp/harbor

SEAL changelog

net.seal/mcp

9 changes recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.

  • server.json 1 field changed
    version
    0.11.2 0.12.0

  • llms.txt +1 −1

    https://seal.net/llms.txt 

    − - Search: `sealfs search "<query>" [--index <seal>]` reads an index snapshot of a seal you hold into memory and ranks it with `seal-indexer`, results only from your own seals; `sealfs events --after <seq>` lists what changed in the seals the key holds. The reference indexer is a workload of the organisation, its image built from released files: https://seal.net/releases/download/seal-indexer-v0.1.3/README.md+ - Search: `sealfs search "<query>" [--index <seal>]` reads an index snapshot of a seal you hold into memory and ranks it with `seal-indexer`, results only from your own seals; `sealfs events --after <seq>` lists what changed in the seals the key holds. The reference indexer is a workload of the organisation, its image built from released files: https://seal.net/releases/download/seal-indexer-v0.1.4/README.md

  • server.json 1 field changed
    version
    0.11.1 0.11.2
  • server.json 1 field changed
    version
    0.10.0 0.11.1

  • llms.txt +3 −1

    https://seal.net/llms.txt 

    − - Exit codes: 0 done, 2 input or not found, 3 version conflict, 4 no right (403, the plan's 402, the day's growth ceiling), 5 held (`hold_id`), 6 network or server, 7 key or login, 10 client outdated+ - Search: `sealfs search "<query>" [--index <seal>]` reads an index snapshot of a seal you hold into memory and ranks it with `seal-indexer`, results only from your own seals; `sealfs events --after <seq>` lists what changed in the seals the key holds. The reference indexer is a workload of the organisation, its image built from released files: https://seal.net/releases/download/seal-indexer-v0.1.3/README.md+ - Contracts: the agent signs by itself. `sealfs sign ls [--pending]` lists the contracts it may sign, each by its file; `sealfs sign show <id>`; `sealfs sign sign <id>` reads the version the contract names, checks its plaintext against the contract's hash and only then signs with the agent's own key. A person makes one on their own computer: `sealfs sign request <file> --signer <email|address>… [--quorum N] [--sequential]`+ - Exit codes: 0 done, 2 input or not found, 3 version conflict, 4 no right (403, the plan's 402, the day's growth ceiling), 5 held (`hold_id`), 6 network or server, 7 key or login, 8 the document is not the contract's (nothing signed), 9 not your turn yet in a contract signed in turn, 10 client outdated

  • llms.txt +10 −1

    https://seal.net/llms.txt 

    − - [MCP server](https://seal.net/docs/mcp): `npx -y sealnet-mcp`, no setup+ - [MCP server](https://seal.net/docs/mcp): `npx -y sealnet-mcp@latest`, no setup+ ## SEAL Pro agents: sealfs+ An agent of a SEAL Pro organisation is `sealfs`: one binary, one `SEAL_SEED`, the keys in its own process. Every command takes `--json`: one object on stdout, or `{"error":{"code","message"}}`.+ - Where: an agent in a container runs `sealfs` without a mount; on a workstation, `sealfs mount` puts the organisation's drive at `/Volumes/SEAL`, `~/seal` or `S:` (`sealfs unmount`, `sealfs install-service` to mount it at login); a person signs a computer in as themselves with `sealfs login`+ - Enroll: `sealfs enroll --workload <id> --token <token>`; or `sealfs enroll --request` prints the address a person creates the agent with, then `sealfs enroll --workload <id>`+ - Files of the seals granted to it, paths `<org>/<room>/<seal>/<path in the seal>`: `sealfs ls [--versions]`, `sealfs cat <file> [--range A-B] [-o <path>]`, `sealfs put <local> <file> [--auto | --base <file_id>] [--keep-both]`, `sealfs rm`, `sealfs restore <file_id>`, `sealfs mv`, `sealfs mkdir`, `sealfs lease`+ - Secrets: `sealfs run --secret NAME=<id|/path>[@version] -- <program>` (the values only in its environment, masked in its output), `sealfs secrets ls`, `sealfs request <id|/path> --reason "…" --wait`, `sealfs secret materialize <id|/path>` (a 0600 file, only its path printed); a value is never printed+ - `sealfs status`, `sealfs doctor [--transcripts <dir>]`, `sealfs cache clear`, `sealfs self-update`+ - Exit codes: 0 done, 2 input or not found, 3 version conflict, 4 no right (403, the plan's 402, the day's growth ceiling), 5 held (`hold_id`), 6 network or server, 7 key or login, 10 client outdated+ - MCP: with `sealfs` on PATH enrolled under the server's `SEAL_SEED`, sealnet-mcp offers `seal_pro_secret_use`, `seal_pro_secret_request`, `seal_pro_file_get` and `seal_pro_run`

  • server.json 1 field changed
    version
    0.9.0 0.10.0

  • server.json 1 field changed
    version
    0.8.0 0.9.0

  • server.json 1 field changed
    version
    0.7.0 0.8.0
SEAL MCP server