wontopos-mcp 1.0.11 → 1.0.12

package/README.md

@@ -117,6 +117,15 @@ automatic retries, redirect refusal, response caps, and key hygiene apply as-is.
 
 ## Changelog
 
+- **1.0.12** - a server that could not answer anything reported itself ready. A store id
+  outside `[A-Za-z0-9][A-Za-z0-9._-]{0,63}` (`선우`, `田中`, an email) cannot be created
+  and cannot be reached, so every tool call 404s - and 1.0.11 warned about it and then
+  served anyway. Worse, the boot check told the agent to fix it with `create_store`,
+  which answers 400 on that same id. A bad API key has always exited loudly; an id that
+  nothing at runtime can repair is the same situation, so it now exits too. The exception
+  is `WONTOPOS_ALLOW_STORE_OVERRIDE=1`, where the agent names a store per call and the
+  configured one is only a default - there the server still has work to do, so it warns
+  and serves.
 - **1.0.11** - fixes a regression 1.0.10 introduced, published the same day. 1.0.10 was
   right that the folded id should be *announced* and wrong to also *send* it. The API
   records the raw id next to the folded one on purpose: that is how it tells a genuine

package/index.mjs

@@ -577,12 +577,24 @@ console.error(
 // names the folded store, which is the part the SDK does not cover.
 //
 // This one has no SDK equivalent — the SDK knows the fold, not the creation rule.
+// A key that can do nothing exits(1). An id that can do nothing used to WARN and then
+// serve — so the host reported a healthy MCP server whose every call 404'd, and the
+// boot check's own advice ("create_store") was impossible: creating this id answers
+// 400 by the same rule. Nothing the agent does at runtime can repair it, so it belongs
+// on the same side as the bad key.
+//
+// Unless the store is not pinned: under ALLOW_STORE_OVERRIDE the agent supplies an id
+// per call and the configured one is only a default, so the server still has work.
 if (STORE_ID_UNUSABLE) {
   console.error(
     `wontopos-mcp: WONTOPOS_USER_ID ${JSON.stringify(STORE)} is not a usable store id. The API requires English ` +
       "letters, digits and . _ - (1-64 chars, starting with a letter or digit), so creating it answers 400 and " +
       "every other call 404s. Romanize it or pick a latin id."
   );
+  if (!ALLOW_STORE_OVERRIDE) {
+    console.error("wontopos-mcp: every tool call would fail and no tool could repair it. Exiting.");
+    process.exit(1);
+  }
 }
 
 // Boot check (one metered stats call, after connect so host startup never waits):
@@ -609,9 +621,12 @@ mem.stats().then(
     } else if (status === 404) {
       console.error(
         `wontopos-mcp: the key works but store "${STORE_FOLDED}" does not exist — ` +
-        (READ_ONLY
-          ? "fix WONTOPOS_USER_ID (read-only mode cannot create stores)."
-          : "ask the agent to create it (create_store) or fix WONTOPOS_USER_ID.")
+        (STORE_ID_UNUSABLE
+          // create_store answers 400 on this id by the same rule, so do not send them there.
+          ? "and it cannot be created under this id. Set WONTOPOS_USER_ID to a latin-alphanumeric id."
+          : READ_ONLY
+            ? "fix WONTOPOS_USER_ID (read-only mode cannot create stores)."
+            : "ask the agent to create it (create_store) or fix WONTOPOS_USER_ID.")
       );
     } else if (status === 402) {
       console.error("wontopos-mcp: the key works but the account has no card or balance (402) — top up at https://wontopos.com/console.");

package/package.json

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