@kryptosai/mcp-observatory 1.32.1 → 1.33.0

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

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-12T23:43:56.515Z
+Generated at 2026-07-15T22:33:16.094Z
 
 ## Target and Environment Metadata
 
@@ -85,7 +85,7 @@ The following state-modifying operations were identified from tool schemas:
 | filesystem | write | working_directory | tool_schema |
 | filesystem | write | working_directory | description_analysis |
 
-_Analyzed at 2026-07-12T23:43:57.308Z_
+_Analyzed at 2026-07-15T22:33:16.909Z_
 
 ## Regressions and Recoveries
 
@@ -95,12 +95,12 @@ _Use the `diff` command against another run artifact to classify regressions and
 
 | Focus | Check | Status | Duration (ms) | Message |
 | --- | --- | --- | --- | --- |
-| healthy | conformance | pass | 6.40 | All 7 conformance checks passed. |
-| healthy | tools | pass | 6.31 | Advertised capability responded with the minimal expected shape (14 items). |
+| healthy | conformance | pass | 7.27 | All 7 conformance checks passed. |
+| healthy | tools | pass | 6.04 | Advertised capability responded with the minimal expected shape (14 items). |
 | review | attack-sim | partial | 2.82 | Safe attack simulation found 3 finding(s): 0 high, 3 medium, 0 low. |
 | review | runtime-profile | partial | 0.25 | Detected 0 potential egress target(s) and 31 potential state mutation(s) with high confidence. |
-| review | schema-quality | partial | 3.06 | Found 18 quality finding(s) across 14 item(s): 0 warnings, 18 info. |
-| review | security | partial | 3.18 | Found 3 security finding(s): 0 high, 3 medium, 0 low. |
+| review | schema-quality | partial | 2.79 | Found 18 quality finding(s) across 14 item(s): 0 warnings, 18 info. |
+| review | security | partial | 2.45 | Found 3 security finding(s): 0 high, 3 medium, 0 low. |
 | review | security-lite | partial | 0.15 | Found 3 security finding(s): 0 high, 3 medium, 0 low. |
 | 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. |
