Skills/npm/gws-mcp-server

gws-mcp-server@0.5.0

VERIFIED· not started

Publisher claims: "MCP server that exposes Google Workspace CLI (gws) as Model Context Protocol tools" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher conorbronsdon · publishing for 257 daysInstalls 1,279Last detonated 16 h ago
$claude mcp add gws-mcp-server -- npx -y gws-mcp-server
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified 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 google.com — 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
server startup · the tool list · tool behavior

Connect it under the guard. Not started: dependency install failed; the server itself was not observed. 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 gws-mcp-server

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

What changed since 0.4.1

vet-skills diff gws-mcp-server 0.4.1 0.5.0

This version reaches for something 0.4.1 did not: 1 new host (google.com). Compared from the two recorded runs, not from source.

New hosts
google.com

0.4.1 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.

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; not started: dependency install failed; the server itself was not observed) on 2026-11-19 and scored it 91/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 · 5 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
5.3sprocessdependency install exit 1 · (Use `node --trace-warnings ...` to show where the warning was created) npm error Cannot read properties of null (reading 'edgesOut') npm error A complete log of this run can be found in: /tmp/ks-detonate-g09kIz/task/home/.npm/_logs/2026-11-19T08_43_39_420Z-debug-0.log
5.3sclaimednot started: dependency install failed (exit 1); the server itself was not observed
5.3sprocessscript backend runs setup only
5.3sprocessno install scripts to re-run

Static findings

HIGH
Destructive file system command detectedbuild/index.js:346 · Destructive file system command detected// The MIME type of the bytes we actually download: the export formatFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05

No other findings across 3,330 lines in 18 files.

Cost to the agent

Instructions loaded
≈57 tok
1 file · 18 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 gws-mcp-server@0.5.0 as of 16 h ago. This is the package itself, not its dependencies.