@kryptosai/mcp-observatory 1.32.1 → 1.34.0

package/docs/safety-index/artifacts/mysql-mcp-server.md

@@ -0,0 +1,106 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:34:46.482Z
+
+## Target and Environment Metadata
+
+- Target: `mysql-mcp-server`
+- Adapter: `local-process`
+- Command: `npx -y mysql-mcp-server`
+- Server: `unknown `
+- Platform: `darwin 25.5.0`
+- Node: `v22.22.1`
+
+## Executive Summary
+
+| Gate | Total | Pass | Fail | Partial | Unsupported | Flaky | Skipped |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| fail | 3 | 0 | 0 | 0 | 0 | 0 | 3 |
+
+## At a Glance
+
+- Safety verdict: **Blocked** — One or more checks can break agent dependence and should be fixed before production use.
+- Top risks: startup: server failed to start
+- Regression/schema drift: Run `mcp-observatory diff <previous-run.json> <current-run.json>` to classify regressions and schema drift.
+- Failing checks: none
+- Partial or flaky checks: none
+- Skipped checks: tools, prompts, resources
+- Unsupported checks: none
+- Suggested next step: Run the target command manually, compare stderr with the diagnosis below, and only raise timeoutMs if startup is genuinely slow.
+- CI next step: `Add CI: npx @kryptosai/mcp-observatory setup-ci --all --command "npx -y <server-package>"`
+
+## What Was Not Tested
+
+- 🔒 network_egress: No outbound network calls were attempted during scan
+- 🔒 filesystem_mutation: Filesystem write operations were not exercised
+- 🔒 credential_access: Credential scanning was not performed
+- ℹ️ destructive_payloads: Destructive payloads were not attempted (safe-mode only)
+
+## Regressions and Recoveries
+
+_Use the `diff` command against another run artifact to classify regressions and recoveries over time._
+
+## Failure Diagnosis
+
+```text
+Could not establish a plain stdio MCP session for target `mysql-mcp-server`.
+Command: npx -y mysql-mcp-server
+Diagnosis: The process exited or detached before MCP initialization completed.
+Raw error: MCP error -32000: Connection closed
+Likely causes:
+- The package may expect extra startup arguments or environment variables.
+- The package may not behave like a plain local-process stdio target under this invocation.
+- The server may be crashing immediately and only leaving clues on stderr.
+Next steps:
+- Run the command manually and look for usage output, auth prompts, or crash text.
+- Check whether the package expects a different transport or an app-oriented startup flow.
+- Use the recent stderr lines below before assuming this is a harness bug.
+Recent stderr:
+- at getConfigFromEnv (file:///Users/williamweishuhn/.npm/_npx/58eed5751e5ff699/node_modules/mysql-mcp-server/build/connection.js:106:15)
+- at file:///Users/williamweishuhn/.npm/_npx/58eed5751e5ff699/node_modules/mysql-mcp-server/build/index.js:20:20
+- at ModuleJob.run (node:internal/modules/esm/module_job:343:25)
+- at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:665:26)
+- at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:117:5)
+```
+
+## Full Capability Status Table
+
+| Focus | Check | Status | Duration (ms) | Message |
+| --- | --- | --- | --- | --- |
+| inspect startup | prompts | skipped | 0.00 | Skipped because startup failed before the MCP session initialized. See the failure diagnosis. |
+| inspect startup | resources | skipped | 0.00 | Skipped because startup failed before the MCP session initialized. See the failure diagnosis. |
+| inspect startup | tools | skipped | 0.00 | Skipped because startup failed before the MCP session initialized. See the failure diagnosis. |
+
+## Evidence Snippets
+
+### prompts — skipped
+
+Summary: Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
+
+_No evidence was captured._
+
+### resources — skipped
+
+Summary: Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
+
+_No evidence was captured._
+
+### tools — skipped
+
+Summary: Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
+
+_No evidence was captured._
+
+## Reproduction Commands
+
+```bash
+npm run cli -- run --target <path-to-target-config.json>
+npm run cli -- report --run <path-to-run-artifact.json> --format markdown
+```
+
+## Artifact Provenance
+
+- Artifact type: `run`
+- Schema version: `1.0.0`
+- Run ID: `run_2026-07-15T223446482Z_8d8632a7`
+- Gate: `fail`

