@kryptosai/mcp-observatory 1.32.1 → 1.34.0

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

@@ -0,0 +1,103 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:35:04.923Z
+
+## Target and Environment Metadata
+
+- Target: `razorpay-mcp`
+- Adapter: `local-process`
+- Command: `npx -y razorpay-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 `razorpay-mcp`.
+Command: npx -y razorpay-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 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_35_04_996Z-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-15T223504923Z_d539a063`
+- Gate: `fail`

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

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

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

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-12T23:44:35.935Z
+Generated at 2026-07-15T22:33:52.922Z
 
 ## 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_36_018Z-debug-0.log
+- npm error A complete log of this run can be found in: /Users/williamweishuhn/.npm/_logs/2026-07-15T22_33_52_997Z-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-12T234435935Z_f9c6f465`
+- Run ID: `run_2026-07-15T223352922Z_48cc0ac8`
 - Gate: `fail`

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

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-15T223447144Z_bfc04dbf",
+  "createdAt": "2026-07-15T22:34:47.144Z",
+  "toolVersion": "1.32.1",
+  "target": {
+    "targetId": "redis-server",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "mcp-server-redis"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "mcp-server-redis",
+      "purpose": "mcp-safety-index",
+      "riskClass": "Cache and data store mutation",
+      "failureClass": "Key/value mutation boundary",
+      "whyItMatters": "Redis MCP servers can read, write, and delete keys, manage pub/sub channels, and execute Lua scripts — agents could manipulate cache and session 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 `redis-server`.\nCommand: npx -y mcp-server-redis\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- /Users/williamweishuhn/.npm/_npx/19a26c80466dfc5c/node_modules/.bin/mcp-server-redis: line 10: AGENTS.md: command not found\n- /Users/williamweishuhn/.npm/_npx/19a26c80466dfc5c/node_modules/.bin/mcp-server-redis: line 11: AGENTS.md: command not found\n- /Users/williamweishuhn/.npm/_npx/19a26c80466dfc5c/node_modules/.bin/mcp-server-redis: line 12: action/: is a directory\n- /Users/williamweishuhn/.npm/_npx/19a26c80466dfc5c/node_modules/.bin/mcp-server-redis: line 14: syntax error near unexpected token `('\n- /Users/williamweishuhn/.npm/_npx/19a26c80466dfc5c/node_modules/.bin/mcp-server-redis: line 14: `const os = require('os');'"
+}

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

@@ -0,0 +1,106 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:34:47.144Z
+
+## Target and Environment Metadata
+
+- Target: `redis-server`
+- Adapter: `local-process`
+- Command: `npx -y mcp-server-redis`
+- 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 `redis-server`.
+Command: npx -y mcp-server-redis
+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:
+- /Users/williamweishuhn/.npm/_npx/19a26c80466dfc5c/node_modules/.bin/mcp-server-redis: line 10: AGENTS.md: command not found
+- /Users/williamweishuhn/.npm/_npx/19a26c80466dfc5c/node_modules/.bin/mcp-server-redis: line 11: AGENTS.md: command not found
+- /Users/williamweishuhn/.npm/_npx/19a26c80466dfc5c/node_modules/.bin/mcp-server-redis: line 12: action/: is a directory
+- /Users/williamweishuhn/.npm/_npx/19a26c80466dfc5c/node_modules/.bin/mcp-server-redis: line 14: syntax error near unexpected token `('
+- /Users/williamweishuhn/.npm/_npx/19a26c80466dfc5c/node_modules/.bin/mcp-server-redis: line 14: `const os = require('os');'
+```
+
+## 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-15T223447144Z_bfc04dbf`
+- Gate: `fail`

package/docs/safety-index/artifacts/ref-tools-server.json

@@ -2,9 +2,9 @@
   "artifactType": "run",
   "schemaVersion": "1.0.0",
   "gate": "pass",
