@kryptosai/mcp-observatory 1.32.1 → 1.33.0

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

@@ -0,0 +1,106 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:33:55.661Z
+
+## Target and Environment Metadata
+
+- Target: `alpaca-server`
+- Adapter: `local-process`
+- Command: `npx -y @alpacahq/alpaca-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 `alpaca-server`.
+Command: npx -y @alpacahq/alpaca-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:
+- npm error 404  '@alpacahq/alpaca-mcp-server@*' 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_33_55_730Z-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-15T223355661Z_c005bfef`
+- Gate: `fail`

package/docs/safety-index/artifacts/antv-chart-server.json

@@ -2,9 +2,9 @@
   "artifactType": "run",
   "schemaVersion": "1.0.0",
   "gate": "pass",
-  "runId": "run_2026-07-12T234411970Z_ecbb3721",
-  "createdAt": "2026-07-12T23:44:11.970Z",
-  "toolVersion": "1.31.0",
+  "runId": "run_2026-07-15T223332070Z_010deadc",
+  "createdAt": "2026-07-15T22:33:32.070Z",
+  "toolVersion": "1.32.1",
   "target": {
     "targetId": "antv-chart-server",
     "adapter": "local-process",
@@ -43,7 +43,7 @@
       "id": "tools",
       "capability": "tools",
       "status": "pass",
-      "durationMs": 1.6119160000016564,
+      "durationMs": 1.573499999998603,
       "message": "Advertised capability responded with the minimal expected shape (27 items).",
       "evidence": [
         {
@@ -82,9 +82,9 @@
             "generate_spreadsheet"
           ],
           "diagnostics": [
-            "[MCP-Server-Chart] 2026-07-12T23:44:12.937Z ℹ️  setting up tool handlers...",
-            "[MCP-Server-Chart] 2026-07-12T23:44:12.938Z ℹ️  tool handlers set up",
-            "[MCP-Server-Chart] 2026-07-12T23:44:12.939Z ✅ Stdio MCP Server started"
+            "[MCP-Server-Chart] 2026-07-15T22:33:32.972Z ℹ️  setting up tool handlers...",
+            "[MCP-Server-Chart] 2026-07-15T22:33:32.973Z ℹ️  tool handlers set up",
+            "[MCP-Server-Chart] 2026-07-15T22:33:32.974Z ✅ Stdio MCP Server started"
           ],
           "schemas": {
             "generate_area_chart": {
@@ -2602,7 +2602,7 @@
       "id": "prompts",
       "capability": "prompts",
       "status": "unsupported",
-      "durationMs": 0.0010000000002037268,
+      "durationMs": 0.0007499999992433004,
       "message": "Prompts are not advertised by the target.",
       "evidence": [
         {
@@ -2618,7 +2618,7 @@
       "id": "resources",
       "capability": "resources",
       "status": "unsupported",
-      "durationMs": 0.0027079999999841675,
+      "durationMs": 0.0025409999980183784,
       "message": "Resources are not advertised by the target.",
       "evidence": [
         {
@@ -2634,7 +2634,7 @@
       "id": "security-lite",
       "capability": "security-lite",
       "status": "pass",
-      "durationMs": 0.07620899999892572,
+      "durationMs": 0.06920800000079907,
       "message": "No security issues detected (lightweight scan).",
       "evidence": [
         {
@@ -2650,7 +2650,7 @@
       "id": "runtime-profile",
       "capability": "runtime-profile",
       "status": "pass",
-      "durationMs": 0.40625,
+      "durationMs": 0.3900419999990845,
       "message": "Detected 0 potential egress target(s) and 117 potential state mutation(s) with low confidence.",
       "evidence": [
         {
@@ -3375,7 +3375,7 @@
       "id": "conformance",
       "capability": "conformance",
       "status": "pass",
-      "durationMs": 1.1692079999993439,
+      "durationMs": 1.0987090000016906,
       "message": "All 7 conformance checks passed.",
       "evidence": [
         {
@@ -3401,7 +3401,7 @@
       "id": "schema-quality",
       "capability": "schema-quality",
       "status": "pass",
-      "durationMs": 0.7347090000002936,
+      "durationMs": 1.2000410000000556,
       "message": "All 27 item(s) have good schema quality.",
       "evidence": [
         {
@@ -3418,7 +3418,7 @@
       "id": "security",
       "capability": "security",
       "status": "pass",
-      "durationMs": 1.331332999998267,
+      "durationMs": 0.7256249999991269,
       "message": "No security issues detected.",
       "evidence": [
         {
@@ -3434,7 +3434,7 @@
       "id": "attack-sim",
       "capability": "attack-sim",
       "status": "pass",
-      "durationMs": 1.6176249999989523,
+      "durationMs": 1.6307079999969574,
       "message": "Safe attack simulation found no high-risk MCP attack-readiness findings.",
       "evidence": [
         {
@@ -3493,17 +3493,17 @@
         "weight": 0.1,
         "score": 100,
         "details": [
-          "Connect: 971ms",
+          "Connect: 907ms",
           "p95 latency: 2ms (3 operations)"
         ]
       }
     ]
   },
   "performanceMetrics": {
-    "connectMs": 971.2009170000019,
-    "toolsListMs": 1.6119160000016564,
-    "promptsListMs": 0.0010000000002037268,
-    "resourcesListMs": 0.0027079999999841675
+    "connectMs": 906.5344579999983,
+    "toolsListMs": 1.573499999998603,
+    "promptsListMs": 0.0007499999992433004,
+    "resourcesListMs": 0.0025409999980183784
   },
   "runtimeProfile": {
     "stateMutations": [
@@ -4210,7 +4210,7 @@
         "source": "description_analysis"
       }
     ],
-    "analyzedAt": "2026-07-12T23:44:12.944Z",
+    "analyzedAt": "2026-07-15T22:33:32.979Z",
     "confidence": "medium"
   }
 }

package/docs/safety-index/artifacts/antv-chart-server.md

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-12T23:44:11.970Z
+Generated at 2026-07-15T22:33:32.070Z
 
 ## Target and Environment Metadata
 
@@ -170,7 +170,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:12.944Z_
+_Analyzed at 2026-07-15T22:33:32.979Z_
 
 ## Regressions and Recoveries
 
@@ -180,13 +180,13 @@ _Use the `diff` command against another run artifact to classify regressions and
 
 | Focus | Check | Status | Duration (ms) | Message |
 | --- | --- | --- | --- | --- |
-| healthy | attack-sim | pass | 1.62 | Safe attack simulation found no high-risk MCP attack-readiness findings. |
-| healthy | conformance | pass | 1.17 | All 7 conformance checks passed. |
-| healthy | runtime-profile | pass | 0.41 | Detected 0 potential egress target(s) and 117 potential state mutation(s) with low confidence. |
-| healthy | schema-quality | pass | 0.73 | All 27 item(s) have good schema quality. |
-| healthy | security | pass | 1.33 | No security issues detected. |
-| healthy | security-lite | pass | 0.08 | No security issues detected (lightweight scan). |
-| healthy | tools | pass | 1.61 | Advertised capability responded with the minimal expected shape (27 items). |
+| healthy | attack-sim | pass | 1.63 | Safe attack simulation found no high-risk MCP attack-readiness findings. |
+| healthy | conformance | pass | 1.10 | All 7 conformance checks passed. |
+| healthy | runtime-profile | pass | 0.39 | Detected 0 potential egress target(s) and 117 potential state mutation(s) with low confidence. |
+| healthy | schema-quality | pass | 1.20 | All 27 item(s) have good schema quality. |
+| healthy | security | pass | 0.73 | No security issues detected. |
+| healthy | security-lite | pass | 0.07 | No security issues detected (lightweight scan). |
+| healthy | tools | pass | 1.57 | Advertised capability responded with the minimal expected shape (27 items). |
 | 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. |
 
@@ -274,7 +274,7 @@ Summary: Advertised capability responded with the minimal expected shape (27 ite
   - Minimal shape present: `true`
   - Item count: `27`
   - Identifiers: generate_area_chart, generate_bar_chart, generate_boxplot_chart, generate_column_chart, generate_district_map (+22 more)
-  - Diagnostics: [MCP-Server-Chart] 2026-07-12T23:44:12.937Z ℹ️  setting up tool handlers..., [MCP-Server-Chart] 2026-07-12T23:44:12.938Z ℹ️  tool handlers set up, [MCP-Server-Chart] 2026-07-12T23:44:12.939Z ✅ Stdio MCP Server started
+  - Diagnostics: [MCP-Server-Chart] 2026-07-15T22:33:32.972Z ℹ️  setting up tool handlers..., [MCP-Server-Chart] 2026-07-15T22:33:32.973Z ℹ️  tool handlers set up, [MCP-Server-Chart] 2026-07-15T22:33:32.974Z ✅ Stdio MCP Server started
 
 ### prompts — unsupported
 
@@ -311,5 +311,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-12T234411970Z_ecbb3721`
+- Run ID: `run_2026-07-15T223332070Z_010deadc`
 - Gate: `pass`

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

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-15T223440099Z_19e65c23",
+  "createdAt": "2026-07-15T22:34:40.099Z",
+  "toolVersion": "1.32.1",
+  "target": {
+    "targetId": "apify-mcp-server",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "@apify/actors-mcp-server"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "@apify/actors-mcp-server",
+      "purpose": "mcp-safety-index",
+      "riskClass": "Web scraping and data extraction",
+      "failureClass": "Actor/scraping/data boundary",
+      "whyItMatters": "Apify MCP servers can trigger web scraping actors, extract data from websites, and manage scraping infrastructure — agents could scrape any accessible web content."
+    }
+  },
+  "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 `apify-mcp-server`.\nCommand: npx -y @apify/actors-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- \u001b[31mERROR\u001b[39m APIFY_TOKEN is required but not set in the environment variables or in ~/.apify/auth.json\n- APIFY_TOKEN is required but not set in the environment variables or in ~/.apify/auth.json"
+}

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

@@ -0,0 +1,103 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:34:40.099Z
+
+## Target and Environment Metadata
+
+- Target: `apify-mcp-server`
+- Adapter: `local-process`
+- Command: `npx -y @apify/actors-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 `apify-mcp-server`.
+Command: npx -y @apify/actors-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:
+- ERROR APIFY_TOKEN is required but not set in the environment variables or in ~/.apify/auth.json
+- APIFY_TOKEN is required but not set in the environment variables or in ~/.apify/auth.json
+```
+
+## 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-15T223440099Z_19e65c23`
+- Gate: `fail`

package/docs/safety-index/artifacts/apple-music-server.json

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-15T223406137Z_743f0e6f",
+  "createdAt": "2026-07-15T22:34:06.137Z",
+  "toolVersion": "1.32.1",
+  "target": {
+    "targetId": "apple-music-server",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "apple-music-mcp"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "apple-music-mcp",
+      "purpose": "mcp-safety-index",
+      "riskClass": "Music streaming API access",
+      "failureClass": "Music library boundary",
+      "whyItMatters": "Apple Music MCP servers can search catalog, manage library, and access recommendations — agents with music access need media rights 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 `apple-music-server`.\nCommand: npx -y apple-music-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- env: bun: No such file or directory"
+}

package/docs/safety-index/artifacts/apple-music-server.md

@@ -0,0 +1,102 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:34:06.137Z
+
+## Target and Environment Metadata
+
+- Target: `apple-music-server`
+- Adapter: `local-process`
+- Command: `npx -y apple-music-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 `apple-music-server`.
+Command: npx -y apple-music-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:
+- env: bun: No such file or directory
+```
+
+## 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-15T223406137Z_743f0e6f`
+- Gate: `fail`