Skills/npm/mcp-watch

mcp-watch@2.0.2

CAUTION· startup only

Publisher claims: "Security scanner for Model Context Protocol (MCP) servers - detect vulnerabilities and security issues" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher kapilduraphe · publishing for 536 daysInstalls 639Last detonated 1 h ago

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
no credential variables read in the code
Where it talks to
no vendor host named in the codeAlso vulnerablemcp.info — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it under the guard. Startup only; authenticated tool behavior not tested. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- npx -y mcp-watch

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-20 and scored it 75/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Destructive command against a filesystem root or device; Destructive file system command detected; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 27 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
6.7sprocessdependency install exit 0
27sclaimedstartup only: exited (0) before answering · security vulnerabilities scan-local [options] <project-path> Scan a local MCP server project directory for security vulnerabilities help [command] display help for command
27sprocessscript backend runs setup only
27sprocessno install scripts to re-run

Static findings

CRITICAL
Destructive command against a filesystem root or devicedist/scanner/scanners/InputValidationScanner.js:67 · Destructive command against a filesystem root or devicemessage: "Command injection vulnerability - append && rm -rf /",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
HIGH
Destructive file system command detecteddist/scanner/scanners/InputValidationScanner.js:67 · Destructive file system command detectedmessage: "Command injection vulnerability - append && rm -rf /",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
HIGH
Access to sensitive file pathsdist/scanner/scanners/CredentialScanner.js:161 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files/process\.env\.[A-Z_]*(?:TOKEN|KEY|SECRET|PASSWORD)/i,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
File type combined with upload actiondist/scanner/scanners/InputValidationScanner.js:54 · File type combined with upload action — agent may exfiltrate local data filesconsole.log("🛡️ Scanning for input validation issues...");Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
HIGH
Access to sensitive file pathsdist/scanner/scanners/CredentialScanner.js:60 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
File permission modification commandpackage.json:10 · File permission modification command — agent changes file ownership/permissions"build": "tsc && chmod +x dist/main.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05

Cost to the agent

Instructions loaded
≈60 tok
1 file · 38 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for mcp-watch@2.0.2 as of 38 min ago. This is the package itself, not its dependencies.

What would make this Verified

5 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Destructive command against a filesystem root or device≈ +9 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
  2. Unclaimed publisher≈ +8 on the totalClaim kapilduraphe: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  3. Destructive file system command detected≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
  4. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  5. File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
  6. File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim kapilduraphePropose a patch to the maintainer