-  "runId": "run_2026-07-12T234402182Z_8b188092",
-  "createdAt": "2026-07-12T23:44:02.182Z",
-  "toolVersion": "1.31.0",
+  "runId": "run_2026-07-17T003626429Z_130951f0",
+  "createdAt": "2026-07-17T00:36:26.429Z",
+  "toolVersion": "1.33.0",
   "target": {
     "targetId": "ref-tools-server",
     "adapter": "local-process",
@@ -43,7 +43,7 @@
       "id": "tools",
       "capability": "tools",
       "status": "pass",
-      "durationMs": 0.9122080000015558,
+      "durationMs": 1.037916999999652,
       "message": "Advertised capability responded with the minimal expected shape (2 items).",
       "evidence": [
         {
@@ -92,7 +92,7 @@
       "id": "prompts",
       "capability": "prompts",
       "status": "pass",
-      "durationMs": 0.20208400000046822,
+      "durationMs": 0.28758299999935844,
       "message": "Advertised capability responded with the minimal expected shape (2 items).",
       "evidence": [
         {
@@ -115,7 +115,7 @@
       "id": "resources",
       "capability": "resources",
       "status": "unsupported",
-      "durationMs": 0.0018750000017462298,
+      "durationMs": 0.0032499999997526174,
       "message": "Resources are not advertised by the target.",
       "evidence": [
         {
@@ -131,7 +131,7 @@
       "id": "security-lite",
       "capability": "security-lite",
       "status": "pass",
-      "durationMs": 0.01933399999870744,
+      "durationMs": 0.01900000000023283,
       "message": "No security issues detected (lightweight scan).",
       "evidence": [
         {
@@ -147,7 +147,7 @@
       "id": "runtime-profile",
       "capability": "runtime-profile",
       "status": "partial",
-      "durationMs": 0.1114159999997355,
+      "durationMs": 0.10537499999918509,
       "message": "Detected 4 potential egress target(s) and 0 potential state mutation(s) with high confidence.",
       "evidence": [
         {
@@ -194,7 +194,7 @@
       "id": "conformance",
       "capability": "conformance",
       "status": "pass",
-      "durationMs": 0.4568749999998545,
+      "durationMs": 0.4587499999997817,
       "message": "All 7 conformance checks passed.",
       "evidence": [
         {
@@ -220,7 +220,7 @@
       "id": "schema-quality",
       "capability": "schema-quality",
       "status": "pass",
-      "durationMs": 0.5522080000009737,
+      "durationMs": 0.4734169999992446,
       "message": "All 4 item(s) have good schema quality.",
       "evidence": [
         {
@@ -237,7 +237,7 @@
       "id": "security",
       "capability": "security",
       "status": "pass",
-      "durationMs": 0.20024999999986903,
+      "durationMs": 0.14400000000023283,
       "message": "No security issues detected.",
       "evidence": [
         {
@@ -253,7 +253,7 @@
       "id": "attack-sim",
       "capability": "attack-sim",
       "status": "pass",
-      "durationMs": 0.28787499999998545,
+      "durationMs": 0.2027909999997064,
       "message": "Safe attack simulation found no high-risk MCP attack-readiness findings.",
       "evidence": [
         {
@@ -312,17 +312,17 @@
         "weight": 0.1,
         "score": 100,
         "details": [
-          "Connect: 775ms",
+          "Connect: 579ms",
           "p95 latency: 1ms (3 operations)"
         ]
       }
     ]
   },
   "performanceMetrics": {
-    "connectMs": 775.0896250000005,
-    "toolsListMs": 0.9122080000015558,
-    "promptsListMs": 0.20208400000046822,
-    "resourcesListMs": 0.0018750000017462298
+    "connectMs": 579.0261249999994,
+    "toolsListMs": 1.037916999999652,
+    "promptsListMs": 0.28758299999935844,
+    "resourcesListMs": 0.0032499999997526174
   },
   "runtimeProfile": {
     "egress": [
@@ -351,7 +351,7 @@
         "confidence": "low"
       }
     ],
-    "analyzedAt": "2026-07-12T23:44:02.958Z",
+    "analyzedAt": "2026-07-17T00:36:27.010Z",
     "confidence": "high"
   }
 }

package/docs/safety-index/artifacts/ref-tools-server.md

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-12T23:44:02.182Z
+Generated at 2026-07-17T00:36:26.429Z
 
 ## Target and Environment Metadata
 
@@ -57,7 +57,7 @@ The following targets were identified as potentially reachable by this server (c
 | The URL of the webpage to read. | unknown | description_analysis | medium |
 | ref_read_url | unknown | description_analysis | low |
 
-_Analyzed at 2026-07-12T23:44:02.958Z_
+_Analyzed at 2026-07-17T00:36:27.010Z_
 
 ## Regressions and Recoveries
 
@@ -67,13 +67,13 @@ _Use the `diff` command against another run artifact to classify regressions and
 
 | Focus | Check | Status | Duration (ms) | Message |
 | --- | --- | --- | --- | --- |
-| healthy | attack-sim | pass | 0.29 | Safe attack simulation found no high-risk MCP attack-readiness findings. |
+| healthy | attack-sim | pass | 0.20 | Safe attack simulation found no high-risk MCP attack-readiness findings. |
 | healthy | conformance | pass | 0.46 | All 7 conformance checks passed. |
-| healthy | prompts | pass | 0.20 | Advertised capability responded with the minimal expected shape (2 items). |
-| healthy | schema-quality | pass | 0.55 | All 4 item(s) have good schema quality. |
-| healthy | security | pass | 0.20 | No security issues detected. |
+| healthy | prompts | pass | 0.29 | Advertised capability responded with the minimal expected shape (2 items). |
+| healthy | schema-quality | pass | 0.47 | All 4 item(s) have good schema quality. |
+| healthy | security | pass | 0.14 | No security issues detected. |
 | healthy | security-lite | pass | 0.02 | No security issues detected (lightweight scan). |
-| healthy | tools | pass | 0.91 | Advertised capability responded with the minimal expected shape (2 items). |
+| healthy | tools | pass | 1.04 | Advertised capability responded with the minimal expected shape (2 items). |
 | review | runtime-profile | partial | 0.11 | Detected 4 potential egress target(s) and 0 potential state mutation(s) with high confidence. |
 | confirm intent | resources | unsupported | 0.00 | Resources are not advertised by the target. |
 
@@ -198,5 +198,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-12T234402182Z_8b188092`
+- Run ID: `run_2026-07-17T003626429Z_130951f0`
 - Gate: `pass`

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

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-15T223503064Z_8b8b0ec6",
+  "createdAt": "2026-07-15T22:35:03.064Z",
+  "toolVersion": "1.32.1",
+  "target": {
+    "targetId": "resend-mcp",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "resend-mcp"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "resend-mcp",
+      "purpose": "mcp-safety-index",
+      "riskClass": "Email sending platform access",
+      "failureClass": "Email send/domain boundary",
+      "whyItMatters": "Resend MCP servers can send emails, manage domains, and track delivery — agents could send transactional and marketing emails on behalf of verified domains."
+    }
+  },
+  "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 `resend-mcp`.\nCommand: npx -y resend-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- Error: No API key. Set RESEND_API_KEY or use --key=<your-resend-api-key>"
+}

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

@@ -0,0 +1,102 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:35:03.064Z
+
+## Target and Environment Metadata
+
+- Target: `resend-mcp`
+- Adapter: `local-process`
+- Command: `npx -y resend-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 `resend-mcp`.
+Command: npx -y resend-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:
+- Error: No API key. Set RESEND_API_KEY or use --key=<your-resend-api-key>
+```
+
+## 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-15T223503064Z_8b8b0ec6`
+- Gate: `fail`