
ai-ecoverse/slicc-vault
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
The separate-origin vault at vault.sliccy.ai: sealed secrets, OAuth tokens, and model/MCP credentials for SLICC seven, used only by its injector
概要
The separate-origin vault at vault.sliccy.ai. It holds the sealed secrets, OAuth tokens, and model and MCP credentials of SLICC seven, so that no value ever reaches the model provider. The design is secrets-tokens-design.md (revision 4) in slicc-agent-plan. This README is the spec of what is built. - the key store, records, origin namespacing, auto-unlock with an optional passkey or passphrase lock, the embedding API with its page and agent roles, the page's put, seal, remove, restore, cancel and lock, the scrub state, the lock button and its popup, the attested policy (rules, [exec], [exits], [limits]), the injector and forward with the response scrub (S1), the agent's redact, redactStream, endpoints, model and mcp (S3, S4), records, grant and refresh, the model and MCP refusal, exec tickets (materialize and materializeConsume), import (backups, KeePass, six's secrets.
README
以下は原文 README の抜粋です。原文を見る。
slicc-vault
The separate-origin vault at vault.sliccy.ai. It holds the sealed secrets, OAuth tokens, and model and MCP credentials of SLICC seven, so that no value ever reaches the model provider. The design is secrets-tokens-design.md (revision 4) in slicc-agent-plan. This README is the spec of what is built.
- Built: the key store, records, origin namespacing, auto-unlock with an optional passkey or passphrase lock, the embedding API with its
pageandagentroles, the page’sput,seal,remove,restore,forgetLease,cancelandlock, the scrub state, the lock button and its popup, the attested policy (rules,[exec],[exits],[limits]), the injector andforwardwith the response scrub (S1), the agent’sredact,redactStream,endpoints,modelandmcp(S3, S4),records,grantandrefresh, the model and MCP refusal, exec tickets (materializeandmaterializeConsume),sessionMaterializefor kernel-verified TLS sessions,import(backups, KeePass, six’ssecrets.env) andexport, sign-in tokens with their grants and refresh throughegress, and the vault side of the/dev/sealedopsseal,placeholder,list,test,request,status,cancelandmaterialize. - The vault has no network stack. It never fetches anything but its own
config.jsonandembedders.json: bios sends every request the vault prepares.
Documents and hosting
The build (npm run build) writes a flat static tree to dist/site/:
| file | what it is |
|---|---|
index.html, frame.js |
the core frame. bios embeds it as a hidden iframe and talks to it over a MessagePort |
button.html, button.js |
the lock button. A popup can only open from a click inside a vault document, so bios and spectrum embed this wherever the lock is offered |
popup.html, popup.js |
the vault window, a top-level vault.sliccy.ai document, used only for the passkey or passphrase lock |
vault.css, fonts/ |
Spectrum 2 from the CSS-only @spectrum-css packages, and Adobe Clean |
config.json |
{ version, embedders }. embedders is vault.sliccy.ai’s fallback list, ["https://seven.sliccy.ai"] |
The bundles hold this repo’s code, @ai-ecoverse/slicc-scrub, and @ai-ecoverse/jerk-oauth (exact-pinned, for token refresh): its wasm is inlined into a separate chunk under chunks/ (about 970 KB) that loads only on the first refresh or MCP grant, never fetched. The only third-party code is for KeePass imports: kdbxweb (with @xmldom/xmldom and fflate) and hash-wasm’s argon2, exact-pinned and bundled into a separate chunk under chunks/ that the core frame loads only when a KeePass import starts; its wasm is inlined, never fetched. The sliccy-ai Worker serves the tree from the network on every load, never from OPFS, with:
Content-Security-Policywithscript-src 'self', no inline scripts or styles, andframe-ancestorslisting the seven origins;
インストール
This server does not publish a one-line install command.
Open the repository installation guide MCP 初心者?mcpskill.org のガイドから始めましょう →