@@ -226,5 +226,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-12T234356515Z_3a972a27`
+- Run ID: `run_2026-07-15T223316094Z_0dceeb90`
 - Gate: `pass`

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

@@ -2,9 +2,9 @@
   "artifactType": "run",
   "schemaVersion": "1.0.0",
   "gate": "fail",
-  "runId": "run_2026-07-12T234424930Z_964a3213",
-  "createdAt": "2026-07-12T23:44:24.930Z",
-  "toolVersion": "1.31.0",
+  "runId": "run_2026-07-15T223342802Z_482400a3",
+  "createdAt": "2026-07-15T22:33:42.802Z",
+  "toolVersion": "1.32.1",
   "target": {
     "targetId": "firecrawl-server",
     "adapter": "local-process",
@@ -43,7 +43,7 @@
       "id": "tools",
       "capability": "tools",
       "status": "pass",
-      "durationMs": 7.67920900000172,
+      "durationMs": 8.349417000001267,
       "message": "Advertised capability responded with the minimal expected shape (26 items).",
       "evidence": [
         {
@@ -2089,7 +2089,7 @@
       "id": "prompts",
       "capability": "prompts",
       "status": "unsupported",
-      "durationMs": 0.0012920000008307397,
+      "durationMs": 0.001374999999825377,
       "message": "Prompts are not advertised by the target.",
       "evidence": [
         {
@@ -2105,7 +2105,7 @@
       "id": "resources",
       "capability": "resources",
       "status": "unsupported",
-      "durationMs": 0.0007499999992433004,
+      "durationMs": 0.000499999998282874,
       "message": "Resources are not advertised by the target.",
       "evidence": [
         {
@@ -2121,7 +2121,7 @@
       "id": "security-lite",
       "capability": "security-lite",
       "status": "fail",
-      "durationMs": 0.39983399999982794,
+      "durationMs": 0.4164170000003651,
       "message": "Found 1 security finding(s): 1 high, 0 medium, 0 low.",
       "evidence": [
         {
@@ -2151,7 +2151,7 @@
       "id": "runtime-profile",
       "capability": "runtime-profile",
       "status": "partial",
-      "durationMs": 0.43979200000103447,
+      "durationMs": 0.41108299999905284,
       "message": "Detected 21 potential egress target(s) and 16 potential state mutation(s) with high confidence.",
       "evidence": [
         {
@@ -2396,7 +2396,7 @@
       "id": "conformance",
       "capability": "conformance",
       "status": "partial",
-      "durationMs": 2.6082080000014685,
+      "durationMs": 2.9204159999972035,
       "message": "6/7 conformance checks passed, 1 failed.",
       "evidence": [
         {
@@ -2424,7 +2424,7 @@
       "id": "schema-quality",
       "capability": "schema-quality",
       "status": "partial",
-      "durationMs": 0.9859580000011192,
+      "durationMs": 1.019333000000188,
       "message": "Found 147 quality finding(s) across 26 item(s): 0 warnings, 147 info.",
       "evidence": [
         {
@@ -3499,7 +3499,7 @@
       "id": "security",
       "capability": "security",
       "status": "fail",
-      "durationMs": 1.0629580000022543,
+      "durationMs": 1.0700419999993755,
       "message": "Found 1 security finding(s): 1 high, 0 medium, 0 low.",
       "evidence": [
         {
@@ -3529,7 +3529,7 @@
       "id": "attack-sim",
       "capability": "attack-sim",
       "status": "fail",
-      "durationMs": 1.881333999997878,
+      "durationMs": 1.6968340000021271,
       "message": "Safe attack simulation found 9 finding(s): 1 high, 8 medium, 0 low.",
       "evidence": [
         {
@@ -3811,17 +3811,17 @@
         "weight": 0.1,
         "score": 100,
         "details": [
-          "Connect: 911ms",
+          "Connect: 957ms",
           "p95 latency: 8ms (3 operations)"
         ]
       }
     ]
   },
   "performanceMetrics": {
-    "connectMs": 911.4984169999989,
-    "toolsListMs": 7.67920900000172,
-    "promptsListMs": 0.0012920000008307397,
-    "resourcesListMs": 0.0007499999992433004
+    "connectMs": 957.3290410000009,
+    "toolsListMs": 8.349417000001267,
+    "promptsListMs": 0.001374999999825377,
+    "resourcesListMs": 0.000499999998282874
   },
   "runtimeProfile": {
     "egress": [
@@ -4050,7 +4050,7 @@
         "source": "description_analysis"
       }
     ],
-    "analyzedAt": "2026-07-12T23:44:25.852Z",
+    "analyzedAt": "2026-07-15T22:33:43.769Z",
     "confidence": "high"
   }
 }

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

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-12T23:44:24.930Z
+Generated at 2026-07-15T22:33:42.802Z
 
 ## Target and Environment Metadata
 
@@ -98,7 +98,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:25.852Z_
+_Analyzed at 2026-07-15T22:33:43.769Z_
 
 ## Regressions and Recoveries
 
@@ -108,15 +108,15 @@ _Use the `diff` command against another run artifact to classify regressions and
 
 | Focus | Check | Status | Duration (ms) | Message |
 | --- | --- | --- | --- | --- |
-| healthy | tools | pass | 7.68 | Advertised capability responded with the minimal expected shape (26 items). |
-| review | conformance | partial | 2.61 | 6/7 conformance checks passed, 1 failed. |
-| review | runtime-profile | partial | 0.44 | Detected 21 potential egress target(s) and 16 potential state mutation(s) with high confidence. |
-| review | schema-quality | partial | 0.99 | Found 147 quality finding(s) across 26 item(s): 0 warnings, 147 info. |
+| healthy | tools | pass | 8.35 | Advertised capability responded with the minimal expected shape (26 items). |
+| review | conformance | partial | 2.92 | 6/7 conformance checks passed, 1 failed. |
+| review | runtime-profile | partial | 0.41 | Detected 21 potential egress target(s) and 16 potential state mutation(s) with high confidence. |
+| review | schema-quality | partial | 1.02 | Found 147 quality finding(s) across 26 item(s): 0 warnings, 147 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. |
-| act now | attack-sim | fail | 1.88 | Safe attack simulation found 9 finding(s): 1 high, 8 medium, 0 low. |
-| act now | security | fail | 1.06 | Found 1 security finding(s): 1 high, 0 medium, 0 low. |
-| act now | security-lite | fail | 0.40 | Found 1 security finding(s): 1 high, 0 medium, 0 low. |
+| act now | attack-sim | fail | 1.70 | Safe attack simulation found 9 finding(s): 1 high, 8 medium, 0 low. |
+| act now | security | fail | 1.07 | Found 1 security finding(s): 1 high, 0 medium, 0 low. |
+| act now | security-lite | fail | 0.42 | Found 1 security finding(s): 1 high, 0 medium, 0 low. |
 
 ## Evidence Snippets
 
@@ -239,5 +239,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-12T234424930Z_964a3213`
+- Run ID: `run_2026-07-15T223342802Z_482400a3`
 - Gate: `fail`

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

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-15T223402661Z_7e29b8a7",
+  "createdAt": "2026-07-15T22:34:02.661Z",
+  "toolVersion": "1.32.1",
+  "target": {
+    "targetId": "flight-server",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "flight-mcp-server"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "flight-mcp-server",
+      "purpose": "mcp-safety-index",
+      "riskClass": "Travel booking API access",
+      "failureClass": "Flight search boundary",
+      "whyItMatters": "Flight MCP servers search, compare, and book flights through airline APIs — agents with booking access need payment and itinerary confirmation boundaries."
+    }
+  },
+  "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 `flight-server`.\nCommand: npx -y flight-mcp-server\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- at runServer (file:///Users/williamweishuhn/.npm/_npx/0492f3c9bc39e9d7/node_modules/flight-mcp-server/dist/index.js:12:24)\n- at file:///Users/williamweishuhn/.npm/_npx/0492f3c9bc39e9d7/node_modules/flight-mcp-server/dist/index.js:26:1\n- at ModuleJob.run (node:internal/modules/esm/module_job:343:25)\n- at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:665:26)\n- at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:117:5)"
+}

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

