@kryptosai/mcp-observatory 1.32.1 → 1.34.0

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

@@ -0,0 +1,211 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:34:58.292Z
+
+## Target and Environment Metadata
+
+- Target: `trello-mcp-server`
+- Adapter: `local-process`
+- Command: `npx -y trello-mcp-server`
+- Server: `Trello MCP Server 1.0.0`
+- Platform: `darwin 25.5.0`
+- Node: `v22.22.1`
+
+## Executive Summary
+
+**Health Score: 77/100 (C)**
+
+| Dimension | Score | Weight |
+| --- | --- | --- |
+| Protocol Compliance | 100/100 | 30% |
+| Schema Quality | 0/100 | 20% |
+| Security | 100/100 | 20% |
+| Reliability | 83/100 | 20% |
+| Performance | 100/100 | 10% |
+
+| Gate | Total | Pass | Fail | Partial | Unsupported | Flaky | Skipped |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| fail | 9 | 7 | 1 | 0 | 1 | 0 | 0 |
+
+## At a Glance
+
+- Safety verdict: **Blocked** — One or more checks can break agent dependence and should be fixed before production use.
+- Top risks: schema-quality: Found 24 quality finding(s) across 16 item(s): 16 warnings, 8 info.
+- Regression/schema drift: Run `mcp-observatory diff <previous-run.json> <current-run.json>` to classify regressions and schema drift.
+- Failing checks: schema-quality
+- Partial or flaky checks: none
+- Skipped checks: none
+- Unsupported checks: prompts
+- Suggested next step: Start with the failing checks: schema-quality.
+- 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
+- ℹ️ 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 |
+| filesystem | write | working_directory | description_analysis |
+| filesystem | write | working_directory | description_analysis |
+| filesystem | write | working_directory | description_analysis |
+| filesystem | write | working_directory | description_analysis |
+
+_Analyzed at 2026-07-15T22:34:59.057Z_
+
+## Regressions and Recoveries
+
+_Use the `diff` command against another run artifact to classify regressions and recoveries over time._
+
+## Full Capability Status Table
+
+| Focus | Check | Status | Duration (ms) | Message |
+| --- | --- | --- | --- | --- |
+| healthy | attack-sim | pass | 1.61 | Safe attack simulation found no high-risk MCP attack-readiness findings. |
+| healthy | conformance | pass | 214.95 | All 7 conformance checks passed. |
+| healthy | resources | pass | 0.66 | Advertised capability responded with the minimal expected shape (3 items). |
+| healthy | runtime-profile | pass | 0.07 | Detected 0 potential egress target(s) and 5 potential state mutation(s) with low confidence. |
+| healthy | security | pass | 0.92 | No security issues detected. |
+| healthy | security-lite | pass | 0.03 | No security issues detected (lightweight scan). |
+| healthy | tools | pass | 3.02 | Advertised capability responded with the minimal expected shape (15 items). |
+| confirm intent | prompts | unsupported | 0.00 | Prompts are not advertised by the target. |
+| act now | schema-quality | fail | 1.90 | Found 24 quality finding(s) across 16 item(s): 16 warnings, 8 info. |
+
+## Evidence Snippets
+
+### attack-sim — pass
+
+Summary: Safe attack simulation found no high-risk MCP attack-readiness findings.
+
+- Endpoint: `attack-sim/safe`
+  - Advertised: `true`
+  - Responded: `true`
+  - Minimal shape present: `true`
+  - Item count: `0`
+  - Identifiers: none
+  - Diagnostics: none
+
+### conformance — pass
+
+Summary: All 7 conformance checks passed.
+
+- Endpoint: `conformance/check`
+  - Advertised: `true`
+  - Responded: `true`
+  - Minimal shape present: `true`
+  - Item count: `7`
+  - Identifiers: none
+  - Diagnostics: [pass] capabilities-present: Server returned capabilities object., [pass] server-info: Server provided initialization info., [pass] tools-capability-match: tools/list returned 15 tool(s). (+4 more)
+
+### resources — pass
+
+Summary: Advertised capability responded with the minimal expected shape (3 items).
+
+- Endpoint: `resources/list`
+  - Advertised: `true`
+  - Responded: `true`
+  - Minimal shape present: `true`
+  - Item count: `1`
+  - Identifiers: trello://boards
+  - Diagnostics: none
+- Endpoint: `resources/templates/list`
+  - Advertised: `true`
+  - Responded: `true`
+  - Minimal shape present: `true`
+  - Item count: `2`
+  - Identifiers: trello://boards/{boardId}/lists, trello://lists/{listId}/cards
+  - Diagnostics: none
+
+### runtime-profile — pass
+
+Summary: Detected 0 potential egress target(s) and 5 potential state mutation(s) with low confidence.
+
+- Endpoint: `runtime-profile/analyze`
+  - Advertised: `true`
+  - Responded: `true`
+  - Minimal shape present: `true`
+  - Item count: `5`
+  - Identifiers: none
+  - Diagnostics: Egress entries: 0, State mutations: 5, Confidence: medium
+
+### security — pass
+
+Summary: No security issues detected.
+
+- Endpoint: `security/scan`
+  - Advertised: `true`
+  - Responded: `true`
+  - Minimal shape present: `true`
+  - Item count: `0`
+  - Identifiers: none
+  - Diagnostics: none
+
+### security-lite — pass
+
+Summary: No security issues detected (lightweight scan).
+
+- Endpoint: `security/scan-lite`
+  - Advertised: `true`
+  - Responded: `true`
+  - Minimal shape present: `true`
+  - Item count: `0`
+  - Identifiers: none
+  - Diagnostics: none
+
+### tools — pass
+
+Summary: Advertised capability responded with the minimal expected shape (15 items).
+
+- Endpoint: `tools/list`
+  - Advertised: `true`
+  - Responded: `true`
+  - Minimal shape present: `true`
+  - Item count: `15`
+  - Identifiers: create-card, get-boards, get-lists, create-cards, move-card (+10 more)
+  - Diagnostics: none
+
+### prompts — unsupported
+
+Summary: Prompts are not advertised by the target.
+
+- Endpoint: `prompts/list`
+  - Advertised: `false`
+  - Responded: `false`
+  - Minimal shape present: `false`
+  - Item count: `0`
+  - Identifiers: none
+  - Diagnostics: none
+
+### schema-quality — fail
+
+Summary: Found 24 quality finding(s) across 16 item(s): 16 warnings, 8 info.
+
+- Endpoint: `schema-quality/scan`
+  - Advertised: `true`
+  - Responded: `true`
+  - Minimal shape present: `true`
+  - Item count: `24`
+  - Identifiers: create-card, get-boards, get-lists, create-cards, move-card (+11 more)
+  - Diagnostics: [warning] tool "create-card": Missing description, [info] tool "create-card": Property 'name' missing description, [info] tool "create-card": Property 'description' missing description (+21 more)
+
+## 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-15T223458292Z_6e410b41`
+- Gate: `fail`

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

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-15T223453315Z_f2ff6c17",
+  "createdAt": "2026-07-15T22:34:53.315Z",
+  "toolVersion": "1.32.1",
+  "target": {
+    "targetId": "twilio-mcp",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "twilio-mcp"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "twilio-mcp",
+      "purpose": "mcp-safety-index",
+      "riskClass": "Communication platform access",
+      "failureClass": "SMS/voice/chat boundary",
+      "whyItMatters": "Twilio MCP servers can send SMS, make voice calls, and manage messaging services — agents could trigger communications to real phone numbers."
+    }
+  },
+  "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 `twilio-mcp`.\nCommand: npx -y twilio-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- ❌ Environment validation failed:\n- - TWILIO_ACCOUNT_SID: Required\n- - TWILIO_AUTH_TOKEN: Required\n- - TWILIO_PHONE_NUMBER: Required\n- - WEBHOOK_BASE_URL: Required"
+}

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

