Pmpt Cli MCP Server
pmpt-cli
npm
v1.18.2
Published by pmptwiki — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Record and share your AI-driven product development journey
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 11.7 = 88. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −11.7 | Untrusted input concatenated into a command sink ×4 MTC-SRC-009 | injection |
2. Client adoption risk — 88 − 11 = 77. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −10 | capability blast radius (critical) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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 a deduction.
Findings 11
high Shell/command execution in server code (dist/commands/doctor.js)MTC-SRC-002
In the server's implementation (`dist/commands/doctor.js:2`): 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: port { execSync } from 'child_process'; import { existsSync, readFileSync } from 'fs'; import { join } from 'path'; impo
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/doctor.js
high Shell/command execution in server code (dist/commands/mcp-setup.js)MTC-SRC-002
In the server's implementation (`dist/commands/mcp-setup.js:2`): 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: port { execSync } from 'child_process'; import { existsSync, readFileSync, writeFileSync, mkdirSync, chmodSync } from 'f
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/mcp-setup.js
high Shell/command execution in server code (dist/index.js)MTC-SRC-002
In the server's implementation (`dist/index.js:257`): 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: exec } = await import('child_process'); prompts.intro('pmpt feedback'); const type = await prompts.select({
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/index.js
high Shell/command execution in server code (dist/lib/clipboard.js)MTC-SRC-002
In the server's implementation (`dist/lib/clipboard.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: port { execSync } from 'child_process'; export function copyToClipboard(text) { try { const platform = proce
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/lib/clipboard.js
high Shell/command execution in server code (dist/lib/config.js)MTC-SRC-002
In the server's implementation (`dist/lib/config.js:3`): 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: port { execSync } from 'child_process'; const CONFIG_DIR = '.pmpt'; const CONFIG_FILE = 'config.json'; const DEFAULT_DOC
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/lib/config.js
high Shell/command execution in server code (dist/lib/git.js)MTC-SRC-002
In the server's implementation (`dist/lib/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: port { execSync } from 'child_process'; import { existsSync } from 'fs'; import { join } from 'path'; /** * Check if di
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/lib/git.js
high Shell/command execution in server code (dist/lib/scanner.js)MTC-SRC-002
In the server's implementation (`dist/lib/scanner.js:3`): 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: port { execSync } from 'child_process'; import { isGitRepo } from './git.js'; // ── Scanner Functions ── function git(pa
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/lib/scanner.js
medium Untrusted input concatenated into a command sink (dist/commands/mcp-setup.js)MTC-SRC-009
In the server's implementation (`dist/commands/mcp-setup.js:78`): 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: ere' : 'which'; execSync(`${which} ${cmd}`, { stdio: ['pipe', 'pipe', 'pipe'] }); return true; }
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/mcp-setup.js
medium Untrusted input concatenated into a command sink (dist/index.js)MTC-SRC-009
In the server's implementation (`dist/index.js:280`): 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: tart' : 'xdg-open'; exec(`${openCmd} "${url}"`); prompts.log.success(`Opening ${url}`); prompts.outro('Thank
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/index.js
medium Untrusted input concatenated into a command sink (dist/lib/git.js)MTC-SRC-009
In the server's implementation (`dist/lib/git.js:15`): 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: try { return execSync(`git ${args}`, { cwd: path, encoding: 'utf-8', stdi
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/lib/git.js
medium Untrusted input concatenated into a command sink (dist/lib/scanner.js)MTC-SRC-009
In the server's implementation (`dist/lib/scanner.js:8`): 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: try { return execSync(`git ${args}`, { cwd: path, encoding: 'utf-8', stdi
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/lib/scanner.js
Tools 14
Each tool and what it can reach — statically extracted from the published source.
pmpt_read_contextingests untrusted inputpmpt_diffno sensitive capabilitypmpt_edit_planno sensitive capabilitypmpt_graduateno sensitive capabilitypmpt_historyno sensitive capabilitypmpt_log_decisionno sensitive capabilitypmpt_planno sensitive capabilitypmpt_plan_questionsno sensitive capabilitypmpt_publishno sensitive capabilitypmpt_qualityno sensitive capability
Show 4 more tools ↓
pmpt_saveno sensitive capabilitypmpt_squashno sensitive capabilitypmpt_statusno sensitive capabilitypmpt_update_docno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (14 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.18.2 latest |
C 77/100 | 11 | 1.13.0 | 2026-09-07 |
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.
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 pmpt-cli --onlineMore in Files & Storage
Safe bulk Meta ads: launch 150+ campaigns from Drive folders with spend guardrails and validation.
CLI tool to add MCP servers to various AI coding clients
MCP compatibility adapter for Agent Tool Protocol
MCP server for multi-tenant DuckDB management with R2/S3 storage
A stdio-to-HTTP MCP proxy that transparently intercepts file parameters, reading local files and base64-encoding them before forwarding to the remote server.
Free buyer-side outcome verification and provider comparison for supplied agent receipts.