Gmail (monsoft) MCP Server
@monsoft/mcp-gmail
npm
v0.4.0
Published by @monsoft — 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.
Gmail MCP server with auto authentication support
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 Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([gmail_read_email]) co-exist with external-action tools ([gmail_send_email]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [gmail_read_email] → sinks [gmail_send_email]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow gmail_read_email → gmail_send_email
Tools 26
Each tool and what it can reach — statically extracted from the published source.
gmail_read_emailingests untrusted inputgmail_send_emailnetwork egressgmail_archive_emailno sensitive capabilitygmail_batch_archiveno sensitive capabilitygmail_batch_deleteno sensitive capabilitygmail_batch_mark_as_readno sensitive capabilitygmail_batch_mark_as_unreadno sensitive capabilitygmail_batch_modifyno sensitive capabilitygmail_batch_move_to_trashno sensitive capabilitygmail_create_labelno sensitive capability
Show 16 more tools ↓
gmail_delete_emailno sensitive capabilitygmail_delete_labelno sensitive capabilitygmail_draft_emailno sensitive capabilitygmail_get_forwardingno sensitive capabilitygmail_get_vacation_responderno sensitive capabilitygmail_list_email_labelsno sensitive capabilitygmail_list_emailsno sensitive capabilitygmail_list_emails_with_advanced_filtersno sensitive capabilitygmail_mark_as_readno sensitive capabilitygmail_mark_as_unreadno sensitive capabilitygmail_modify_emailno sensitive capabilitygmail_move_to_trashno sensitive capabilitygmail_recover_from_trashno sensitive capabilitygmail_set_vacation_responderno sensitive capabilitygmail_update_forwardingno sensitive capabilitygmail_update_labelno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (26 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 1
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 |
|---|---|---|---|---|
v0.4.0 latest |
A 96/100 | 1 | 1.13.0 | 2026-09-07 |
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 @monsoft/mcp-gmail --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 Cloud & DevOps
Operator control CLI for AdGuard Home with an MCP adapter
interacting with Aliyun (Alibaba Cloud) services through This MCP server provides tools.
MCP server for the Aspro.Cloud REST API
MCP server for Atlassian Confluence and Jira Cloud APIs
AuroraCloud-first MCP server that exposes AuroraDocs workspace data to Claude Desktop and other AI agents
The official AWS Knowledge Base retrieval server using Bedrock Agent Runtime.