vaultzero 0.1.4__tar.gz → 0.1.5__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {vaultzero-0.1.4 → vaultzero-0.1.5}/PKG-INFO +1 -1
- {vaultzero-0.1.4 → vaultzero-0.1.5}/pyproject.toml +1 -1
- {vaultzero-0.1.4 → vaultzero-0.1.5}/vaultzero/client/mcp_server.py +8 -14
- {vaultzero-0.1.4 → vaultzero-0.1.5}/.gitignore +0 -0
- {vaultzero-0.1.4 → vaultzero-0.1.5}/LICENSE +0 -0
- {vaultzero-0.1.4 → vaultzero-0.1.5}/README.md +0 -0
- {vaultzero-0.1.4 → vaultzero-0.1.5}/tests/__init__.py +0 -0
- {vaultzero-0.1.4 → vaultzero-0.1.5}/tests/unit/__init__.py +0 -0
- {vaultzero-0.1.4 → vaultzero-0.1.5}/tests/unit/golden_vectors.json +0 -0
- {vaultzero-0.1.4 → vaultzero-0.1.5}/tests/unit/test_crypto.py +0 -0
- {vaultzero-0.1.4 → vaultzero-0.1.5}/tests/unit/test_sdk_and_mcp.py +0 -0
- {vaultzero-0.1.4 → vaultzero-0.1.5}/vaultzero/__init__.py +0 -0
- {vaultzero-0.1.4 → vaultzero-0.1.5}/vaultzero/client/__init__.py +0 -0
- {vaultzero-0.1.4 → vaultzero-0.1.5}/vaultzero/client/_net.py +0 -0
- {vaultzero-0.1.4 → vaultzero-0.1.5}/vaultzero/client/crypto.py +0 -0
- {vaultzero-0.1.4 → vaultzero-0.1.5}/vaultzero/client/embeddings.py +0 -0
- {vaultzero-0.1.4 → vaultzero-0.1.5}/vaultzero/client/sdk.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: vaultzero
|
|
3
|
-
Version: 0.1.
|
|
3
|
+
Version: 0.1.5
|
|
4
4
|
Summary: MCP server for a privacy-first agent memory vault: memories are encrypted on the client before they reach the server.
|
|
5
5
|
Project-URL: Homepage, https://vaultzero.cc
|
|
6
6
|
Project-URL: Documentation, https://github.com/xo0ps/VaultZero-Client#readme
|
|
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
|
|
|
4
4
|
|
|
5
5
|
[project]
|
|
6
6
|
name = "vaultzero"
|
|
7
|
-
version = "0.1.
|
|
7
|
+
version = "0.1.5"
|
|
8
8
|
# This string is what MCP directories show next to the listing, so it names the thing a
|
|
9
9
|
# prospective user is looking for (an MCP server) before the architecture behind it.
|
|
10
10
|
description = "MCP server for a privacy-first agent memory vault: memories are encrypted on the client before they reach the server."
|
|
@@ -78,8 +78,8 @@ def create_mcp_server(
|
|
|
78
78
|
),
|
|
79
79
|
)
|
|
80
80
|
async def remember_fact(fact_text: str, scope: str, retention: str = default_retention) -> str:
|
|
81
|
-
"""Store one durable fact in encrypted long-term memory,
|
|
82
|
-
recall_context
|
|
81
|
+
"""Store one durable fact in encrypted long-term memory, readable later by
|
|
82
|
+
recall_context.
|
|
83
83
|
|
|
84
84
|
Use this when the user states something worth keeping across sessions: a
|
|
85
85
|
preference, a decision, an identifier, a recurring constraint. Do NOT use it for
|
|
@@ -87,9 +87,8 @@ def create_mcp_server(
|
|
|
87
87
|
restate something already stored — storing the same fact twice creates two
|
|
88
88
|
memories that both surface on recall.
|
|
89
89
|
|
|
90
|
-
|
|
91
|
-
|
|
92
|
-
different machine or a hosted instance.
|
|
90
|
+
The write is only reversible by a client holding the same key store, so the fact
|
|
91
|
+
cannot be read back from another machine or a hosted instance.
|
|
93
92
|
|
|
94
93
|
Args:
|
|
95
94
|
fact_text: The fact to persist, as a self-contained sentence. Write it so it
|
|
@@ -139,21 +138,16 @@ def create_mcp_server(
|
|
|
139
138
|
)
|
|
140
139
|
async def recall_context(query: str, scopes: list[str], limit: int = 5) -> str:
|
|
141
140
|
"""Retrieve facts previously written by remember_fact, ranked by similarity to
|
|
142
|
-
the query
|
|
141
|
+
the query and decrypted for this call.
|
|
143
142
|
|
|
144
143
|
Use this before answering a question that may depend on something the user told
|
|
145
144
|
you earlier — preferences, past decisions, standing constraints. Do NOT use it to
|
|
146
145
|
browse or audit everything stored: it ranks by relevance to one query and returns
|
|
147
146
|
at most `limit` items, so it is a lookup, not a listing.
|
|
148
147
|
|
|
149
|
-
|
|
150
|
-
|
|
151
|
-
|
|
152
|
-
Requires the key store that wrote the memories. If a matching key is not present,
|
|
153
|
-
the call returns "decryption key not found in the trusted key store" — that is
|
|
154
|
-
expected on a different machine, a hosted instance, or a fresh process without
|
|
155
|
-
VZ_KEY_STORE_PATH, and the memories are unreadable there by design rather than by
|
|
156
|
-
failure.
|
|
148
|
+
An empty result is a successful answer, not an error. Without the key store that
|
|
149
|
+
wrote the memories this returns "decryption key not found" — expected on another
|
|
150
|
+
machine or a hosted instance.
|
|
157
151
|
|
|
158
152
|
Args:
|
|
159
153
|
query: Natural-language description of what you are looking for. It is matched
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|