package/docs/safety-index/artifacts/nadra-mcp.json

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-15T223557353Z_5a3f2a63",
+  "createdAt": "2026-07-15T22:35:57.353Z",
+  "toolVersion": "1.32.1",
+  "target": {
+    "targetId": "nadra-mcp",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "nadra-mcp"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "nadra-mcp",
+      "purpose": "mcp-safety-index",
+      "riskClass": "National identity database access",
+      "failureClass": "Identity verification/CNIC boundary",
+      "whyItMatters": "NADRA maintains Pakistan's national identity database for 240M+ citizens. MCP servers verifying CNIC numbers, issuing identity documents, or querying demographic data handle the entire Pakistani population's PII — a massive identity trust boundary invisible to Western scanners."
+    }
+  },
+  "environment": {
+    "platform": "darwin 25.5.0",
+    "nodeVersion": "v22.22.1"
+  },
+  "summary": {
+    "total": 3,
+    "pass": 0,
+    "fail": 0,
+    "partial": 0,
+    "unsupported": 0,
+    "flaky": 0,
+    "skipped": 3,
+    "gate": "fail"
+  },
+  "checks": [
+    {
+      "id": "tools",
+      "capability": "tools",
+      "status": "skipped",
+      "durationMs": 0,
+      "message": "Skipped because startup failed before the MCP session initialized. See the failure diagnosis.",
+      "evidence": []
+    },
+    {
+      "id": "prompts",
+      "capability": "prompts",
+      "status": "skipped",
+      "durationMs": 0,
+      "message": "Skipped because startup failed before the MCP session initialized. See the failure diagnosis.",
+      "evidence": []
+    },
+    {
+      "id": "resources",
+      "capability": "resources",
+      "status": "skipped",
+      "durationMs": 0,
+      "message": "Skipped because startup failed before the MCP session initialized. See the failure diagnosis.",
+      "evidence": []
+    }
+  ],
+  "fatalError": "Could not establish a plain stdio MCP session for target `nadra-mcp`.\nCommand: npx -y nadra-mcp\nDiagnosis: The process exited or detached before MCP initialization completed.\nRaw error: MCP error -32000: Connection closed\nLikely causes:\n- The package may expect extra startup arguments or environment variables.\n- The package may not behave like a plain local-process stdio target under this invocation.\n- The server may be crashing immediately and only leaving clues on stderr.\nNext steps:\n- Run the command manually and look for usage output, auth prompts, or crash text.\n- Check whether the package expects a different transport or an app-oriented startup flow.\n- Use the recent stderr lines below before assuming this is a harness bug.\nRecent stderr:\n- npm error 404  'nadra-mcp@*' is not in this registry.\n- npm error 404\n- npm error 404 Note that you can also install from a\n- npm error 404 tarball, folder, http url, or git url.\n- npm error A complete log of this run can be found in: /Users/williamweishuhn/.npm/_logs/2026-07-15T22_35_57_428Z-debug-0.log"
+}

package/docs/safety-index/artifacts/nadra-mcp.md

