Vet MCP Server

@safedep/vet npm v1.17.4 Source verified

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

Trust grade
C
78/100
Last scanned
Trust
C · 78/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.
C Why this grade 100 − 21.7 = 78/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
−15.4 Package runs install-time scripts MTC-SUP-010 supply-chain
−6.3 Untrusted input concatenated into a command sink 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 4

high Shell/command execution in server code (bin/vet.js)MTC-SRC-002

In the server's implementation (`bin/vet.js:5`): 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 bin/vet.js

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

In the server's implementation (`install.js:8`): 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 install.js

high Package runs install-time scripts (preinstall, postinstall)MTC-SUP-010

"@safedep/vet" executes preinstall/postinstall script(s) at install time. The large majority of malicious packages abuse install hooks to run code before you ever import them.

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package @safedep/vet

medium Untrusted input concatenated into a command sink (install.js)MTC-SRC-009

In the server's implementation (`install.js:113`): 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( `powershell -NoProfile -Command "Expand-Archive -Force -Path '${archivePath}' -DestinationPath '${

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 install.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
v1.17.4 latest C 78/100 4 1.5.0 2026-07-23

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: C · 78/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/safedep-vet/badge.svg)](https://mcptrustchecker.com/registry/safedep-vet)
HTML
<a href="https://mcptrustchecker.com/registry/safedep-vet"><img src="https://mcptrustchecker.com/registry/safedep-vet/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/safedep-vet/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 @safedep/vet --online

Use the free API → How scoring works

More in Security & Testing