Gmail (domdomegg) MCP Server
gmail-mcp
npm
v2.4.0
Published by domdomegg — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for Gmail - read, send, archive, and manage emails
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 − 4 = 96. 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 |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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 1
medium Hardcoded egress to an external endpoint (dist/utils/token-cache.js)MTC-SRC-003
In the server's implementation (`dist/utils/token-cache.js:49`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. 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 response = await fetch(`https://oauth2.googleapis.com/tokeninfo?access_token=${token}`); if (!response.ok
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/utils/token-cache.js
Tools 36
Each tool and what it can reach — statically extracted from the published source.
messages_listingests untrusted inputattachment_getno sensitive capabilitydraft_createno sensitive capabilitydraft_deleteno sensitive capabilitydraft_getno sensitive capabilitydraft_sendno sensitive capabilitydraft_updateno sensitive capabilitydrafts_listno sensitive capabilityfilter_createno sensitive capabilityfilter_deleteno sensitive capability
Show 26 more tools ↓
filter_getno sensitive capabilityfilters_listno sensitive capabilityget_profileno sensitive capabilitylabel_createno sensitive capabilitylabel_deleteno sensitive capabilitylabel_getno sensitive capabilitylabel_updateno sensitive capabilitylabels_listno sensitive capabilitymessage_archiveno sensitive capabilitymessage_deleteno sensitive capabilitymessage_forwardno sensitive capabilitymessage_getno sensitive capabilitymessage_modifyno sensitive capabilitymessage_sendno sensitive capabilitymessage_trashno sensitive capabilitymessage_untrashno sensitive capabilitymessages_batch_deleteno sensitive capabilitymessages_batch_modifyno sensitive capabilitythread_deleteno sensitive capabilitythread_getno sensitive capabilitythread_modifyno sensitive capabilitythread_trashno sensitive capabilitythread_untrashno sensitive capabilitythreads_listno sensitive capabilityvacation_getno sensitive capabilityvacation_setno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (36 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 | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.4.0 latest |
A 96/100 | 1 | 1.13.0 | 2026-09-07 |
v2.3.2 |
A 96/100 | 1 | 1.12.1 | 2026-07-27 |
v2.3.1 |
A 96/100 | 1 | 1.8.0 | 2026-07-23 |
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.
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 gmail-mcp --onlineOther implementations of Gmail 26
Independent packages implementing the same tool, scanned with the same engine. Compare all 27 side by side →
Gmail MCP server — scope-gated tools + attachment/download path jails + supply-chain hardening. Fork of GongRzhe/Gmail-MCP-Server via ArtyMcLabin's intermediate fork.
Lean Gmail MCP server with auto authentication support (maintained fork of GongRzhe/Gmail-MCP-Server)
MCP server for Gmail — read, search, send, reply, and manage emails via AI agents
MCP server for Gmail - let AI agents send, read, and search email
MCP server for Gmail API with OAuth2 authentication and comprehensive email management
A Model Context Protocol (MCP) server for Gmail integration
More in Communication & Collaboration
One key, 100+ models — chat with any LLM and generate video, images, speech. Free trial at 370.ai.
Retired compatibility stub for the AgentCanary MCP server. Daily briefs continue on X and Telegram.
A Backstage plugin that provides a chat interface for interacting with the MCP Servers.
Signal-first Bitcoin intelligence: sovereign, hiring & hashrate signals over MCP.
WhatsApp® reminders and rescheduling for Calendly. Public read-only MCP endpoint.
Open Source Generic MCP Client for testing & evaluating mcp servers and agents