denpex-mcp 0.2.6 → 0.2.8
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 +6 -3
- package/dist/index.js +74 -8
- package/package.json +60 -60
package/README.md
CHANGED
|
@@ -19,7 +19,10 @@ straight off disk and hands back the root cause and the fix.
|
|
|
19
19
|
Sign in at **[denpex.com/dashboard](https://denpex.com/dashboard) → API Keys** and create a key (`dpx_…`).
|
|
20
20
|
The key unlocks authenticated cloud diagnosis, your diagnosis history, quota, and fleet
|
|
21
21
|
incidents. *Without a key, `diagnose_crash` uses the same canonical anonymous engine as
|
|
22
|
-
the homepage's three free diagnoses.
|
|
22
|
+
the homepage's three free diagnoses. Anonymous clarifications reuse the server-issued,
|
|
23
|
+
log-bound refinement token automatically (or accept it explicitly after an MCP restart),
|
|
24
|
+
so answering Denpex does not spend another diagnosis and cannot be forged with a public
|
|
25
|
+
boolean header. Set `DENPEX_LOCAL=1` explicitly for zero-egress;
|
|
23
26
|
`lookup_failure` and `analyze_cascade` remain available from the bundled offline data.*
|
|
24
27
|
|
|
25
28
|
### 2. Add it to your client
|
|
@@ -103,7 +106,7 @@ errors is cloud-only and simply unavailable offline.
|
|
|
103
106
|
|
|
104
107
|
| Tool | What it does | Needs |
|
|
105
108
|
|------|--------------|-------|
|
|
106
|
-
| `diagnose_crash` | Root cause + escalating fix from `logs` / `file` / `dir`. Also accepts `telemetry` (dmesg / nvidia-smi / ibstat), `codeContext` and `
|
|
109
|
+
| `diagnose_crash` | Root cause + escalating fix from `logs` / `file` / `dir`. Also accepts `telemetry` (dmesg / nvidia-smi / ibstat), `codeContext`, `topologyMap`, typed `operatorAnswers`, and (after an anonymous MCP restart) the prior `refinementToken`. | canonical cloud by default; explicit offline mode |
|
|
107
110
|
| `lookup_failure` | Search the bundled encyclopedia (300+ classes) by code/keyword/symptom. | works offline |
|
|
108
111
|
| `analyze_cascade` | Find the culprit rank in a distributed hang; route Xid faults. | works offline |
|
|
109
112
|
| `submit_fix_outcome` | Report whether a fix worked. **This is what makes the next diagnosis better.** | API key |
|
|
@@ -154,7 +157,7 @@ Two fields deserve attention when you write the agent loop:
|
|
|
154
157
|
```bash
|
|
155
158
|
npm install
|
|
156
159
|
npm run build # regenerates the offline corpus, then bundles dist/index.js
|
|
157
|
-
npm test #
|
|
160
|
+
npm test # 111 unit + protocol-integration tests
|
|
158
161
|
npm run inspector # interactive protocol inspector (MCP Inspector)
|
|
159
162
|
```
|
|
160
163
|
|