@@ -0,0 +1,106 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:35:57.353Z
+
+## Target and Environment Metadata
+
+- Target: `nadra-mcp`
+- Adapter: `local-process`
+- Command: `npx -y nadra-mcp`
+- Server: `unknown `
+- Platform: `darwin 25.5.0`
+- Node: `v22.22.1`
+
+## Executive Summary
+
+| Gate | Total | Pass | Fail | Partial | Unsupported | Flaky | Skipped |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| fail | 3 | 0 | 0 | 0 | 0 | 0 | 3 |
+
+## At a Glance
+
+- Safety verdict: **Blocked** — One or more checks can break agent dependence and should be fixed before production use.
+- Top risks: startup: server failed to start
+- Regression/schema drift: Run `mcp-observatory diff <previous-run.json> <current-run.json>` to classify regressions and schema drift.
+- Failing checks: none
+- Partial or flaky checks: none
+- Skipped checks: tools, prompts, resources
+- Unsupported checks: none
+- Suggested next step: Run the target command manually, compare stderr with the diagnosis below, and only raise timeoutMs if startup is genuinely slow.
+- CI next step: `Add CI: npx @kryptosai/mcp-observatory setup-ci --all --command "npx -y <server-package>"`
+
+## What Was Not Tested
+
+- 🔒 network_egress: No outbound network calls were attempted during scan
+- 🔒 filesystem_mutation: Filesystem write operations were not exercised
+- 🔒 credential_access: Credential scanning was not performed
+- ℹ️ destructive_payloads: Destructive payloads were not attempted (safe-mode only)
+
+## Regressions and Recoveries
+
+_Use the `diff` command against another run artifact to classify regressions and recoveries over time._
+
+## Failure Diagnosis
+
+```text
+Could not establish a plain stdio MCP session for target `nadra-mcp`.
+Command: npx -y nadra-mcp
+Diagnosis: The process exited or detached before MCP initialization completed.
+Raw error: MCP error -32000: Connection closed
+Likely causes:
+- The package may expect extra startup arguments or environment variables.
+- The package may not behave like a plain local-process stdio target under this invocation.
+- The server may be crashing immediately and only leaving clues on stderr.
+Next steps:
+- Run the command manually and look for usage output, auth prompts, or crash text.
+- Check whether the package expects a different transport or an app-oriented startup flow.
+- Use the recent stderr lines below before assuming this is a harness bug.
+Recent stderr:
+- npm error 404  'nadra-mcp@*' is not in this registry.
+- npm error 404
+- npm error 404 Note that you can also install from a
+- npm error 404 tarball, folder, http url, or git url.
+- npm error A complete log of this run can be found in: /Users/williamweishuhn/.npm/_logs/2026-07-15T22_35_57_428Z-debug-0.log
+```
+
+## Full Capability Status Table
+
+| Focus | Check | Status | Duration (ms) | Message |
+| --- | --- | --- | --- | --- |
+| inspect startup | prompts | skipped | 0.00 | Skipped because startup failed before the MCP session initialized. See the failure diagnosis. |
+| inspect startup | resources | skipped | 0.00 | Skipped because startup failed before the MCP session initialized. See the failure diagnosis. |
+| inspect startup | tools | skipped | 0.00 | Skipped because startup failed before the MCP session initialized. See the failure diagnosis. |
+
+## Evidence Snippets
+
+### prompts — skipped
+
+Summary: Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
+
+_No evidence was captured._
+
+### resources — skipped
+
+Summary: Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
+
+_No evidence was captured._
+
+### tools — skipped
+
+Summary: Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
+
+_No evidence was captured._
+
+## Reproduction Commands
+
+```bash
+npm run cli -- run --target <path-to-target-config.json>
+npm run cli -- report --run <path-to-run-artifact.json> --format markdown
+```
+
+## Artifact Provenance
+
+- Artifact type: `run`
+- Schema version: `1.0.0`
+- Run ID: `run_2026-07-15T223557353Z_5a3f2a63`
+- Gate: `fail`

package/docs/safety-index/artifacts/neon-server.json

@@ -2,9 +2,9 @@
   "artifactType": "run",
   "schemaVersion": "1.0.0",
   "gate": "fail",
-  "runId": "run_2026-07-12T234427856Z_5836c2d6",
-  "createdAt": "2026-07-12T23:44:27.856Z",
-  "toolVersion": "1.31.0",
+  "runId": "run_2026-07-15T223345711Z_873cc482",
+  "createdAt": "2026-07-15T22:33:45.711Z",
+  "toolVersion": "1.32.1",
   "target": {
     "targetId": "neon-server",
     "adapter": "local-process",
@@ -62,5 +62,5 @@
       "evidence": []
     }
   ],