@@ -0,0 +1,106 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:34:53.315Z
+
+## Target and Environment Metadata
+
+- Target: `twilio-mcp`
+- Adapter: `local-process`
+- Command: `npx -y twilio-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 `twilio-mcp`.
+Command: npx -y twilio-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:
+- ❌ Environment validation failed:
+- - TWILIO_ACCOUNT_SID: Required
+- - TWILIO_AUTH_TOKEN: Required
+- - TWILIO_PHONE_NUMBER: Required
+- - WEBHOOK_BASE_URL: Required
+```
+
+## 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-15T223453315Z_f2ff6c17`
+- Gate: `fail`

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

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-15T223507161Z_4410d394",
+  "createdAt": "2026-07-15T22:35:07.161Z",
+  "toolVersion": "1.32.1",
+  "target": {
+    "targetId": "udyam-mcp",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "udyam-mcp"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "udyam-mcp",
+      "purpose": "mcp-safety-index",
+      "riskClass": "MSME business registration access",
+      "failureClass": "Business registration/verification boundary",
+      "whyItMatters": "Udyam registration is mandatory for 63M+ Indian MSMEs. MCP servers querying or verifying Udyam certificates access official business identity 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 `udyam-mcp`.\nCommand: npx -y udyam-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  'udyam-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_07_232Z-debug-0.log"
+}

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

@@ -0,0 +1,106 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:35:07.161Z
+
+## Target and Environment Metadata
+
+- Target: `udyam-mcp`
+- Adapter: `local-process`
+- Command: `npx -y udyam-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 `udyam-mcp`.
+Command: npx -y udyam-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  'udyam-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_07_232Z-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-15T223507161Z_4410d394`
+- Gate: `fail`

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

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-15T223552658Z_69a2e94d",
+  "createdAt": "2026-07-15T22:35:52.658Z",
+  "toolVersion": "1.32.1",
+  "target": {
+    "targetId": "ufone-mcp",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "ufone-mcp"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "ufone-mcp",
+      "purpose": "mcp-safety-index",
+      "riskClass": "Pakistani telecom API access (PTCL group)",
+      "failureClass": "SMS/voice/fiber boundary",
+      "whyItMatters": "Ufone (PTCL group) combines mobile and fiber infrastructure, Pakistan's largest fixed-line backbone. MCP servers bridging telecom and broadband services need visible infrastructure 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 `ufone-mcp`.\nCommand: npx -y ufone-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  'ufone-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_52_731Z-debug-0.log"
+}