Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Gmail MCP

NPM · @RENZO.JOHNSON/GMAIL-MCP

Gmail MCP server: list, read, search and send email, manage drafts and labels.

+4 this week 67 Trust /100

Last scanned (13 hours ago)

Scores higher than 38% of npm servers

Category Communication

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 371 tokens (~61/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "gmail_send" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 63

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@renzo.johnson/gmail-mcp@26.11.14

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~371 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
gmail_admin ~111

Gmail administration. Actions: create_draft(to, subject, body), update_draft(draft_id, to, subject, body), add_label(message_id, label_id), remove_label(message_id, label_id), create_label(name), mark_read(message_id), mark_unread(message_id), untrash(message_id). Destructive (confirm:true): delete_draft(draft_id), delete_label(label_id), trash(message_id).

NameTypeReqDescription
actionstringyesAdmin action
paramsobject–Action parameters

No output schema declared.

No examples provided.

gmail_list ~91

Lists recent emails from Gmail inbox with metadata (from, to, subject, date, snippet).

NameTypeReqDescription
label_idsarray–Filter by label IDs (e.g. ["INBOX", "UNREAD"])
max_resultsnumber–Max messages to return (default 20)
querystring–Gmail search query (e.g. "is:unread", "from:user@example.com")

No output schema declared.

No examples provided.

gmail_read ~37

Reads a full email message by ID. Returns headers, body text, and attachment list.

NameTypeReqDescription
message_idstringyesGmail message ID

No output schema declared.

No examples provided.

gmail_search ~51

Searches Gmail using query syntax. Returns matching messages with metadata.

NameTypeReqDescription
max_resultsnumber–Max results (default 20)
querystringyesGmail search query (same syntax as Gmail search bar)

No output schema declared.

No examples provided.

gmail_send ~67

Sends an email from your Gmail account.

NameTypeReqDescription
bccstring–BCC recipients
bodystringyesPlain text email body
ccstring–CC recipients
subjectstringyesEmail subject line
tostringyesRecipient email address

No output schema declared.

No examples provided.

ping ~14

Checks server connectivity and auth status

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Gmail MCP server?

Gmail MCP runs locally as an npm package, launched with npx -y @renzo.johnson/gmail-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @renzo.johnson/gmail-mcp

# add to Claude Code
claude mcp add com-renzojohnson-gmail-mcp -- npx -y @renzo.johnson/gmail-mcp
Common questions

What is the Gmail MCP server?

Gmail MCP is listed in the public MCP registry as com.renzojohnson/gmail-mcp. Gmail MCP server: list, read, search and send email, manage drafts and labels. This page covers its npm package (@renzo.johnson/gmail-mcp).

Is the Gmail MCP server safe to use?

Gmail MCP scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Gmail MCP server expose?

Gmail MCP exposes 6 tools: ping, gmail_list, gmail_read, gmail_search, gmail_send, gmail_admin. Their descriptions and schemas cost roughly 371 tokens of context every time the server is loaded.

Is the Gmail MCP server still maintained?

Gmail MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Gmail MCP server under?

Gmail MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Gmail MCP server?

VerifyMCP ran 15 checks on Gmail MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Gmail MCP: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.