-  "fatalError": "Could not establish a plain stdio MCP session for target `neon-server`.\nCommand: npx -y mcp-server-neon\nDiagnosis: The process exited or detached before MCP initialization completed.\nRaw error: MCP error -32000: Connection closed\nLikely causes:\n- The package may expect extra startup arguments or environment variables.\n- The package may not behave like a plain local-process stdio target under this invocation.\n- The server may be crashing immediately and only leaving clues on stderr.\nNext steps:\n- Run the command manually and look for usage output, auth prompts, or crash text.\n- Check whether the package expects a different transport or an app-oriented startup flow.\n- Use the recent stderr lines below before assuming this is a harness bug.\nRecent stderr:\n- npm error could not determine executable to run\n- npm error A complete log of this run can be found in: /Users/williamweishuhn/.npm/_logs/2026-07-12T23_44_27_929Z-debug-0.log"
+  "fatalError": "Could not establish a plain stdio MCP session for target `neon-server`.\nCommand: npx -y mcp-server-neon\nDiagnosis: The process exited or detached before MCP initialization completed.\nRaw error: MCP error -32000: Connection closed\nLikely causes:\n- The package may expect extra startup arguments or environment variables.\n- The package may not behave like a plain local-process stdio target under this invocation.\n- The server may be crashing immediately and only leaving clues on stderr.\nNext steps:\n- Run the command manually and look for usage output, auth prompts, or crash text.\n- Check whether the package expects a different transport or an app-oriented startup flow.\n- Use the recent stderr lines below before assuming this is a harness bug.\nRecent stderr:\n- npm error could not determine executable to run\n- npm error A complete log of this run can be found in: /Users/williamweishuhn/.npm/_logs/2026-07-15T22_33_45_780Z-debug-0.log"
 }

package/docs/safety-index/artifacts/neon-server.md

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-12T23:44:27.856Z
+Generated at 2026-07-15T22:33:45.711Z
 
 ## Target and Environment Metadata
 
@@ -57,7 +57,7 @@ Next steps:
 - Use the recent stderr lines below before assuming this is a harness bug.
 Recent stderr:
 - npm error could not determine executable to run
