Gogcli Mcp Gmail MCP Server

gogcli-mcp-gmail npm v2.29.0 Source verified

Published by chrischall — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Extended Gmail MCP server via gogcli — auth + full Gmail support (threads, labels, drafts, attachments, forward, autoreply, bulk operations)

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

high Dynamic code execution in server code (dist/index.js)MTC-SRC-001

In the server's implementation (`dist/index.js:2946`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const makeValidate = new Function(`${names_1.default.self}`, `${names_1.default.scope}`, sourceCode); const v

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/index.js

high Shell/command execution in server code (dist/index.js)MTC-SRC-002

In the server's implementation (`dist/index.js:31651`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ?? (await import("node:child_process")).spawn; const effectiveTimeout = timeout ?? TIMEOUT_MS; return new Promise((

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/index.js

Tools 43

Each tool and what it can reach — statically extracted from the published source.

  • gog_gmail_attachmentingests untrusted input
  • gog_gmail_rawreads sensitive data
  • gog_gmail_thread_attachmentsingests untrusted input
  • gog_gmail_thread_getingests untrusted input
  • gog_gmail_autoreplyno sensitive capability
  • gog_gmail_batch_deleteno sensitive capability
  • gog_gmail_batch_modifyno sensitive capability
  • gog_gmail_drafts_createno sensitive capability
  • gog_gmail_drafts_deleteno sensitive capability
  • gog_gmail_drafts_diffno sensitive capability
Show 33 more tools ↓
  • gog_gmail_drafts_forwardno sensitive capability
  • gog_gmail_drafts_getno sensitive capability
  • gog_gmail_drafts_listno sensitive capability
  • gog_gmail_drafts_replyno sensitive capability
  • gog_gmail_drafts_reply_allno sensitive capability
  • gog_gmail_drafts_sendno sensitive capability
  • gog_gmail_drafts_updateno sensitive capability
  • gog_gmail_filters_createno sensitive capability
  • gog_gmail_filters_deleteno sensitive capability
  • gog_gmail_filters_getno sensitive capability
  • gog_gmail_filters_listno sensitive capability
  • gog_gmail_forwardno sensitive capability
  • gog_gmail_historyno sensitive capability
  • gog_gmail_importno sensitive capability
  • gog_gmail_labels_createno sensitive capability
  • gog_gmail_labels_deleteno sensitive capability
  • gog_gmail_labels_getno sensitive capability
  • gog_gmail_labels_listno sensitive capability
  • gog_gmail_labels_modifyno sensitive capability
  • gog_gmail_labels_renameno sensitive capability
  • gog_gmail_labels_styleno sensitive capability
  • gog_gmail_message_modifyno sensitive capability
  • gog_gmail_messages_searchno sensitive capability
  • gog_gmail_sendas_createno sensitive capability
  • gog_gmail_sendas_deleteno sensitive capability
  • gog_gmail_sendas_getno sensitive capability
  • gog_gmail_sendas_listno sensitive capability
  • gog_gmail_sendas_updateno sensitive capability
  • gog_gmail_sendas_verifyno sensitive capability
  • gog_gmail_thread_modifyno sensitive capability
  • gog_gmail_urlno sensitive capability
  • gog_gmail_vacation_getno sensitive capability
  • gog_gmail_vacation_updateno sensitive capability

What this scan could not see

Versions 10

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.29.0 latest A 94/100 2 1.13.0 2026-09-07
v2.27.1 A 94/100 2 1.13.0 2026-09-04
v2.27.0 A 94/100 2 1.13.0 2026-09-01
v2.26.0 A 94/100 2 1.13.0 2026-08-29
v2.25.0 A 94/100 2 1.13.0 2026-08-28
Show 5 more versions ↓
v2.24.0 A 94/100 2 1.12.1 2026-08-15
v2.23.2 A 94/100 2 1.12.1 2026-08-14
v2.23.1 A 94/100 2 1.12.1 2026-08-13
v2.22.0 A 94/100 2 1.12.1 2026-08-10
v2.20.0 A 94/100 2 1.12.1 2026-08-09

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/gogcli-mcp-gmail/badge.svg)](https://mcptrustchecker.com/registry/gogcli-mcp-gmail)
HTML
<a href="https://mcptrustchecker.com/registry/gogcli-mcp-gmail"><img src="https://mcptrustchecker.com/registry/gogcli-mcp-gmail/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/gogcli-mcp-gmail/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan gogcli-mcp-gmail --online

Use the free API → How scoring works

More in Communication & Collaboration