wontopos-mcp 1.0.13 → 1.0.14

package/README.md

@@ -79,8 +79,12 @@ Create a key in the [console](https://wontopos.com). Optional env:
   this to the agent explicitly. Don't store untrusted third-party text as
   memories in a store an autonomous agent obeys.
 - **Never store secrets as memories** - anything stored is recallable by every
-  tool holding the key. Runs locally over stdio: the key stays in your
-  environment and never passes through a third-party server.
+  tool holding the key.
+- **This package runs locally over stdio**, so your key stays in your environment and
+  is never sent to us as part of an MCP session — it only rides the API calls the
+  server makes on your behalf. The hosted endpoint below is the other trade: your host
+  sends the key to us on every call, exactly like any API request. Neither is wrong;
+  pick the one whose exposure you prefer.
 
 ## Tools
 
@@ -96,6 +100,38 @@ Create a key in the [console](https://wontopos.com). Optional env:
 | `stats` | Memory counts for a store. |
 | `create_store` | Creates the pinned store after asking the user (any store with `ALLOW_STORE_OVERRIDE=1`). |
 
+## Hosted endpoint (for hosts that can't run a local process)
+
+Some MCP hosts only speak remote MCP — they cannot spawn `npx` on your machine. Those
+connect to the hosted endpoint instead. Same memory, same stores, same account:
+
+```json
+{
+  "mcpServers": {
+    "wontopos": {
+      "url": "https://api.wontopos.com/mcp",
+      "headers": {
+        "X-API-Key": "wos-live-...",
+        "X-WOS-Store": "my-project"
+      }
+    }
+  }
+}
+```
+
+`X-WOS-Store` pins the connection to one store (omit it for the seeded `default`), and
+`X-WOS-Read-Only: 1` registers no write tools. The store is named by the CONNECTION, not
+by the model — the tools take no store argument, so a prompt-injected model cannot move
+to a sibling store.
+
+It offers `recall` · `search` · `remember` · `list_memories` · `stats` · `engram` — the
+retrieval and write core. The curation tools (`update`, `forget`, `create_store`) are
+local-only for now.
+
+The endpoint is a protocol adapter, not a second way in: every tool call re-enters the
+ordinary `/api/v1/memory` routes carrying your key, so the same authentication, rate
+limits, billing gates and tenant isolation apply — the same code, not a copy of it.
+
 ## One memory, many tools
 
 Same `WONTOPOS_API_KEY` + same store id ⇒ the memory follows you:

package/index.mjs

@@ -124,7 +124,13 @@ if (!apiKey) {
 // non-numeric value, 0, negative) falls back to the default rather than being
 // passed through as a broken timeout — mirrors the SDK's NaN guard.
 const timeoutRaw = Number(process.env.WONTOPOS_TIMEOUT_MS);
-const timeoutMs = Number.isFinite(timeoutRaw) && timeoutRaw > 0 ? timeoutRaw : 20000;
+// Upper bound as well as lower. `2147483648` is finite and positive, so it passed the
+// old check — and then Node's timer overflows a signed 32-bit millisecond field and
+// clamps it to ~1ms, so the boot check and every tool call failed almost instantly.
+// A value meant to be generous became the shortest possible timeout.
+const TIMEOUT_MAX_MS = 2_147_483_647; // Node's ceiling; above it, timers wrap to 1ms
+const timeoutMs =
+  Number.isFinite(timeoutRaw) && timeoutRaw > 0 ? Math.min(timeoutRaw, TIMEOUT_MAX_MS) : 20000;
 
 // Model: default tablet-1 (lean and fast). Reach for a fuller engine ONLY by
 // setting WONTOPOS_MODEL=scroll-1 explicitly — it costs more, so it is opt-in and
@@ -225,7 +231,12 @@ function fitToCap(result) {
         // SILENT — the model would read a short list as the whole answer. Append a
         // sentinel entry instead: still valid JSON, still an array, and the reader
         // is told what is missing. A truncation nobody can see is the worse bug.
-        return Array.isArray(clone) ? ser([...clone, { _truncated: note }]) : ser({ ...clone, _truncated: note });
+        // Re-measure WITH the note attached. The loop above checked the payload before
+        // this sentinel existed, so appending it could carry the reply back over the
+        // hard cap (measured: 131,162 bytes against a 131,072 limit). If it still does
+        // not fit, drop to the last-resort form below rather than ship an oversized one.
+        const withNote = Array.isArray(clone) ? ser([...clone, { _truncated: note }]) : ser({ ...clone, _truncated: note });
+        if (byteLen(withNote) <= MAX_RESULT_BYTES) return withNote;
       }
     }
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wontopos-mcp",
-  "version": "1.0.13",
+  "version": "1.0.14",
   "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": [