-- npm error A complete log of this run can be found in: /Users/williamweishuhn/.npm/_logs/2026-07-12T23_44_27_929Z-debug-0.log
+- npm error A complete log of this run can be found in: /Users/williamweishuhn/.npm/_logs/2026-07-15T22_33_45_780Z-debug-0.log
 ```
 
 ## Full Capability Status Table
@@ -99,5 +99,5 @@ npm run cli -- report --run <path-to-run-artifact.json> --format markdown
 
 - Artifact type: `run`
 - Schema version: `1.0.0`
-- Run ID: `run_2026-07-12T234427856Z_5836c2d6`
+- Run ID: `run_2026-07-15T223345711Z_873cc482`
 - Gate: `fail`

package/docs/safety-index/artifacts/notion-server.json

@@ -2,9 +2,9 @@
   "artifactType": "run",
   "schemaVersion": "1.0.0",
   "gate": "pass",
-  "runId": "run_2026-07-12T234422045Z_8961b236",
-  "createdAt": "2026-07-12T23:44:22.045Z",
-  "toolVersion": "1.31.0",
+  "runId": "run_2026-07-15T223340323Z_a54e806c",
+  "createdAt": "2026-07-15T22:33:40.323Z",
+  "toolVersion": "1.32.1",
   "target": {
     "targetId": "notion-server",
     "adapter": "local-process",
@@ -43,7 +43,7 @@
       "id": "tools",
       "capability": "tools",
       "status": "pass",
-      "durationMs": 1.7988749999967695,
+      "durationMs": 1.6952499999970314,
       "message": "Advertised capability responded with the minimal expected shape (24 items).",
       "evidence": [
         {
@@ -6306,7 +6306,7 @@
       "id": "prompts",
       "capability": "prompts",
       "status": "unsupported",
-      "durationMs": 0.0010419999998703133,
+      "durationMs": 0.0006250000005820766,
       "message": "Prompts are not advertised by the target.",
       "evidence": [
         {
@@ -6322,7 +6322,7 @@
       "id": "resources",
       "capability": "resources",
       "status": "unsupported",
-      "durationMs": 0.0004579999986162875,
+      "durationMs": 0.0003749999996216502,
       "message": "Resources are not advertised by the target.",
       "evidence": [
         {
@@ -6338,7 +6338,7 @@
       "id": "security-lite",
       "capability": "security-lite",
       "status": "pass",
-      "durationMs": 0.06054199999925913,
+      "durationMs": 0.04754200000024866,
       "message": "No security issues detected (lightweight scan).",
       "evidence": [
         {
@@ -6354,7 +6354,7 @@
       "id": "runtime-profile",
       "capability": "runtime-profile",
       "status": "pass",
-      "durationMs": 0.1742500000000291,
+      "durationMs": 0.16424999999799184,
       "message": "Detected 10 potential egress target(s) and 21 potential state mutation(s) with low confidence.",
       "evidence": [
         {
@@ -6563,7 +6563,7 @@
       "id": "conformance",
       "capability": "conformance",
       "status": "pass",
-      "durationMs": 205.06424999999945,
+      "durationMs": 167.19545799999833,
       "message": "All 7 conformance checks passed.",
       "evidence": [
         {
@@ -6589,7 +6589,7 @@
       "id": "schema-quality",
       "capability": "schema-quality",
       "status": "partial",
-      "durationMs": 3.6534999999967113,
+      "durationMs": 2.0611250000001746,
       "message": "Found 31 quality finding(s) across 24 item(s): 0 warnings, 31 info.",
       "evidence": [
         {
@@ -6840,7 +6840,7 @@
       "id": "security",
       "capability": "security",
       "status": "pass",
-      "durationMs": 3.776832999999897,
+      "durationMs": 1.2720829999998386,
       "message": "No security issues detected.",
       "evidence": [
         {
@@ -6856,7 +6856,7 @@
       "id": "attack-sim",
       "capability": "attack-sim",
       "status": "partial",
-      "durationMs": 3.114000000001397,
+      "durationMs": 2.5102500000029977,
       "message": "Safe attack simulation found 1 finding(s): 0 high, 1 medium, 0 low.",
       "evidence": [
         {
@@ -6942,17 +6942,17 @@
         "weight": 0.1,
         "score": 100,
         "details": [
-          "Connect: 806ms",
+          "Connect: 782ms",
           "p95 latency: 2ms (3 operations)"
         ]
       }
     ]
   },
   "performanceMetrics": {
-    "connectMs": 806.2848330000015,
-    "toolsListMs": 1.7988749999967695,
-    "promptsListMs": 0.0010419999998703133,
-    "resourcesListMs": 0.0004579999986162875
+    "connectMs": 781.9518330000028,
+    "toolsListMs": 1.6952499999970314,
+    "promptsListMs": 0.0006250000005820766,
+    "resourcesListMs": 0.0003749999996216502
   },
   "runtimeProfile": {
     "egress": [
@@ -7145,7 +7145,7 @@
         "source": "description_analysis"
       }
     ],
-    "analyzedAt": "2026-07-12T23:44:22.854Z",
+    "analyzedAt": "2026-07-15T22:33:41.108Z",
     "confidence": "medium"
   }
 }

package/docs/safety-index/artifacts/notion-server.md

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-12T23:44:22.045Z
+Generated at 2026-07-15T22:33:40.323Z
 
 ## Target and Environment Metadata
 
@@ -91,7 +91,7 @@ The following state-modifying operations were identified from tool schemas:
 | filesystem | write | working_directory | description_analysis |
 | filesystem | write | working_directory | description_analysis |
 
-_Analyzed at 2026-07-12T23:44:22.854Z_
+_Analyzed at 2026-07-15T22:33:41.108Z_
 
 ## Regressions and Recoveries
 
@@ -101,13 +101,13 @@ _Use the `diff` command against another run artifact to classify regressions and
 
 | Focus | Check | Status | Duration (ms) | Message |
 | --- | --- | --- | --- | --- |
-| healthy | conformance | pass | 205.06 | All 7 conformance checks passed. |
-| healthy | runtime-profile | pass | 0.17 | Detected 10 potential egress target(s) and 21 potential state mutation(s) with low confidence. |
-| healthy | security | pass | 3.78 | No security issues detected. |
-| healthy | security-lite | pass | 0.06 | No security issues detected (lightweight scan). |
-| healthy | tools | pass | 1.80 | Advertised capability responded with the minimal expected shape (24 items). |
-| review | attack-sim | partial | 3.11 | Safe attack simulation found 1 finding(s): 0 high, 1 medium, 0 low. |
-| review | schema-quality | partial | 3.65 | Found 31 quality finding(s) across 24 item(s): 0 warnings, 31 info. |
+| healthy | conformance | pass | 167.20 | All 7 conformance checks passed. |
+| healthy | runtime-profile | pass | 0.16 | Detected 10 potential egress target(s) and 21 potential state mutation(s) with low confidence. |
+| healthy | security | pass | 1.27 | No security issues detected. |
+| healthy | security-lite | pass | 0.05 | No security issues detected (lightweight scan). |
+| healthy | tools | pass | 1.70 | Advertised capability responded with the minimal expected shape (24 items). |
+| review | attack-sim | partial | 2.51 | Safe attack simulation found 1 finding(s): 0 high, 1 medium, 0 low. |
+| review | schema-quality | partial | 2.06 | Found 31 quality finding(s) across 24 item(s): 0 warnings, 31 info. |
 | confirm intent | prompts | unsupported | 0.00 | Prompts are not advertised by the target. |
 | confirm intent | resources | unsupported | 0.00 | Resources are not advertised by the target. |
 
@@ -232,5 +232,5 @@ npm run cli -- report --run <path-to-run-artifact.json> --format markdown
 
 - Artifact type: `run`
 - Schema version: `1.0.0`
-- Run ID: `run_2026-07-12T234422045Z_8961b236`
+- Run ID: `run_2026-07-15T223340323Z_a54e806c`
 - Gate: `pass`

package/docs/safety-index/artifacts/obsidian-mcp.json

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-15T223501652Z_4a375362",
+  "createdAt": "2026-07-15T22:35:01.652Z",
+  "toolVersion": "1.32.1",
+  "target": {
+    "targetId": "obsidian-mcp",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "obsidian-mcp"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "obsidian-mcp",
+      "purpose": "mcp-safety-index",
+      "riskClass": "Personal knowledge base access",
+      "failureClass": "Note/vault/file boundary",
+      "whyItMatters": "Obsidian MCP servers can read, write, search, and link notes in personal knowledge vaults — agents could access private notes and research."
+    }
+  },
+  "environment": {
+    "platform": "darwin 25.5.0",
+    "nodeVersion": "v22.22.1"
+  },
+  "summary": {
+    "total": 3,
+    "pass": 0,
+    "fail": 0,
+    "partial": 0,
+    "unsupported": 0,
+    "flaky": 0,
+    "skipped": 3,
+    "gate": "fail"
+  },
+  "checks": [
+    {
+      "id": "tools",
+      "capability": "tools",
+      "status": "skipped",
+      "durationMs": 0,
+      "message": "Skipped because startup failed before the MCP session initialized. See the failure diagnosis.",
+      "evidence": []
+    },
+    {
+      "id": "prompts",
+      "capability": "prompts",
+      "status": "skipped",
+      "durationMs": 0,
+      "message": "Skipped because startup failed before the MCP session initialized. See the failure diagnosis.",
+      "evidence": []
+    },
+    {
+      "id": "resources",
+      "capability": "resources",
+      "status": "skipped",
+      "durationMs": 0,
+      "message": "Skipped because startup failed before the MCP session initialized. See the failure diagnosis.",
+      "evidence": []
+    }
+  ],
+  "fatalError": "Could not establish a plain stdio MCP session for target `obsidian-mcp`.\nCommand: npx -y obsidian-mcp\nDiagnosis: The process exited or detached before MCP initialization completed.\nRaw error: MCP error -32000: Connection closed\nLikely causes:\n- The package may expect extra startup arguments or environment variables.\n- The package may not behave like a plain local-process stdio target under this invocation.\n- The server may be crashing immediately and only leaving clues on stderr.\nNext steps:\n- Run the command manually and look for usage output, auth prompts, or crash text.\n- Check whether the package expects a different transport or an app-oriented startup flow.\n- Use the recent stderr lines below before assuming this is a harness bug.\nRecent stderr:\n- obsidian-mcp /tmp/vault                 # ❌ System directory\n- obsidian-mcp ~/.config/vault            # ❌ Hidden directory\n- obsidian-mcp //server/share/vault       # ❌ Network path\n- obsidian-mcp /mnt/network/vault         # ❌ Network mount\n- obsidian-mcp ~/symlink-to-vault         # ❌ External symlink"
+}

package/docs/safety-index/artifacts/obsidian-mcp.md

@@ -0,0 +1,106 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:35:01.652Z
+
+## Target and Environment Metadata
+
+- Target: `obsidian-mcp`
+- Adapter: `local-process`
+- Command: `npx -y obsidian-mcp`
+- Server: `unknown `
+- Platform: `darwin 25.5.0`
+- Node: `v22.22.1`
+
+## Executive Summary
+
+| Gate | Total | Pass | Fail | Partial | Unsupported | Flaky | Skipped |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| fail | 3 | 0 | 0 | 0 | 0 | 0 | 3 |
+
+## At a Glance
+
+- Safety verdict: **Blocked** — One or more checks can break agent dependence and should be fixed before production use.
+- Top risks: startup: server failed to start
+- Regression/schema drift: Run `mcp-observatory diff <previous-run.json> <current-run.json>` to classify regressions and schema drift.
+- Failing checks: none
+- Partial or flaky checks: none
+- Skipped checks: tools, prompts, resources
+- Unsupported checks: none
+- Suggested next step: Run the target command manually, compare stderr with the diagnosis below, and only raise timeoutMs if startup is genuinely slow.
+- CI next step: `Add CI: npx @kryptosai/mcp-observatory setup-ci --all --command "npx -y <server-package>"`
+
+## What Was Not Tested
+
+- 🔒 network_egress: No outbound network calls were attempted during scan
+- 🔒 filesystem_mutation: Filesystem write operations were not exercised
+- 🔒 credential_access: Credential scanning was not performed
+- ℹ️ destructive_payloads: Destructive payloads were not attempted (safe-mode only)
+
+## Regressions and Recoveries
+
+_Use the `diff` command against another run artifact to classify regressions and recoveries over time._
+
+## Failure Diagnosis
+
+```text
+Could not establish a plain stdio MCP session for target `obsidian-mcp`.
+Command: npx -y obsidian-mcp
+Diagnosis: The process exited or detached before MCP initialization completed.
+Raw error: MCP error -32000: Connection closed
+Likely causes:
+- The package may expect extra startup arguments or environment variables.
+- The package may not behave like a plain local-process stdio target under this invocation.
+- The server may be crashing immediately and only leaving clues on stderr.
+Next steps:
+- Run the command manually and look for usage output, auth prompts, or crash text.
+- Check whether the package expects a different transport or an app-oriented startup flow.
+- Use the recent stderr lines below before assuming this is a harness bug.
+Recent stderr:
+- obsidian-mcp /tmp/vault                 # ❌ System directory
+- obsidian-mcp ~/.config/vault            # ❌ Hidden directory
+- obsidian-mcp //server/share/vault       # ❌ Network path
+- obsidian-mcp /mnt/network/vault         # ❌ Network mount
+- obsidian-mcp ~/symlink-to-vault         # ❌ External symlink
+```
+
+## Full Capability Status Table
+
+| Focus | Check | Status | Duration (ms) | Message |
+| --- | --- | --- | --- | --- |
+| inspect startup | prompts | skipped | 0.00 | Skipped because startup failed before the MCP session initialized. See the failure diagnosis. |
+| inspect startup | resources | skipped | 0.00 | Skipped because startup failed before the MCP session initialized. See the failure diagnosis. |
+| inspect startup | tools | skipped | 0.00 | Skipped because startup failed before the MCP session initialized. See the failure diagnosis. |
+
+## Evidence Snippets
+
+### prompts — skipped
+
+Summary: Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
+
+_No evidence was captured._
+
+### resources — skipped
+
+Summary: Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
+
+_No evidence was captured._
+
+### tools — skipped
+
+Summary: Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
+
+_No evidence was captured._
+
+## Reproduction Commands
+
+```bash
+npm run cli -- run --target <path-to-target-config.json>
+npm run cli -- report --run <path-to-run-artifact.json> --format markdown
+```
+
+## Artifact Provenance
+
+- Artifact type: `run`
+- Schema version: `1.0.0`
+- Run ID: `run_2026-07-15T223501652Z_4a375362`
+- Gate: `fail`