@kryptosai/mcp-observatory 1.32.1 → 1.34.0

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

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-15T223455589Z_b69d6059",
+  "createdAt": "2026-07-15T22:34:55.589Z",
+  "toolVersion": "1.32.1",
+  "target": {
+    "targetId": "perplexity-mcp",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "perplexity-mcp"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "perplexity-mcp",
+      "purpose": "mcp-safety-index",
+      "riskClass": "AI-powered search access",
+      "failureClass": "Search result/LLM boundary",
+      "whyItMatters": "Perplexity MCP servers combine web search with LLM reasoning — agents can retrieve AI-generated answers that blend search results with model outputs."
+    }
+  },
+  "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 `perplexity-mcp`.\nCommand: npx -y perplexity-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 file:///Users/williamweishuhn/.npm/_npx/3ec903104d4a7191/node_modules/perplexity-mcp/build/index.js:107:28\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)\n- Node.js v22.22.1"
+}

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

@@ -0,0 +1,106 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:34:55.589Z
+
+## Target and Environment Metadata
+
+- Target: `perplexity-mcp`
+- Adapter: `local-process`
+- Command: `npx -y perplexity-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 `perplexity-mcp`.
+Command: npx -y perplexity-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:
+- at file:///Users/williamweishuhn/.npm/_npx/3ec903104d4a7191/node_modules/perplexity-mcp/build/index.js:107:28
+- 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)
+- Node.js v22.22.1
+```
+
+## 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-15T223455589Z_b69d6059`
+- Gate: `fail`

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

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-15T223549694Z_d5dcfc60",
+  "createdAt": "2026-07-15T22:35:49.694Z",
+  "toolVersion": "1.32.1",
+  "target": {
+    "targetId": "pims-mcp",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "pims-mcp"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "pims-mcp",
+      "purpose": "mcp-safety-index",
+      "riskClass": "Public hospital system API access",
+      "failureClass": "Patient record/hospital management boundary",
+      "whyItMatters": "PIMS (Pakistan Institute of Medical Sciences) is Islamabad's flagship tertiary-care teaching hospital serving millions. MCP servers accessing patient records, lab results, and hospital administration handle PHI and critical medical infrastructure data."
+    }
+  },
+  "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 `pims-mcp`.\nCommand: npx -y pims-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  'pims-mcp@*' is not in this registry.\n- npm error 404\n- npm error 404 Note that you can also install from a\n- npm error 404 tarball, folder, http url, or git url.\n- npm error A complete log of this run can be found in: /Users/williamweishuhn/.npm/_logs/2026-07-15T22_35_49_773Z-debug-0.log"
+}

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

@@ -0,0 +1,106 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:35:49.694Z
+
+## Target and Environment Metadata
+
+- Target: `pims-mcp`
+- Adapter: `local-process`
+- Command: `npx -y pims-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 `pims-mcp`.
+Command: npx -y pims-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  'pims-mcp@*' is not in this registry.
+- npm error 404
+- npm error 404 Note that you can also install from a
+- npm error 404 tarball, folder, http url, or git url.
+- npm error A complete log of this run can be found in: /Users/williamweishuhn/.npm/_logs/2026-07-15T22_35_49_773Z-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-15T223549694Z_d5dcfc60`
+- Gate: `fail`

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

@@ -2,9 +2,9 @@
   "artifactType": "run",
   "schemaVersion": "1.0.0",
   "gate": "fail",
