Cli MCP Server

@cynicalsally/cli npm v0.7.0 Source verified

Published by w1ckedxt — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Trust grade
B
88/100
Last scanned
Trust
B · 88/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
B Why this grade 100 − 11.7 = 88/100

Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:

PointsWhat was foundCategory
−11.7 Untrusted input concatenated into a command sink ×4 MTC-SRC-009 injection

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind the deduction.

Findings 9

high Reads a sensitive credential path or dumps the environment (dist/utils/files.js)MTC-SRC-006

In the server's implementation (`dist/utils/files.js:53`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: id_rsa

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/utils/files.js

high Shell/command execution in server code (dist/commands/tools.js)MTC-SRC-002

In the server's implementation (`dist/commands/tools.js:311`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/commands/tools.js

high Shell/command execution in server code (dist/commands/upgrade.js)MTC-SRC-002

In the server's implementation (`dist/commands/upgrade.js:4`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/commands/upgrade.js

high Shell/command execution in server code (dist/utils/background.js)MTC-SRC-002

In the server's implementation (`dist/utils/background.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/utils/background.js

high Shell/command execution in server code (dist/utils/git.js)MTC-SRC-002

In the server's implementation (`dist/utils/git.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/utils/git.js

medium Untrusted input concatenated into a command sink (dist/commands/tools.js)MTC-SRC-009

In the server's implementation (`dist/commands/tools.js:314`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: execSync(`gh pr diff ${

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/commands/tools.js

medium Untrusted input concatenated into a command sink (dist/commands/upgrade.js)MTC-SRC-009

In the server's implementation (`dist/commands/upgrade.js:35`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: exec(`${openCmd} "${

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/commands/upgrade.js

medium Untrusted input concatenated into a command sink (dist/utils/background.js)MTC-SRC-009

In the server's implementation (`dist/utils/background.js:31`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: exec(`osascript -e 'display notification "${safeMessage}" with title "${

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/utils/background.js

medium Untrusted input concatenated into a command sink (dist/utils/git.js)MTC-SRC-009

In the server's implementation (`dist/utils/git.js:38`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: execSync(`git diff ${

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/utils/git.js

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.7.0 latest B 88/100 9 1.5.0 2026-07-22

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: B · 88/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/cynicalsally-cli/badge.svg)](https://mcptrustchecker.com/registry/cynicalsally-cli)
HTML
<a href="https://mcptrustchecker.com/registry/cynicalsally-cli"><img src="https://mcptrustchecker.com/registry/cynicalsally-cli/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/cynicalsally-cli/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @cynicalsally/cli --online

Use the free API → How scoring works

More in Developer Tools