@kryptosai/mcp-observatory 1.32.1 → 1.33.0

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

@@ -0,0 +1,103 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:34:51.316Z
+
+## Target and Environment Metadata
+
+- Target: `gcp-mcp-server`
+- Adapter: `local-process`
+- Command: `npx -y mcp-server-gcp`
+- 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 `gcp-mcp-server`.
+Command: npx -y mcp-server-gcp
+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 could not determine executable to run
+- 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
+```
+
+## 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-15T223451316Z_f7d490a7`
+- Gate: `fail`

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

@@ -2,9 +2,9 @@
   "artifactType": "run",
   "schemaVersion": "1.0.0",
   "gate": "pass",
-  "runId": "run_2026-07-12T234404127Z_20ace2e1",
-  "createdAt": "2026-07-12T23:44:04.127Z",
-  "toolVersion": "1.31.0",
+  "runId": "run_2026-07-15T223324164Z_9a89cc98",
+  "createdAt": "2026-07-15T22:33:24.164Z",
+  "toolVersion": "1.32.1",
   "target": {
     "targetId": "github-mcp-server",
     "adapter": "local-process",
@@ -43,7 +43,7 @@
       "id": "tools",
       "capability": "tools",
       "status": "pass",
-      "durationMs": 2.782208000000537,
+      "durationMs": 3.21929099999943,
       "message": "Advertised capability responded with the minimal expected shape (26 items).",
       "evidence": [
         {
@@ -1032,7 +1032,7 @@
       "id": "prompts",
       "capability": "prompts",
       "status": "unsupported",
-      "durationMs": 0.002125000000887667,
+      "durationMs": 0.001833000000260654,
       "message": "Prompts are not advertised by the target.",
       "evidence": [
         {
@@ -1048,7 +1048,7 @@
       "id": "resources",
       "capability": "resources",
       "status": "unsupported",
-      "durationMs": 0.0020000000004074536,
+      "durationMs": 0.0023330000003625173,
       "message": "Resources are not advertised by the target.",
       "evidence": [
         {
@@ -1064,7 +1064,7 @@
       "id": "security-lite",
       "capability": "security-lite",
       "status": "partial",
-      "durationMs": 0.06500000000050932,
+      "durationMs": 0.062334000000191736,
       "message": "Found 1 security finding(s): 0 high, 1 medium, 0 low.",
       "evidence": [
         {
@@ -1094,7 +1094,7 @@
       "id": "runtime-profile",
       "capability": "runtime-profile",
       "status": "partial",
-      "durationMs": 0.3124580000003334,
+      "durationMs": 0.2916669999995065,
       "message": "Detected 0 potential egress target(s) and 27 potential state mutation(s) with high confidence.",
       "evidence": [
         {
@@ -1279,7 +1279,7 @@
       "id": "conformance",
       "capability": "conformance",
       "status": "pass",
-      "durationMs": 1.012749999999869,
+      "durationMs": 1.4020839999993768,
       "message": "All 7 conformance checks passed.",
       "evidence": [
         {
@@ -1305,7 +1305,7 @@
       "id": "schema-quality",
       "capability": "schema-quality",
       "status": "partial",
-      "durationMs": 0.5399580000012065,
+      "durationMs": 0.8174589999998716,
       "message": "Found 51 quality finding(s) across 26 item(s): 0 warnings, 51 info.",
       "evidence": [
         {
@@ -1693,7 +1693,7 @@
       "id": "security",
       "capability": "security",
       "status": "partial",
-      "durationMs": 0.7721669999991718,
+      "durationMs": 0.769125000000713,
       "message": "Found 1 security finding(s): 0 high, 1 medium, 0 low.",
       "evidence": [
         {
@@ -1723,7 +1723,7 @@
       "id": "attack-sim",
       "capability": "attack-sim",
       "status": "partial",
-      "durationMs": 1.2275410000002012,
+      "durationMs": 1.0075829999987036,
       "message": "Safe attack simulation found 5 finding(s): 0 high, 5 medium, 0 low.",
       "evidence": [
         {
@@ -1877,17 +1877,17 @@
         "weight": 0.1,
         "score": 100,
         "details": [
-          "Connect: 765ms",
+          "Connect: 726ms",
           "p95 latency: 3ms (3 operations)"
         ]
       }
     ]
   },
   "performanceMetrics": {
-    "connectMs": 764.8195000000014,
-    "toolsListMs": 2.782208000000537,
-    "promptsListMs": 0.002125000000887667,
-    "resourcesListMs": 0.0020000000004074536
+    "connectMs": 725.5884580000002,
+    "toolsListMs": 3.21929099999943,
+    "promptsListMs": 0.001833000000260654,
+    "resourcesListMs": 0.0023330000003625173
   },
   "runtimeProfile": {
     "stateMutations": [
@@ -2054,7 +2054,7 @@
         "source": "description_analysis"
       }
     ],
-    "analyzedAt": "2026-07-12T23:44:04.897Z",
+    "analyzedAt": "2026-07-15T22:33:24.895Z",
     "confidence": "high"
   }
 }

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

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-12T23:44:04.127Z
+Generated at 2026-07-15T22:33:24.164Z
 
 ## Target and Environment Metadata
 
@@ -80,7 +80,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:04.897Z_
+_Analyzed at 2026-07-15T22:33:24.895Z_
 
 ## Regressions and Recoveries
 
@@ -90,13 +90,13 @@ _Use the `diff` command against another run artifact to classify regressions and
 
 | Focus | Check | Status | Duration (ms) | Message |
 | --- | --- | --- | --- | --- |
-| healthy | conformance | pass | 1.01 | All 7 conformance checks passed. |
-| healthy | tools | pass | 2.78 | Advertised capability responded with the minimal expected shape (26 items). |
-| review | attack-sim | partial | 1.23 | Safe attack simulation found 5 finding(s): 0 high, 5 medium, 0 low. |
-| review | runtime-profile | partial | 0.31 | Detected 0 potential egress target(s) and 27 potential state mutation(s) with high confidence. |
-| review | schema-quality | partial | 0.54 | Found 51 quality finding(s) across 26 item(s): 0 warnings, 51 info. |
+| healthy | conformance | pass | 1.40 | All 7 conformance checks passed. |
+| healthy | tools | pass | 3.22 | Advertised capability responded with the minimal expected shape (26 items). |
+| review | attack-sim | partial | 1.01 | Safe attack simulation found 5 finding(s): 0 high, 5 medium, 0 low. |
+| review | runtime-profile | partial | 0.29 | Detected 0 potential egress target(s) and 27 potential state mutation(s) with high confidence. |
+| review | schema-quality | partial | 0.82 | Found 51 quality finding(s) across 26 item(s): 0 warnings, 51 info. |
 | review | security | partial | 0.77 | Found 1 security finding(s): 0 high, 1 medium, 0 low. |
-| review | security-lite | partial | 0.07 | Found 1 security finding(s): 0 high, 1 medium, 0 low. |
+| review | security-lite | partial | 0.06 | Found 1 security finding(s): 0 high, 1 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. |
 
@@ -221,5 +221,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-12T234404127Z_20ace2e1`
+- Run ID: `run_2026-07-15T223324164Z_9a89cc98`
 - Gate: `pass`

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

@@ -2,9 +2,9 @@
   "artifactType": "run",
   "schemaVersion": "1.0.0",
   "gate": "fail",
-  "runId": "run_2026-07-12T234432356Z_5fb3b8bf",
-  "createdAt": "2026-07-12T23:44:32.356Z",
-  "toolVersion": "1.31.0",
+  "runId": "run_2026-07-15T223349920Z_3504d108",
+  "createdAt": "2026-07-15T22:33:49.920Z",
+  "toolVersion": "1.32.1",
   "target": {
     "targetId": "gitlab-server",
     "adapter": "local-process",
@@ -43,7 +43,7 @@
       "id": "tools",
       "capability": "tools",
       "status": "fail",
-      "durationMs": 1.0523330000069109,
+      "durationMs": 1.895250000001397,
       "message": "Advertised capability failed during tools/list: [\n  {\n    \"code\": \"invalid_value\",\n    \"values\": [\n      \"object\"\n    ],\n    \"path\": [\n      \"tools\",\n      0,\n      \"inputSchema\",\n      \"type\"\n    ],\n    \"message\": \"Invalid input: expected \\\"object\\\"\"\n  },\n  {\n    \"code\": \"invalid_value\",\n    \"values\": [\n      \"object\"\n    ],\n    \"path\": [\n      \"tools\",\n      1,\n      \"inputSchema\",\n      \"type\"\n    ],\n    \"message\": \"Invalid input: expected \\\"object\\\"\"\n  },\n  {\n    \"code\": \"invalid_value\",\n    \"values\": [\n      \"object\"\n    ],\n    \"path\": [\n      \"tools\",\n      2,\n      \"inputSchema\",\n      \"type\"\n    ],\n    \"message\": \"Invalid input: expected \\\"object\\\"\"\n  },\n  {\n    \"code\": \"invalid_value\",\n    \"values\": [\n      \"object\"\n    ],\n    \"path\": [\n      \"tools\",\n      3,\n      \"inputSchema\",\n      \"type\"\n    ],\n    \"message\": \"Invalid input: expected \\\"object\\\"\"\n  },\n  {\n    \"code\": \"invalid_value\",\n    \"values\": [\n      \"object\"\n    ],\n    \"path\": [\n      \"tools\",\n      4,\n      \"inputSchema\",\n      \"type\"\n    ],\n    \"message\": \"Invalid input: expected \\\"object\\\"\"\n  },\n  {\n    \"code\": \"invalid_value\",\n    \"values\": [\n      \"object\"\n    ],\n    \"path\": [\n      \"tools\",\n      5,\n      \"inputSchema\",\n      \"type\"\n    ],\n    \"message\": \"Invalid input: expected \\\"object\\\"\"\n  },\n  {\n    \"code\": \"invalid_value\",\n    \"values\": [\n      \"object\"\n    ],\n    \"path\": [\n      \"tools\",\n      6,\n      \"inputSchema\",\n      \"type\"\n    ],\n    \"message\": \"Invalid input: expected \\\"object\\\"\"\n  },\n  {\n    \"code\": \"invalid_value\",\n    \"values\": [\n      \"object\"\n    ],\n    \"path\": [\n      \"tools\",\n      7,\n      \"inputSchema\",\n      \"type\"\n    ],\n    \"message\": \"Invalid input: expected \\\"object\\\"\"\n  },\n  {\n    \"code\": \"invalid_value\",\n    \"values\": [\n      \"object\"\n    ],\n    \"path\": [\n      \"tools\",\n      8,\n      \"inputSchema\",\n      \"type\"\n    ],\n    \"message\": \"Invalid input: expected \\\"object\\\"\"\n  }\n]",
       "evidence": [
         {
@@ -62,7 +62,7 @@
       "id": "prompts",
       "capability": "prompts",
       "status": "unsupported",
-      "durationMs": 0.0006250000005820766,
+      "durationMs": 0.0006659999999101274,
       "message": "Prompts are not advertised by the target.",
       "evidence": [
         {
@@ -78,7 +78,7 @@
       "id": "resources",
       "capability": "resources",
       "status": "unsupported",
-      "durationMs": 0.0004999999946448952,
+      "durationMs": 0.0004580000022542663,
       "message": "Resources are not advertised by the target.",
       "evidence": [
         {
@@ -94,7 +94,7 @@
       "id": "conformance",
       "capability": "conformance",
       "status": "partial",
-      "durationMs": 0.5679170000003069,
+      "durationMs": 0.5302920000031008,
       "message": "5/7 conformance checks passed, 2 failed.",
       "evidence": [
         {
@@ -123,7 +123,7 @@
       "id": "schema-quality",
       "capability": "schema-quality",
       "status": "pass",
-      "durationMs": 0.13045899999997346,
+      "durationMs": 0.12754199999471894,
       "message": "All 0 item(s) have good schema quality.",
       "evidence": [
         {
@@ -140,7 +140,7 @@
       "id": "security",
       "capability": "security",
       "status": "pass",
-      "durationMs": 0.25466700000106357,
+      "durationMs": 0.2620840000017779,
       "message": "No security issues detected.",
       "evidence": [
         {
@@ -156,7 +156,7 @@
       "id": "attack-sim",
       "capability": "attack-sim",
       "status": "pass",
-      "durationMs": 0.203125,
+      "durationMs": 0.21029099999577738,
       "message": "Safe attack simulation found no high-risk MCP attack-readiness findings.",
       "evidence": [
         {
@@ -214,16 +214,16 @@
         "weight": 0.1,
         "score": 100,
         "details": [
-          "Connect: 814ms",
-          "p95 latency: 1ms (3 operations)"
+          "Connect: 802ms",
+          "p95 latency: 2ms (3 operations)"
         ]
       }
     ]
   },
   "performanceMetrics": {
-    "connectMs": 814.0159159999967,
-    "toolsListMs": 1.0523330000069109,
-    "promptsListMs": 0.0006250000005820766,
-    "resourcesListMs": 0.0004999999946448952
+    "connectMs": 801.9415840000001,
+    "toolsListMs": 1.895250000001397,
+    "promptsListMs": 0.0006659999999101274,
+    "resourcesListMs": 0.0004580000022542663
   }
 }

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

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-12T23:44:32.356Z
+Generated at 2026-07-15T22:33:49.920Z
 
 ## Target and Environment Metadata
 
@@ -172,13 +172,13 @@ _Use the `diff` command against another run artifact to classify regressions and
 
 | Focus | Check | Status | Duration (ms) | Message |
 | --- | --- | --- | --- | --- |
-| healthy | attack-sim | pass | 0.20 | Safe attack simulation found no high-risk MCP attack-readiness findings. |
+| healthy | attack-sim | pass | 0.21 | Safe attack simulation found no high-risk MCP attack-readiness findings. |
 | healthy | schema-quality | pass | 0.13 | All 0 item(s) have good schema quality. |
-| healthy | security | pass | 0.25 | No security issues detected. |
-| review | conformance | partial | 0.57 | 5/7 conformance checks passed, 2 failed. |
+| healthy | security | pass | 0.26 | No security issues detected. |
+| review | conformance | partial | 0.53 | 5/7 conformance checks passed, 2 failed. |
 | 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 | tools | fail | 1.05 | Advertised capability failed during tools/list: [
+| act now | tools | fail | 1.90 | Advertised capability failed during tools/list: [
   {
     "code": "invalid_value",
     "values": [
@@ -749,5 +749,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-12T234432356Z_5fb3b8bf`
+- Run ID: `run_2026-07-15T223349920Z_3504d108`
 - Gate: `fail`

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

@@ -2,9 +2,9 @@
   "artifactType": "run",
   "schemaVersion": "1.0.0",
   "gate": "fail",
-  "runId": "run_2026-07-12T234433182Z_64b0f22c",
-  "createdAt": "2026-07-12T23:44:33.182Z",
-  "toolVersion": "1.31.0",
+  "runId": "run_2026-07-15T223350732Z_5313d000",
+  "createdAt": "2026-07-15T22:33:50.732Z",
+  "toolVersion": "1.32.1",
   "target": {
     "targetId": "gmail-server",
     "adapter": "local-process",
@@ -62,5 +62,5 @@
       "evidence": []
     }
   ],
-  "fatalError": "Could not establish a plain stdio MCP session for target `gmail-server`.\nCommand: npx -y @anthropic/mcp-server-gmail\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  '@anthropic/mcp-server-gmail@*' 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-12T23_44_33_249Z-debug-0.log"
+  "fatalError": "Could not establish a plain stdio MCP session for target `gmail-server`.\nCommand: npx -y @anthropic/mcp-server-gmail\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  '@anthropic/mcp-server-gmail@*' 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_33_50_802Z-debug-0.log"
 }

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

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-12T23:44:33.182Z
+Generated at 2026-07-15T22:33:50.732Z
 
 ## Target and Environment Metadata
 
@@ -60,7 +60,7 @@ Recent stderr:
 - 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-12T23_44_33_249Z-debug-0.log
+- npm error A complete log of this run can be found in: /Users/williamweishuhn/.npm/_logs/2026-07-15T22_33_50_802Z-debug-0.log
 ```
 
 ## Full Capability Status Table
@@ -102,5 +102,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-12T234433182Z_64b0f22c`
+- Run ID: `run_2026-07-15T223350732Z_5313d000`
 - Gate: `fail`

package/docs/safety-index/artifacts/google-calendar-server.json

@@ -2,9 +2,9 @@
   "artifactType": "run",
   "schemaVersion": "1.0.0",
   "gate": "fail",
-  "runId": "run_2026-07-12T234434571Z_4c1be932",
-  "createdAt": "2026-07-12T23:44:34.571Z",
-  "toolVersion": "1.31.0",
+  "runId": "run_2026-07-15T223351850Z_602adb4c",
+  "createdAt": "2026-07-15T22:33:51.850Z",
+  "toolVersion": "1.32.1",
   "target": {
     "targetId": "google-calendar-server",
     "adapter": "local-process",
@@ -62,5 +62,5 @@
       "evidence": []
     }
   ],
-  "fatalError": "Could not establish a plain stdio MCP session for target `google-calendar-server`.\nCommand: npx -y @anthropic/mcp-server-google-calendar\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  '@anthropic/mcp-server-google-calendar@*' 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-12T23_44_34_663Z-debug-0.log"
+  "fatalError": "Could not establish a plain stdio MCP session for target `google-calendar-server`.\nCommand: npx -y @anthropic/mcp-server-google-calendar\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  '@anthropic/mcp-server-google-calendar@*' 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_33_51_926Z-debug-0.log"
 }

package/docs/safety-index/artifacts/google-calendar-server.md

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-12T23:44:34.571Z
+Generated at 2026-07-15T22:33:51.850Z
 
 ## Target and Environment Metadata
 
@@ -60,7 +60,7 @@ Recent stderr:
 - 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-12T23_44_34_663Z-debug-0.log
+- npm error A complete log of this run can be found in: /Users/williamweishuhn/.npm/_logs/2026-07-15T22_33_51_926Z-debug-0.log
 ```
 
 ## Full Capability Status Table
@@ -102,5 +102,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-12T234434571Z_4c1be932`
+- Run ID: `run_2026-07-15T223351850Z_602adb4c`
 - Gate: `fail`

package/docs/safety-index/artifacts/google-drive-server.json

@@ -2,9 +2,9 @@
   "artifactType": "run",
   "schemaVersion": "1.0.0",
   "gate": "fail",
-  "runId": "run_2026-07-12T234418010Z_4cf2604f",
-  "createdAt": "2026-07-12T23:44:18.010Z",
-  "toolVersion": "1.31.0",
+  "runId": "run_2026-07-15T223337541Z_890c2e42",
+  "createdAt": "2026-07-15T22:33:37.541Z",
+  "toolVersion": "1.32.1",
   "target": {
     "targetId": "google-drive-server",
     "adapter": "local-process",
@@ -62,5 +62,5 @@
       "evidence": []
     }
   ],
-  "fatalError": "Could not establish a plain stdio MCP session for target `google-drive-server`.\nCommand: npx -y @modelcontextprotocol/server-google-drive\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  '@modelcontextprotocol/server-google-drive@*' 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-12T23_44_18_081Z-debug-0.log"
+  "fatalError": "Could not establish a plain stdio MCP session for target `google-drive-server`.\nCommand: npx -y @modelcontextprotocol/server-google-drive\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  '@modelcontextprotocol/server-google-drive@*' 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_33_37_608Z-debug-0.log"
 }

package/docs/safety-index/artifacts/google-drive-server.md

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-12T23:44:18.010Z
+Generated at 2026-07-15T22:33:37.541Z
 
 ## Target and Environment Metadata
 
@@ -60,7 +60,7 @@ Recent stderr:
 - 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-12T23_44_18_081Z-debug-0.log
+- npm error A complete log of this run can be found in: /Users/williamweishuhn/.npm/_logs/2026-07-15T22_33_37_608Z-debug-0.log
 ```
 
 ## Full Capability Status Table
@@ -102,5 +102,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-12T234418010Z_4cf2604f`
+- Run ID: `run_2026-07-15T223337541Z_890c2e42`
 - Gate: `fail`

package/docs/safety-index/artifacts/google-sheets-server.json

@@ -2,9 +2,9 @@
   "artifactType": "run",
   "schemaVersion": "1.0.0",
   "gate": "fail",
-  "runId": "run_2026-07-12T234434132Z_dd9ed2e5",
-  "createdAt": "2026-07-12T23:44:34.132Z",
-  "toolVersion": "1.31.0",
+  "runId": "run_2026-07-15T223351476Z_8b328f38",
+  "createdAt": "2026-07-15T22:33:51.476Z",
+  "toolVersion": "1.32.1",
   "target": {
     "targetId": "google-sheets-server",
     "adapter": "local-process",
@@ -62,5 +62,5 @@
       "evidence": []
     }
   ],
-  "fatalError": "Could not establish a plain stdio MCP session for target `google-sheets-server`.\nCommand: npx -y @anthropic/mcp-server-google-sheets\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  '@anthropic/mcp-server-google-sheets@*' 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-12T23_44_34_217Z-debug-0.log"
+  "fatalError": "Could not establish a plain stdio MCP session for target `google-sheets-server`.\nCommand: npx -y @anthropic/mcp-server-google-sheets\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  '@anthropic/mcp-server-google-sheets@*' 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_33_51_550Z-debug-0.log"
 }

package/docs/safety-index/artifacts/google-sheets-server.md

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-12T23:44:34.132Z
+Generated at 2026-07-15T22:33:51.476Z
 
 ## Target and Environment Metadata
 
@@ -60,7 +60,7 @@ Recent stderr:
 - 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-12T23_44_34_217Z-debug-0.log
+- npm error A complete log of this run can be found in: /Users/williamweishuhn/.npm/_logs/2026-07-15T22_33_51_550Z-debug-0.log
 ```
 
 ## Full Capability Status Table
@@ -102,5 +102,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-12T234434132Z_dd9ed2e5`
+- Run ID: `run_2026-07-15T223351476Z_8b328f38`
 - Gate: `fail`

package/docs/safety-index/artifacts/google-tasks-server.json

@@ -2,9 +2,9 @@
   "artifactType": "run",
   "schemaVersion": "1.0.0",
   "gate": "fail",
-  "runId": "run_2026-07-12T234435050Z_5916222a",
-  "createdAt": "2026-07-12T23:44:35.050Z",
-  "toolVersion": "1.31.0",
+  "runId": "run_2026-07-15T223352227Z_6f84b1e5",
+  "createdAt": "2026-07-15T22:33:52.227Z",
+  "toolVersion": "1.32.1",
   "target": {
     "targetId": "google-tasks-server",
     "adapter": "local-process",
@@ -62,5 +62,5 @@
       "evidence": []
     }
   ],
-  "fatalError": "Could not establish a plain stdio MCP session for target `google-tasks-server`.\nCommand: npx -y @anthropic/mcp-server-google-tasks\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  '@anthropic/mcp-server-google-tasks@*' 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-12T23_44_35_135Z-debug-0.log"
+  "fatalError": "Could not establish a plain stdio MCP session for target `google-tasks-server`.\nCommand: npx -y @anthropic/mcp-server-google-tasks\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  '@anthropic/mcp-server-google-tasks@*' 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_33_52_302Z-debug-0.log"
 }

package/docs/safety-index/artifacts/google-tasks-server.md

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-12T23:44:35.050Z
+Generated at 2026-07-15T22:33:52.227Z
 
 ## Target and Environment Metadata
 
@@ -60,7 +60,7 @@ Recent stderr:
 - 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-12T23_44_35_135Z-debug-0.log
+- npm error A complete log of this run can be found in: /Users/williamweishuhn/.npm/_logs/2026-07-15T22_33_52_302Z-debug-0.log
 ```
 
 ## Full Capability Status Table
@@ -102,5 +102,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-12T234435050Z_5916222a`
+- Run ID: `run_2026-07-15T223352227Z_6f84b1e5`
 - Gate: `fail`