-  "runId": "run_2026-07-12T234410399Z_1a4faea8",
-  "createdAt": "2026-07-12T23:44:10.399Z",
-  "toolVersion": "1.31.0",
+  "runId": "run_2026-07-17T003633428Z_a9fd4dd4",
+  "createdAt": "2026-07-17T00:36:33.428Z",
+  "toolVersion": "1.33.0",
   "target": {
     "targetId": "playwright-mcp-server",
     "adapter": "local-process",
@@ -43,7 +43,7 @@
       "id": "tools",
       "capability": "tools",
       "status": "pass",
-      "durationMs": 2.8462499999986903,
+      "durationMs": 2.7732919999998558,
       "message": "Advertised capability responded with the minimal expected shape (24 items).",
       "evidence": [
         {
@@ -667,7 +667,7 @@
       "id": "prompts",
       "capability": "prompts",
       "status": "unsupported",
-      "durationMs": 0.000915999997232575,
+      "durationMs": 0.0008340000003954628,
       "message": "Prompts are not advertised by the target.",
       "evidence": [
         {
@@ -683,7 +683,7 @@
       "id": "resources",
       "capability": "resources",
       "status": "unsupported",
-      "durationMs": 0.0022089999984018505,
+      "durationMs": 0.0022080000017012935,
       "message": "Resources are not advertised by the target.",
       "evidence": [
         {
@@ -699,7 +699,7 @@
       "id": "security-lite",
       "capability": "security-lite",
       "status": "fail",
-      "durationMs": 0.06170800000109011,
+      "durationMs": 0.057834000001093955,
       "message": "Found 6 security finding(s): 2 high, 2 medium, 2 low.",
       "evidence": [
         {
@@ -767,7 +767,7 @@
       "id": "runtime-profile",
       "capability": "runtime-profile",
       "status": "partial",
-      "durationMs": 0.21437499999956344,
+      "durationMs": 0.20362500000010186,
       "message": "Detected 7 potential egress target(s) and 21 potential state mutation(s) with high confidence.",
       "evidence": [
         {
@@ -958,7 +958,7 @@
       "id": "conformance",
       "capability": "conformance",
       "status": "pass",
-      "durationMs": 717.015707999999,
+      "durationMs": 773.3511670000007,
       "message": "All 7 conformance checks passed.",
       "evidence": [
         {
@@ -984,7 +984,7 @@
       "id": "schema-quality",
       "capability": "schema-quality",
       "status": "partial",
-      "durationMs": 1.3825419999993755,
+      "durationMs": 1.262790999999197,
       "message": "Found 5 quality finding(s) across 24 item(s): 0 warnings, 5 info.",
       "evidence": [
         {
@@ -1046,7 +1046,7 @@
       "id": "security",
       "capability": "security",
       "status": "fail",
-      "durationMs": 0.8916250000002037,
+      "durationMs": 0.8856250000008004,
       "message": "Found 6 security finding(s): 2 high, 2 medium, 2 low.",
       "evidence": [
         {
@@ -1114,7 +1114,7 @@
       "id": "attack-sim",
       "capability": "attack-sim",
       "status": "fail",
-      "durationMs": 1.0519169999970472,
+      "durationMs": 1.3217079999994894,
       "message": "Safe attack simulation found 4 finding(s): 1 high, 3 medium, 0 low.",
       "evidence": [
         {
@@ -1275,17 +1275,17 @@
         "weight": 0.1,
         "score": 100,
         "details": [
-          "Connect: 836ms",
+          "Connect: 659ms",
           "p95 latency: 3ms (3 operations)"
         ]
       }
     ]
   },
   "performanceMetrics": {
-    "connectMs": 835.6217080000024,
-    "toolsListMs": 2.8462499999986903,
-    "promptsListMs": 0.000915999997232575,
-    "resourcesListMs": 0.0022089999984018505
+    "connectMs": 658.5614999999998,
+    "toolsListMs": 2.7732919999998558,
+    "promptsListMs": 0.0008340000003954628,
+    "resourcesListMs": 0.0022080000017012935
   },
   "runtimeProfile": {
     "egress": [
@@ -1460,7 +1460,7 @@
         "source": "description_analysis"
       }
     ],
-    "analyzedAt": "2026-07-12T23:44:11.239Z",
+    "analyzedAt": "2026-07-17T00:36:34.091Z",
     "confidence": "high"
   }
 }

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

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-12T23:44:10.399Z
+Generated at 2026-07-17T00:36:33.428Z
 
 ## Target and Environment Metadata
 
@@ -88,7 +88,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:11.239Z_
+_Analyzed at 2026-07-17T00:36:34.091Z_
 
 ## Regressions and Recoveries
 
@@ -98,13 +98,13 @@ _Use the `diff` command against another run artifact to classify regressions and
 
 | Focus | Check | Status | Duration (ms) | Message |
 | --- | --- | --- | --- | --- |
-| healthy | conformance | pass | 717.02 | All 7 conformance checks passed. |
-| healthy | tools | pass | 2.85 | Advertised capability responded with the minimal expected shape (24 items). |
-| review | runtime-profile | partial | 0.21 | Detected 7 potential egress target(s) and 21 potential state mutation(s) with high confidence. |
-| review | schema-quality | partial | 1.38 | Found 5 quality finding(s) across 24 item(s): 0 warnings, 5 info. |
+| healthy | conformance | pass | 773.35 | All 7 conformance checks passed. |
+| healthy | tools | pass | 2.77 | Advertised capability responded with the minimal expected shape (24 items). |
+| review | runtime-profile | partial | 0.20 | Detected 7 potential egress target(s) and 21 potential state mutation(s) with high confidence. |
+| review | schema-quality | partial | 1.26 | Found 5 quality finding(s) across 24 item(s): 0 warnings, 5 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.05 | Safe attack simulation found 4 finding(s): 1 high, 3 medium, 0 low. |
+| act now | attack-sim | fail | 1.32 | Safe attack simulation found 4 finding(s): 1 high, 3 medium, 0 low. |
 | act now | security | fail | 0.89 | Found 6 security finding(s): 2 high, 2 medium, 2 low. |
 | act now | security-lite | fail | 0.06 | Found 6 security finding(s): 2 high, 2 medium, 2 low. |
 
@@ -229,5 +229,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-12T234410399Z_1a4faea8`
+- Run ID: `run_2026-07-17T003633428Z_a9fd4dd4`
 - Gate: `fail`

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

@@ -2,9 +2,9 @@
   "artifactType": "run",
   "schemaVersion": "1.0.0",
   "gate": "fail",
-  "runId": "run_2026-07-12T234429948Z_a99275fd",
-  "createdAt": "2026-07-12T23:44:29.948Z",
-  "toolVersion": "1.31.0",
+  "runId": "run_2026-07-15T223347574Z_9c8e8a04",
+  "createdAt": "2026-07-15T22:33:47.574Z",
+  "toolVersion": "1.32.1",
   "target": {
     "targetId": "postgres-server",
     "adapter": "local-process",
@@ -44,7 +44,7 @@
       "id": "tools",
       "capability": "tools",
       "status": "pass",
-      "durationMs": 0.3888340000048629,
+      "durationMs": 0.39333299999998417,
       "message": "Advertised capability responded with the minimal expected shape (1 item).",
       "evidence": [
         {
@@ -74,7 +74,7 @@
       "id": "prompts",
       "capability": "prompts",
       "status": "unsupported",
-      "durationMs": 0.0008339999985764734,
+      "durationMs": 0.0009580000041751191,
       "message": "Prompts are not advertised by the target.",
       "evidence": [
         {
@@ -90,7 +90,7 @@
       "id": "resources",
       "capability": "resources",
       "status": "fail",
-      "durationMs": 6.440833000000566,
+      "durationMs": 7.060457999999926,
       "message": "Advertised capability did not respond successfully.",
       "evidence": [
         {
@@ -117,7 +117,7 @@
       "id": "security-lite",
       "capability": "security-lite",
       "status": "pass",
-      "durationMs": 0.019625000000814907,
+      "durationMs": 0.013832999997248407,
       "message": "No security issues detected (lightweight scan).",
       "evidence": [
         {
@@ -133,7 +133,7 @@
       "id": "runtime-profile",
       "capability": "runtime-profile",
       "status": "pass",
-      "durationMs": 0.033833000001322944,
+      "durationMs": 0.025374999997438863,
       "message": "Detected 0 potential egress target(s) and 1 potential state mutation(s) with low confidence.",
       "evidence": [
         {
@@ -162,7 +162,7 @@
       "id": "conformance",
       "capability": "conformance",
       "status": "partial",
-      "durationMs": 1.618291999999201,
+      "durationMs": 1.3955409999980475,
       "message": "5/7 conformance checks passed, 2 failed.",
       "evidence": [
         {
@@ -191,7 +191,7 @@
       "id": "schema-quality",
       "capability": "schema-quality",
       "status": "partial",
-      "durationMs": 0.6995000000024447,
+      "durationMs": 0.8317500000048312,
       "message": "Found 2 quality finding(s) across 1 item(s): 0 warnings, 2 info.",
       "evidence": [
         {
@@ -228,7 +228,7 @@
       "id": "security",
       "capability": "security",
       "status": "pass",
-      "durationMs": 0.07745799999975134,
+      "durationMs": 0.12654099999781465,
       "message": "No security issues detected.",
       "evidence": [
         {
@@ -244,7 +244,7 @@
       "id": "attack-sim",
       "capability": "attack-sim",
       "status": "pass",
-      "durationMs": 0.9408750000002328,
+      "durationMs": 0.875040999999328,
       "message": "Safe attack simulation found no high-risk MCP attack-readiness findings.",
       "evidence": [
         {
@@ -303,17 +303,17 @@
         "weight": 0.1,
         "score": 100,
         "details": [
-          "Connect: 759ms",
-          "p95 latency: 6ms (3 operations)"
+          "Connect: 809ms",
+          "p95 latency: 7ms (3 operations)"
         ]
       }
     ]
   },
   "performanceMetrics": {
-    "connectMs": 759.3523330000025,
-    "toolsListMs": 0.3888340000048629,
-    "promptsListMs": 0.0008339999985764734,
-    "resourcesListMs": 6.440833000000566
+    "connectMs": 808.682375000004,
+    "toolsListMs": 0.39333299999998417,
+    "promptsListMs": 0.0009580000041751191,
+    "resourcesListMs": 7.060457999999926
   },
   "runtimeProfile": {
     "stateMutations": [
@@ -324,7 +324,7 @@
         "source": "description_analysis"
       }
     ],
-    "analyzedAt": "2026-07-12T23:44:30.715Z",
+    "analyzedAt": "2026-07-15T22:33:48.390Z",
     "confidence": "medium"
   }
 }