denpex-mcp 0.2.17 → 0.2.19
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 -4
- package/dist/index.js +7447 -3476
- package/package.json +3 -1
package/README.md
CHANGED
|
@@ -18,10 +18,12 @@ straight off disk and hands back the root cause and the fix.
|
|
|
18
18
|
|
|
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
|
-
incidents. *Without a key, `diagnose_crash`
|
|
22
|
-
the
|
|
23
|
-
|
|
24
|
-
|
|
21
|
+
incidents. *Without a key, the first `diagnose_crash` cloud run is frictionless and uses
|
|
22
|
+
the same canonical anonymous engine as the homepage. Later new anonymous diagnoses need
|
|
23
|
+
the browser check at [denpex.com](https://denpex.com/#instant-diagnosis), which MCP cannot
|
|
24
|
+
complete, or an API key. Anonymous clarifications reuse the server-issued, log-bound
|
|
25
|
+
refinement token automatically (or accept it explicitly after an MCP restart), so
|
|
26
|
+
answering Denpex does not spend another diagnosis and cannot be forged with a public
|
|
25
27
|
boolean header. Set `DENPEX_LOCAL=1` explicitly for zero-egress;
|
|
26
28
|
`lookup_failure` and `analyze_cascade` remain available from the bundled offline data.*
|
|
27
29
|
|