Skills/npm/mmggws

mmggws@0.1.52

VERIFIED

Publisher claims: "MoMo Google Workspace CLI and MCP server" Observed in sandbox: calls registry.npmjs.org only, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher dta.teks · publishing for 157 daysInstalls 2,992Last detonated 3d ago
$claude mcp add mmggws -- npx -y mmggws
WatchReport an issue

Coverage

Server started and answered tools/list.
Tested
MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with real credentials

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 code
What the honeypot saw
no credential files read · reached only registry.npmjs.org
What we could not test
what the tools do when called with real credentials

Reasonable to connect. No credential asked for, no third-party host named, Server started and answered tools/list.

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) on 2026-11-11 and scored it 84/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: calls registry.npmjs.org only, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 20 s · 2 scenarios
t+CategoryObserved action
0.0sprocessno install scripts in bundle
20sfilesystemread ~/.config/gwmcp/token.json outside project
20snetworkCONNECT tcp://registry.npmjs.org:443
20sprocessexec /app/apps/web/node_modules/.bin/npm
20sprocessexec /root/.cache/node/corepack/v1/pnpm/10.28.0/dist/node-gyp-bin/npm
20sprocessexec /app/node_modules/.bin/npm
20sprocessexec /pnpm/npm
20sprocessexec /usr/local/sbin/npm
20sprocessexec /usr/local/bin/npm
20sprocessexec /tmp/ks-detonate-IcQamd/task/home/work/acme-api/.claude/skills/mmggws/node_modules/@mmggws/linux-x64/vendor/mmggws-linux-amd64
20sclaimed3 tools: execute, instructions, search
20sprocessscript backend runs setup only
20sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packagebin/mmggws.js:27 · npx invocation of non-well-known package — may execute untrusted code// another platform, --omit=optional, or a cached npx install that lost it). TheFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagebin/mmggws.js:70 · npx invocation of non-well-known package — may execute untrusted codeconsole.error(` remove the cached npx install: rm -rf "${parts.slice(0, npxIndex + 2).join(sep)}"`);Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagebin/mmggws.js:71 · npx invocation of non-well-known package — may execute untrusted codeconsole.error(" then run your npx command again");Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈43 tok
1 file · 6 in bundle
Tool list per prompt
≈566 tok
3 tools · 189 per tool
Handshake
2179 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 248

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 mmggws@0.1.52 as of 3d ago. This is the package itself, not its dependencies.