Gmail (d-mato) MCP Server

@d-mato/gmail-mcp npm v0.2.1 Source verified

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

MCP server for Gmail - search, read, archive, and manage your email

View on npm ↗ Repository ↗ Raw report (JSON) ↗

Trust grade

97/100

Last scanned 2026-09-07 get badge →

Trust

A · 97/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

Moderate

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.

A Why this grade threat 100 − adoption risk = 97/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 − 3 = 97. 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:

Points	Adoption-risk factor
−3	capability blast radius (moderate) — 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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 21

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

gmail_get_attachmentingests untrusted input
gmail_add_labelno sensitive capability
gmail_archiveno sensitive capability
gmail_archive_threadno sensitive capability
gmail_batch_archiveno sensitive capability
gmail_batch_trashno sensitive capability
gmail_create_labelno sensitive capability
gmail_delete_labelno sensitive capability
gmail_get_messageno sensitive capability
gmail_get_threadno sensitive capability

Show 11 more tools ↓

gmail_list_labelsno sensitive capability
gmail_mark_readno sensitive capability
gmail_mark_thread_readno sensitive capability
gmail_mark_thread_unreadno sensitive capability
gmail_mark_unreadno sensitive capability
gmail_remove_labelno sensitive capability
gmail_searchno sensitive capability
gmail_trashno sensitive capability
gmail_trash_threadno sensitive capability
gmail_untrashno sensitive capability
gmail_untrash_threadno sensitive capability

What this scan could not see

Tools were statically extracted from the published source (21 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Versions 3

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.

Version	Score	Engine	Scanned
`v0.2.1` latest	A 97/100	1.13.0	2026-09-07
`v0.2.0`	A 97/100	1.12.1	2026-08-14
`v0.1.10`	A 100/100	1.12.1	2026-08-02

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.

Markdown (GitHub README)

[![MCP Trust Score](https://mcptrustchecker.com/registry/d-mato-gmail-mcp/badge.svg)](https://mcptrustchecker.com/registry/d-mato-gmail-mcp)

HTML

<a href="https://mcptrustchecker.com/registry/d-mato-gmail-mcp"><img src="https://mcptrustchecker.com/registry/d-mato-gmail-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>

Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/d-mato-gmail-mcp/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 @d-mato/gmail-mcp --online

Use the free API → How scoring works

Other implementations of Gmail 26

Independent packages implementing the same tool, scanned with the same engine. Compare all 27 side by side →

Gmail (klodr) Source verified npm

@klodr/gmail-mcp

Gmail MCP server — scope-gated tools + attachment/download path jails + supply-chain hardening. Fork of GongRzhe/Gmail-MCP-Server via ArtyMcLabin's intermediate fork.

Communication & Collaboration Score 100/100 0 findings 306/wk Cap. Minimal

Gmail (artymclabin) npm

@artymclabin/gmail-mcp

Lean Gmail MCP server with auto authentication support (maintained fork of GongRzhe/Gmail-MCP-Server)

Communication & Collaboration Score 99/100 0 findings 398/wk Cap. Minimal

Gmail (franciscpd) npm

@franciscpd/gmail-mcp-server

MCP server for Gmail — read, search, send, reply, and manage emails via AI agents

Communication & Collaboration Score 99/100 0 findings 87/wk Cap. Minimal

Gmail (striderlabs) npm

@striderlabs/mcp-gmail

MCP server for Gmail - let AI agents send, read, and search email