wontopos-mcp 1.0.17 → 1.0.18

package/README.md

@@ -58,7 +58,7 @@ Create a key in the [console](https://wontopos.com). Optional env:
 | `WONTOPOS_MODEL` | The engine. Default `tablet-2` — same token price as `tablet-1` and the one that can serve photos and re-ask. Also `tablet-1`, `scroll-1`, `scroll-1.2`. |
 | `WONTOPOS_VERIFY` | Default re-ask passes for `search`, 0-3. Default `0`. Each pass is another engine call, billed for what it delivers; the agent can raise it per call. |
 | `WONTOPOS_MAX_IMAGES` | Default photo results per `search`, 0-5. Default `0` — see below. |
-| `WONTOPOS_BASE_URL` | Self-hosted deployments only. |
+| `WONTOPOS_BASE_URL` | A different API host. Leave unset for the default. |
 | `WONTOPOS_READ_ONLY` | `1` / `true` / `yes` / `on` / `y` / `t` = read tools only, see Security. A value that is none of those (and none of `0` / `false` / `no` / `off`) stops the server rather than being read as off. |
 | `WONTOPOS_ALLOW_STORE_OVERRIDE` | `1` (same spellings) = multi-store; default = pinned, see Security. |
 
@@ -279,7 +279,7 @@ automatic retries, redirect refusal, response caps, and key hygiene apply as-is.
   used the trimmed value, so `create_store` made `alice` while every read and write
   went to `" alice \n"` — a different collection — and the console still printed
   `store "alice" verified`. And an oversized result was capped by slicing the
-  serialized JSON, handing the model a fragment with no closing bracket and a final
+  serialized JSON, handing the model truncated JSON with no closing bracket and a final
   memory cut mid-sentence (measured: 131,041 bytes of unparseable text from a 764 KB
   search). Now whole entries are dropped instead, the reply stays valid JSON, and
   what was dropped is stated in the payload — a truncation nobody can see is worse

package/index.mjs

@@ -19,7 +19,7 @@
 //   WONTOPOS_MAX_IMAGES default photo results per search, 0-5 (default 0). Zero
 //                       because this server answers a MODEL: an image memory it
 //                       cannot look at is a row of context that buys nothing.
-//   WONTOPOS_BASE_URL   self-hosted deployments only
+//   WONTOPOS_BASE_URL   a different API host; unset for the default
 //   WONTOPOS_READ_ONLY  "1" = read tools only (recall/search/list_memories/engram/
 //                       stats/revisions); no tool can write, update, or delete. For
 //                       agents that should consult memory, not own it.
@@ -135,7 +135,7 @@ const DATE_ONLY_RE = /^\d{4}-\d{2}-\d{2}$/;
  *  A bare "2026-03-14" is the form a model naturally emits. The current API accepts
  *  it, so this is not the only thing standing between an agent and a working call —
  *  it stays for the two things it still does: it rejects a non-date locally with a
- *  message saying what to send, and it works against an older or self-hosted backend
+ *  message saying what to send, and it works against an older or unfamiliar backend
  *  that takes only the full form.
  *  Returns null when the value is not a date at all, so the caller can refuse it.  */
 function normalizeEventDate(raw) {
@@ -519,7 +519,7 @@ function modelCaps() {
         // `null` = the catalogue answered but said nothing usable about this model —
         // either it did not name it, or it named it and declared no `capabilities`.
         // Both are "we do not know", and both must read the same way. That is not
-        // the same as "cannot": a self-hosted deployment lists whatever it runs, and
+        // the same as "cannot": a backend we do not know lists whatever it runs, and
         // this server must not invent a refusal on its behalf. See how it is read
         // below. This one IS cached — it is an answer, not a missing answer.
         return c ? { images: c.images === true, reAsk: c.re_ask === true } : null;
@@ -679,7 +679,7 @@ registerTool(
     //                          drop would bill for a search the agent believes it
     //                          shaped; the service refuses it anyway, one round trip
     //                          later and with less to say about which install it is.
-    //   unknown (self-hosted, or the catalogue is unreachable) → send nothing by
+    //   unknown (an unfamiliar host, or the catalogue is unreachable) → send nothing by
     //                          default, forward an explicit ask and let the service
     //                          answer. Refusing locally on a guess would deny a
     //                          capability the deployment may well have.
@@ -687,7 +687,7 @@ registerTool(
     // `?? DEFAULT` collapses "the agent asked for this" and "nobody said anything"
     // into one value, and the unknown-engine branch below needs to tell them apart:
     // forwarding an ASK lets the service decide, while forwarding a DEFAULT would put
-    // a field on every search that a self-hosted engine may refuse — every search,
+    // a field on every search that an older engine may refuse — every search,
     // including the ones that never mentioned photos.
     const askedVerify = verify != null;
     const wantVerify = askedVerify ? verify : DEFAULT_VERIFY;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wontopos-mcp",
-  "version": "1.0.17",
+  "version": "1.0.18",
   "mcpName": "com.wontopos/mcp",
   "description": "(beta) Wontopos (WOS) long-term memory as an MCP server — one memory across Claude Code, Claude Desktop, Cursor, ChatGPT, and your own agents.",
   "keywords": [