ofw-mcp 2.20.0 → 2.20.1

package/.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "OurFamilyWizard tools for Claude Code",
-    "version": "2.20.0"
+    "version": "2.20.1"
   },
   "plugins": [
     {
@@ -14,7 +14,7 @@
       "displayName": "OurFamilyWizard",
       "source": "./",
       "description": "OurFamilyWizard co-parenting tools for Claude — messages, calendar, expenses, and journal via MCP",
-      "version": "2.20.0",
+      "version": "2.20.1",
       "author": {
         "name": "Chris Chall"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "ofw",
   "displayName": "OurFamilyWizard",
-  "version": "2.20.0",
+  "version": "2.20.1",
   "description": "OurFamilyWizard co-parenting tools for Claude — messages, calendar, expenses, and journal via MCP",
   "author": {
     "name": "Chris Chall"

package/README.md

@@ -235,7 +235,7 @@ Previews name what you are approving — recipients by name, subject and full bo
 |---|---|---|
 | `MCP_CONFIRM_MODE` | `ask-user` | What a gated write does on a client that cannot show a prompt. `ask-user`: two steps, and the model must get your approval in chat before using the token. `auto`: two steps, but the model may use the token after reviewing the preview itself. `refuse`: such writes are refused (do them on ourfamilywizard.com). An unrecognised value is treated as `refuse`. |
 | `MCP_CONFIRM_TTL_SECONDS` | `600` | How long a token stays valid. |
-| `MCP_CONFIRM_SECRET` | random per process | Signing key; set it only if tokens must survive a server restart. |
+| `MCP_CONFIRM_SECRET` | random per process | Signing key; set it only if tokens must survive a server restart. On mcp-host the host supplies a stable per-child key (`MCP_HOST_CONFIRM_SECRET`) and spent tokens are recorded under `MCP_DATA_DIR`, so an approval survives an idle restart. |
 
 Private events and `PRIVATE` uploads — which the co-parent never sees — are not gated. `OFW_WRITE_MODE` below stays the structural layer underneath: a tool your write mode excludes does not exist at all.
 

package/dist/auth-password.js

@@ -10,7 +10,7 @@
 // `resolveAuth()` in `./auth.ts` can call it without a Client instance, and
 // so tests can mock it at the module boundary.
 import { createHash } from 'node:crypto';
-import { currentCallSignal } from '@chrischall/mcp-utils';
+import { EdgeBlockedError, currentCallSignal, detectEdgeBlock } from '@chrischall/mcp-utils';
 import { BASE_URL, OFW_PROTOCOL_HEADERS, OFW_TOKEN_TTL_MS, assertOfwUrl } from './protocol.js';
 /**
  * OFW definitively refused this username/password (it re-rendered its login
@@ -86,6 +86,22 @@ export async function loginWithPassword(username, password) {
         }).toString(),
     });
     if (!response.ok) {
+        // A CDN/WAF refusal page is not OFW judging the password: name it, so the
+        // healthcheck reports edge_blocked instead of a missing credential, and
+        // nothing is latched as rejected (chrischall/mcp-host#1015). The page
+        // itself stays out of the message.
+        const edge = detectEdgeBlock({
+            body: await response.text().catch(() => ''),
+            headers: response.headers,
+            status: response.status,
+        });
+        if (edge !== null) {
+            throw new EdgeBlockedError(response.status, edge.vendor, {
+                service: 'OurFamilyWizard',
+                method: 'POST',
+                path: '/ofw/login',
+            });
+        }
         throw new Error(`OFW login failed: ${response.status} ${response.statusText}`);
     }
     const contentType = response.headers.get('content-type') ?? '';