@seanhogg/builderforce-memory-mcp 2026.6.35 → 2026.7.11
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.
- package/README.md +1 -1
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -9,7 +9,7 @@ tool core over a pluggable `MemoryBackend`, three transports:
|
|
|
9
9
|
| **stdio** | `runStdio(backend)` / `npx @seanhogg/builderforce-memory-mcp` | `{ type:"stdio", command, args }` | any language / separate process; decouples the SSM+IndexedDB deps from the consumer |
|
|
10
10
|
| **HTTP (Streamable)** | `createMemoryHttpHandler(backend, { authToken })` | `{ type:"http", url, headers }` | multi-tenant / networked (builderforce.ai hosting, remote agents) |
|
|
11
11
|
|
|
12
|
-
> **Technical report & peer review.** This transport is reviewed in the Evermind technical report's adversarial [`PEER-REVIEW.md`](../../publication/evermind/PEER-REVIEW.md). Note before exposing the HTTP handler publicly: the `authToken` check is a **non-constant-time** string compare (timing channel) and the handler shares **one `backend` with no per-tenant isolation** — a single token reads every tenant's facts. Despite the "multi-tenant" note above, real isolation (token→namespace mapping, constant-time compare, rate limiting) is **not yet implemented**. Tracked as `EVM-3` in the Builderforce.ai Consolidated Gap Register.
|
|
12
|
+
> **Technical report & peer review.** This transport is reviewed in the Evermind technical report's adversarial [`PEER-REVIEW.md`](../../publication/evermind/PEER-REVIEW.md). Note before exposing the HTTP handler publicly: the `authToken` check is a **non-constant-time** string compare (timing channel) and the handler shares **one `backend` with no per-tenant isolation** — a single token reads every tenant's facts. Despite the "multi-tenant" note above, real isolation (token→namespace mapping, constant-time compare, rate limiting) is **not yet implemented**. Tracked as `EVM-3` in the Builderforce.ai Consolidated Gap Register. **Resolved in v2026.6.34:** the HTTP handler now uses a constant-time token compare and per-tenant namespace isolation (see the resolution addendum in [`PEER-REVIEW.md`](../../publication/evermind/PEER-REVIEW.md)).
|
|
13
13
|
|
|
14
14
|
## Why this saves tokens
|
|
15
15
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@seanhogg/builderforce-memory-mcp",
|
|
3
|
-
"version": "2026.
|
|
3
|
+
"version": "2026.7.11",
|
|
4
4
|
"description": "BuilderForce Agent Memory — MCP transport. Exposes @seanhogg/builderforce-memory to any MCP client (Claude Agent SDK in-process, stdio, or HTTP) over a pluggable MemoryBackend, with token-saving fetch-on-demand recall.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "dist/index.js",
|
|
@@ -50,7 +50,7 @@
|
|
|
50
50
|
},
|
|
51
51
|
"peerDependencies": {
|
|
52
52
|
"@anthropic-ai/claude-agent-sdk": ">=0.1.0",
|
|
53
|
-
"@seanhogg/builderforce-memory": "^2026.
|
|
53
|
+
"@seanhogg/builderforce-memory": "^2026.7.11",
|
|
54
54
|
"fake-indexeddb": "^6.0.0"
|
|
55
55
|
},
|
|
56
56
|
"peerDependenciesMeta": {
|
|
@@ -73,7 +73,7 @@
|
|
|
73
73
|
"fake-indexeddb": "^6.0.0",
|
|
74
74
|
"typescript": "^6.0.3",
|
|
75
75
|
"@typescript/native-preview": "7.0.0-dev.20260627.2",
|
|
76
|
-
"@seanhogg/builderforce-memory": "2026.
|
|
76
|
+
"@seanhogg/builderforce-memory": "2026.7.11"
|
|
77
77
|
},
|
|
78
78
|
"engines": {
|
|
79
79
|
"node": ">=18.0.0"
|