mcp@0.64.52

VERIFIED· install only

Publisher claims: "MCP server runtime for GJS and Node — default-deny read-only gate, stdio serve loop that ends on client EOF, uniform tool results" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher gjsify · publishing for 152 daysInstalls 12,654Last detonated 1 h ago
$claude mcp add mcp -- npx -y @gjsify/mcp
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
6 of 6 bundled scripts run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

What changed since 0.64.41

vet-skills diff mcp 0.64.41 0.64.52

In the sandbox, this version reached for nothing 0.64.41 did not. Compared from the two recorded runs, not from source.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-21 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 1 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.1sprocessbundled script run in the sandbox with no arguments
0.2sprocessexited 1: Node.js v22.23.5
0.2sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.3sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.4sprocessexited 1: Node.js v22.23.5
0.4sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.5sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.6sprocess6 of 6 bundled scripts run with no arguments
0.6sprocessscript backend runs setup only
0.6sprocessscript backend runs setup only
0.6sprocessno install scripts to re-run

Static findings

No findings across 232 lines in 15 files.

Cost to the agent

Instructions loaded
≈57 tok
1 file · 15 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

No advisories in OSV for @gjsify/mcp@0.64.52 as of 22 min ago. This is the package itself, not its dependencies.