@kryptosai/mcp-observatory 1.31.0 → 1.32.1

package/docs/safety-index/artifacts/sequential-thinking-server.json

@@ -2,9 +2,9 @@
   "artifactType": "run",
   "schemaVersion": "1.0.0",
   "gate": "pass",
-  "runId": "run_2026-07-06T194946140Z_d608f553",
-  "createdAt": "2026-07-06T19:49:46.140Z",
-  "toolVersion": "0.28.0",
+  "runId": "run_2026-07-12T234354820Z_c1f1096e",
+  "createdAt": "2026-07-12T23:43:54.820Z",
+  "toolVersion": "1.31.0",
   "target": {
     "targetId": "sequential-thinking-server",
     "adapter": "local-process",
@@ -29,8 +29,8 @@
     "nodeVersion": "v22.22.1"
   },
   "summary": {
-    "total": 8,
-    "pass": 6,
+    "total": 9,
+    "pass": 7,
     "fail": 0,
     "partial": 0,
     "unsupported": 2,
@@ -43,7 +43,7 @@
       "id": "tools",
       "capability": "tools",
       "status": "pass",
-      "durationMs": 3.737249999999676,
+      "durationMs": 4.1571249999997235,
       "message": "Advertised capability responded with the minimal expected shape (1 item).",
       "evidence": [
         {
@@ -122,7 +122,7 @@
       "id": "prompts",
       "capability": "prompts",
       "status": "unsupported",
-      "durationMs": 0.00408400000014808,
+      "durationMs": 0.0039999999999054126,
       "message": "Prompts are not advertised by the target.",
       "evidence": [
         {
@@ -138,7 +138,7 @@
       "id": "resources",
       "capability": "resources",
       "status": "unsupported",
-      "durationMs": 0.0015830000002097222,
+      "durationMs": 0.0014999999998508429,
       "message": "Resources are not advertised by the target.",
       "evidence": [
         {
@@ -154,7 +154,7 @@
       "id": "security-lite",
       "capability": "security-lite",
       "status": "pass",
-      "durationMs": 0.0753340000001117,
+      "durationMs": 0.02804199999991397,
       "message": "No security issues detected (lightweight scan).",
       "evidence": [
         {
@@ -166,11 +166,40 @@
         }
       ]
     },
+    {
+      "id": "runtime-profile",
+      "capability": "runtime-profile",
+      "status": "pass",
+      "durationMs": 0.07287500000029468,
+      "message": "Detected 0 potential egress target(s) and 1 potential state mutation(s) with low confidence.",
+      "evidence": [
+        {
+          "endpoint": "runtime-profile/analyze",
+          "advertised": true,
+          "responded": true,
+          "minimalShapePresent": true,
+          "itemCount": 1,
+          "diagnostics": [
+            "Egress entries: 0",
+            "State mutations: 1",
+            "Confidence: medium"
+          ],
+          "findings": [
+            {
+              "resource": "filesystem",
+              "operation": "write",
+              "scope": "working_directory",
+              "source": "description_analysis"
+            }
+          ]
+        }
+      ]
+    },
     {
       "id": "conformance",
       "capability": "conformance",
       "status": "pass",
-      "durationMs": 1.5115419999997357,
+      "durationMs": 1.5781660000002375,
       "message": "All 7 conformance checks passed.",
       "evidence": [
         {
@@ -196,7 +225,7 @@
       "id": "schema-quality",
       "capability": "schema-quality",
       "status": "pass",
-      "durationMs": 0.8508339999998498,
+      "durationMs": 0.8027910000000702,
       "message": "All 1 item(s) have good schema quality.",
       "evidence": [
         {
@@ -213,7 +242,7 @@
       "id": "security",
       "capability": "security",
       "status": "pass",
-      "durationMs": 0.908542000000125,
+      "durationMs": 0.8892080000000533,
       "message": "No security issues detected.",
       "evidence": [
         {
@@ -229,7 +258,7 @@
       "id": "attack-sim",
       "capability": "attack-sim",
       "status": "pass",
-      "durationMs": 0.819166000000223,
+      "durationMs": 0.8314170000003287,
       "message": "Safe attack simulation found no high-risk MCP attack-readiness findings.",
       "evidence": [
         {
@@ -288,16 +317,28 @@
         "weight": 0.1,
         "score": 100,
         "details": [
-          "Connect: 614ms",
+          "Connect: 844ms",
           "p95 latency: 4ms (3 operations)"
         ]
       }
     ]
   },
   "performanceMetrics": {
-    "connectMs": 614.4627080000002,
-    "toolsListMs": 3.737249999999676,
-    "promptsListMs": 0.00408400000014808,
-    "resourcesListMs": 0.0015830000002097222
+    "connectMs": 843.9233340000003,
+    "toolsListMs": 4.1571249999997235,
+    "promptsListMs": 0.0039999999999054126,
+    "resourcesListMs": 0.0014999999998508429
+  },
+  "runtimeProfile": {
+    "stateMutations": [
+      {
+        "resource": "filesystem",
+        "operation": "write",
+        "scope": "working_directory",
+        "source": "description_analysis"
+      }
+    ],
+    "analyzedAt": "2026-07-12T23:43:55.670Z",
+    "confidence": "medium"
   }
 }

package/docs/safety-index/artifacts/sequential-thinking-server.md

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-06T19:49:46.140Z
+Generated at 2026-07-12T23:43:54.820Z
 
 ## Target and Environment Metadata
 
@@ -25,7 +25,7 @@ Generated at 2026-07-06T19:49:46.140Z
 
 | Gate | Total | Pass | Fail | Partial | Unsupported | Flaky | Skipped |
 | --- | --- | --- | --- | --- | --- | --- | --- |
-| pass | 8 | 6 | 0 | 0 | 2 | 0 | 0 |
+| pass | 9 | 7 | 0 | 0 | 2 | 0 | 0 |
 
 ## At a Glance
 
@@ -39,6 +39,25 @@ Generated at 2026-07-06T19:49:46.140Z
 - Suggested next step: Confirm that unsupported capabilities are intentional for this target: prompts, resources.
 - 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 performed (see security findings)
+- ℹ️ destructive_payloads: Destructive payloads were not attempted (safe-mode only)
+
+## Runtime Profile
+
+### State Mutations
+
+The following state-modifying operations were identified from tool schemas:
+
+| Resource | Operation | Scope | Source |
+| --- | --- | --- | --- |
+| filesystem | write | working_directory | description_analysis |
+
+_Analyzed at 2026-07-12T23:43:55.670Z_
+
 ## Regressions and Recoveries
 
 _Use the `diff` command against another run artifact to classify regressions and recoveries over time._
@@ -47,12 +66,13 @@ _Use the `diff` command against another run artifact to classify regressions and
 
 | Focus | Check | Status | Duration (ms) | Message |
 | --- | --- | --- | --- | --- |
-| healthy | attack-sim | pass | 0.82 | Safe attack simulation found no high-risk MCP attack-readiness findings. |
-| healthy | conformance | pass | 1.51 | All 7 conformance checks passed. |
-| healthy | schema-quality | pass | 0.85 | All 1 item(s) have good schema quality. |
-| healthy | security | pass | 0.91 | No security issues detected. |
-| healthy | security-lite | pass | 0.08 | No security issues detected (lightweight scan). |
-| healthy | tools | pass | 3.74 | Advertised capability responded with the minimal expected shape (1 item). |
+| healthy | attack-sim | pass | 0.83 | Safe attack simulation found no high-risk MCP attack-readiness findings. |
+| healthy | conformance | pass | 1.58 | All 7 conformance checks passed. |
+| healthy | runtime-profile | pass | 0.07 | Detected 0 potential egress target(s) and 1 potential state mutation(s) with low confidence. |
+| healthy | schema-quality | pass | 0.80 | All 1 item(s) have good schema quality. |
+| healthy | security | pass | 0.89 | No security issues detected. |
+| healthy | security-lite | pass | 0.03 | No security issues detected (lightweight scan). |
+| healthy | tools | pass | 4.16 | Advertised capability responded with the minimal expected shape (1 item). |
 | 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. |
 
@@ -82,6 +102,18 @@ Summary: All 7 conformance checks passed.
   - Identifiers: none
   - Diagnostics: [pass] capabilities-present: Server returned capabilities object., [pass] server-info: Server provided initialization info., [pass] tools-capability-match: tools/list returned 1 tool(s). (+4 more)
 
+### runtime-profile — pass
+
+Summary: Detected 0 potential egress target(s) and 1 potential state mutation(s) with low confidence.
+
+- Endpoint: `runtime-profile/analyze`
+  - Advertised: `true`
+  - Responded: `true`
+  - Minimal shape present: `true`
+  - Item count: `1`
+  - Identifiers: none
+  - Diagnostics: Egress entries: 0, State mutations: 1, Confidence: medium
+
 ### schema-quality — pass
 
 Summary: All 1 item(s) have good schema quality.
@@ -165,5 +197,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-06T194946140Z_d608f553`
+- Run ID: `run_2026-07-12T234354820Z_c1f1096e`
 - Gate: `pass`

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

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-12T234417152Z_b9951b3e",
+  "createdAt": "2026-07-12T23:44:17.152Z",
+  "toolVersion": "1.31.0",
+  "target": {
+    "targetId": "slack-server",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "@modelcontextprotocol/server-slack"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "@modelcontextprotocol/server-slack",
+      "purpose": "mcp-safety-index",
+      "riskClass": "Messaging platform access",
+      "failureClass": "Message/channel boundary",
+      "whyItMatters": "Slack MCP servers can expose channel history, message posting, and workspace search capabilities to agents."
+    }
+  },
+  "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 `slack-server`.\nCommand: npx -y @modelcontextprotocol/server-slack\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- Please set SLACK_BOT_TOKEN and SLACK_TEAM_ID environment variables"
+}

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

@@ -0,0 +1,102 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-12T23:44:17.152Z
+
+## Target and Environment Metadata
+
+- Target: `slack-server`
+- Adapter: `local-process`
+- Command: `npx -y @modelcontextprotocol/server-slack`
+- 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 `slack-server`.
+Command: npx -y @modelcontextprotocol/server-slack
+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:
+- Please set SLACK_BOT_TOKEN and SLACK_TEAM_ID environment variables
+```
+
+## 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-12T234417152Z_b9951b3e`
+- Gate: `fail`

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

@@ -0,0 +1,67 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-12T234430725Z_502b9b31",
+  "createdAt": "2026-07-12T23:44:30.725Z",
+  "toolVersion": "1.31.0",
+  "target": {
+    "targetId": "sqlite-server",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "@modelcontextprotocol/server-sqlite",
+      "/tmp/test.db"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "@modelcontextprotocol/server-sqlite",
+      "purpose": "mcp-safety-index",
+      "riskClass": "Local database mutation",
+      "failureClass": "SQLite file boundary",
+      "whyItMatters": "SQLite MCP servers can grant agents read/write/query access to local database files with SQL execution capabilities."
+    }
+  },
+  "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 `sqlite-server`.\nCommand: npx -y @modelcontextprotocol/server-sqlite /tmp/test.db\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-sqlite@*' 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_30_791Z-debug-0.log"
+}

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

@@ -0,0 +1,106 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-12T23:44:30.725Z
+
+## Target and Environment Metadata
+
+- Target: `sqlite-server`
+- Adapter: `local-process`
+- Command: `npx -y @modelcontextprotocol/server-sqlite /tmp/test.db`
+- 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 `sqlite-server`.
+Command: npx -y @modelcontextprotocol/server-sqlite /tmp/test.db
+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  '@modelcontextprotocol/server-sqlite@*' 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-12T23_44_30_791Z-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-12T234430725Z_502b9b31`
+- Gate: `fail`

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

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-12T234421042Z_9da69382",
+  "createdAt": "2026-07-12T23:44:21.042Z",
+  "toolVersion": "1.31.0",
+  "target": {
+    "targetId": "stripe-server",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "@stripe/mcp"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "@stripe/mcp",
+      "purpose": "mcp-safety-index",
+      "riskClass": "Payment API boundary",
+      "failureClass": "Financial transaction tool boundary",
+      "whyItMatters": "Stripe tools can create customers, process payments, and manage subscriptions — financial mutation surfaces that need visible 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 `stripe-server`.\nCommand: npx -y @stripe/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- at Module._load (node:internal/modules/cjs/loader:1263:12)\n- at TracingChannel.traceSync (node:diagnostics_channel:328:14)\n- at wrapModuleLoad (node:internal/modules/cjs/loader:237:24)\n- at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5)\n- Node.js v22.22.1"
+}