Skills/npm/gmail-mcp

gmail-mcp@1.2.4

VERIFIED· not started

Publisher claims: "Lean Gmail MCP server with auto authentication support (maintained fork of GongRzhe/Gmail-MCP-Server)" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher artymclabin · publishing for 127 daysInstalls 1,977Last detonated 5d ago
$claude mcp add gmail-mcp -- npx -y @artymclabin/gmail-mcp
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
GMAIL_CREDENTIALS_PATHGMAIL_OAUTH_PATHConfiguration, not credentials: GMAIL_MCP_TOOL_PREFIX
Where it talks to
no vendor host named in the codeAlso google.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names google.com as well as its own vendor. The guard injects GMAIL_CREDENTIALS_PATH, GMAIL_OAUTH_PATH only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- npx -y @artymclabin/gmail-mcp

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; not started: dependency install failed; the server itself was not observed) on 2026-11-09 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 · 9 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
8.9sprocessdependency 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-6YISbS/task/home/.npm/_logs/2026-11-09T16_46_48_809Z-debug-0.log
8.9sclaimednot started: dependency install failed (exit 1); the server itself was not observed
8.9sprocessscript backend runs setup only
9.0sprocessno install scripts to re-run

Static findings

No findings across 4,072 lines in 14 files.

Cost to the agent

Instructions loaded
≈63 tok
1 file · 14 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 @artymclabin/gmail-mcp@1.2.4 as of 5d ago. This is the package itself, not its dependencies.