@@ -0,0 +1,106 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:34:02.661Z
+
+## Target and Environment Metadata
+
+- Target: `flight-server`
+- Adapter: `local-process`
+- Command: `npx -y flight-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 `flight-server`.
+Command: npx -y flight-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 runServer (file:///Users/williamweishuhn/.npm/_npx/0492f3c9bc39e9d7/node_modules/flight-mcp-server/dist/index.js:12:24)
+- at file:///Users/williamweishuhn/.npm/_npx/0492f3c9bc39e9d7/node_modules/flight-mcp-server/dist/index.js:26:1
+- 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-15T223402661Z_7e29b8a7`
+- Gate: `fail`

package/docs/safety-index/artifacts/foodpanda-pakistan-mcp.json

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-15T223601442Z_a60172b9",
+  "createdAt": "2026-07-15T22:36:01.442Z",
+  "toolVersion": "1.32.1",
+  "target": {
+    "targetId": "foodpanda-pakistan-mcp",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "foodpanda-pakistan-mcp"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "foodpanda-pakistan-mcp",
+      "purpose": "mcp-safety-index",
+      "riskClass": "Pakistani food delivery platform API access",
+      "failureClass": "Order/restaurant/delivery boundary",
+      "whyItMatters": "Foodpanda is Pakistan's largest food delivery platform covering all major cities. MCP servers exposing order management, restaurant data, and delivery tracking handle real-time logistics and payment data for millions of users."
+    }
+  },
+  "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 `foodpanda-pakistan-mcp`.\nCommand: npx -y foodpanda-pakistan-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  'foodpanda-pakistan-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_36_01_517Z-debug-0.log"
+}

package/docs/safety-index/artifacts/foodpanda-pakistan-mcp.md

@@ -0,0 +1,106 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:36:01.442Z
+
+## Target and Environment Metadata
+
+- Target: `foodpanda-pakistan-mcp`
+- Adapter: `local-process`
+- Command: `npx -y foodpanda-pakistan-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 `foodpanda-pakistan-mcp`.
+Command: npx -y foodpanda-pakistan-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  'foodpanda-pakistan-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_36_01_517Z-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-15T223601442Z_a60172b9`
+- Gate: `fail`

package/docs/safety-index/artifacts/gcp-mcp-server.json

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-15T223451316Z_f7d490a7",
+  "createdAt": "2026-07-15T22:34:51.316Z",
+  "toolVersion": "1.32.1",
+  "target": {
+    "targetId": "gcp-mcp-server",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "mcp-server-gcp"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "mcp-server-gcp",
+      "purpose": "mcp-safety-index",
+      "riskClass": "Cloud infrastructure control",
+      "failureClass": "GCP service boundary",
+      "whyItMatters": "GCP MCP servers can interact with Compute Engine, Cloud Storage, BigQuery, and other GCP services — broad cloud control surface."
+    }
+  },
+  "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 `gcp-mcp-server`.\nCommand: npx -y mcp-server-gcp\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_34_51_384Z-debug-0.log"
+}