@odatano/nightgate-mcp 0.18.0 → 0.18.1

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/CHANGELOG.md CHANGED
@@ -7,6 +7,23 @@ The README says which NIGHTGATE the current version needs.
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [0.18.1] - 2026-10-26
11
+
12
+ Needs NIGHTGATE 0.36.0.
13
+
14
+ ### Fixed
15
+
16
+ - **Writes from a fresh install.** `@odatano/nightgate-tx` ^0.15.1 installs one
17
+ copy of `@midnight-ntwrk/onchain-runtime-v3`. Two copies failed every write
18
+ after proving with `expected instance of StateValue`.
19
+
20
+ ### Documentation
21
+
22
+ - `docs/tools.md`: how a client keeps a write open, and that the MCP Inspector
23
+ CLI stops it after 60 seconds.
24
+ - README and `docs/tools.md`: servers on one machine share one seed file and
25
+ so one identity unless each sets its own seed.
26
+
10
27
  ## [0.18.0] - 2026-10-26
11
28
 
12
29
  Needs NIGHTGATE 0.36.0; from 0.37.0 the server holds each status read until the job settles.
package/README.md CHANGED
@@ -45,7 +45,8 @@ That is all the setup. `anchor_document` with the sha256 of a document anchors
45
45
  it in the shared sandbox vault and answers once it landed, with the free
46
46
  `verify_attestation` call that shows it on-chain. The first write creates your
47
47
  seed in `~/.nightgate-mcp/seed` and says so; keep that file, it is your
48
- identity on Midnight. `get_usage` shows the units left on the key.
48
+ identity on Midnight. Servers on one machine share it unless each sets its
49
+ own `NIGHTGATE_SEED_HEX`. `get_usage` shows the units left on the key.
49
50
 
50
51
  ## Tools
51
52
 
package/docs/tools.md CHANGED
@@ -62,7 +62,10 @@ A tool that was cut off, for example by a client timeout, or that came back
62
62
  started and submits nothing new, so there is no second fee.
63
63
 
64
64
  While a call runs it sends MCP progress every 5 seconds, so a client that
65
- resets its request timeout on progress keeps the call open.
65
+ resets its request timeout on progress keeps the call open. A proof takes
66
+ several minutes. The MCP Inspector CLI ignores progress and stops after 60
67
+ seconds, so it cannot run the writes. With `@modelcontextprotocol/sdk`, call
68
+ `client.callTool(params, undefined, { timeout: 600000, resetTimeoutOnProgress: true })`.
66
69
 
67
70
  ## Sandbox vaults
68
71
 
@@ -89,7 +92,9 @@ disclosures of those records.
89
92
  seed creates it, readable by the owner only, and its answer carries
90
93
  `seed: { created, file, meaning }`.
91
94
 
92
- Keep the file and back it up.
95
+ Keep the file and back it up. Every server on the same machine shares that
96
+ file and so one identity. For separate identities, give each server its own
97
+ `NIGHTGATE_SEED_HEX` or `NIGHTGATE_SEED_FILE`.
93
98
 
94
99
  ## Field claims
95
100
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@odatano/nightgate-mcp",
3
- "version": "0.18.0",
3
+ "version": "0.18.1",
4
4
  "description": "MCP server exposing NIGHTGATE (Midnight blockchain attestation layer) to AI agents",
5
5
  "license": "Apache-2.0",
6
6
  "publishConfig": {
@@ -47,7 +47,7 @@
47
47
  ],
48
48
  "dependencies": {
49
49
  "@modelcontextprotocol/sdk": "^1.0.0",
50
- "@odatano/nightgate-tx": "^0.15.0",
50
+ "@odatano/nightgate-tx": "^0.15.1",
51
51
  "zod": "^3.23.0"
52
52
  },
53
53
  "peerDependencies": {