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.

com.mcparmory/google-gmail

OCI · GHCR.IO/MCPARMORY/GOOGLE-GMAIL:1.0.4 · 2 COMPONENTS · SCANNED SEP 20

Send, read, organize emails, manage labels, drafts, and filters

0 this week 49 Trust /100
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 Security0
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 8935 tokens (~141/item across 63 items; 63 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 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 Safety89
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 11 of 19 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_draft" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
  • An AI judge read all 63 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the com.mcparmory/google-gmail MCP server?

com.mcparmory/google-gmail runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/google-gmail:1.0.4. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/mcparmory/google-gmail:1.0.4

# add to Claude Code
claude mcp add com-mcparmory-google-gmail -- docker run --rm -i ghcr.io/mcparmory/google-gmail:1.0.4
// .cursor/mcp.json
{
  "mcpServers": {
    "com-mcparmory-google-gmail": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/google-gmail:1.0.4"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-mcparmory-google-gmail": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/google-gmail:1.0.4"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-mcparmory-google-gmail -- docker run --rm -i ghcr.io/mcparmory/google-gmail:1.0.4
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mcparmory-google-gmail": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/google-gmail:1.0.4"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  com-mcparmory-google-gmail:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/mcparmory/google-gmail:1.0.4"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-mcparmory-google-gmail": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/google-gmail:1.0.4"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "com-mcparmory-google-gmail": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/google-gmail:1.0.4"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1

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

  • 19 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 18 Sept 26 +1
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

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

  • 13 Sept 26 +1

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

  • 12 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 11 Sept 26 +1
    • Stability: 0.97 → pass security
  • 9 Sept 26 +1

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

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 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/google-gmail:1.0.4

Provenance No attestation

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

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 63 exposed · ~8,935 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
send_draft ~314

Sends an existing draft message to recipients specified in the To, Cc, and Bcc headers. The draft must already exist and contain valid recipient information.

NameTypeReqDescription
classificationLabelValuesarrayClassification label values to apply to the message. Each classification label ID must be unique; duplicate IDs will be deduplicated arbitrarily. Only available for Google Workspace accounts.
email_bccstringBlind carbon copy recipients (Bcc header), comma-separated
email_bodystringEmail body content (plain text or HTML)
email_body_is_htmlbooleanWhether email_body is HTML (True) or plain text (False)
email_ccstringCarbon copy recipients (Cc header), comma-separated
email_fromstringSender email address (From header)
email_in_reply_tostringIn-Reply-To header (Message-ID of original message)
email_referencesstringReferences header (Message-IDs of related messages), space-separated
email_reply_tostringReply-To header address
email_subjectstringEmail subject line
email_tostringRecipient email address (To header)
idstringThe immutable ID of the draft.
labelIdsarrayList of label IDs to apply to this message. Labels are applied in the order provided.
userIdstringyesThe user's email address or the special value `me` to indicate the authenticated user.

No output schema declared.

No examples provided.

send_message ~307

Sends an email message to recipients specified in the To, Cc, and Bcc headers. The message is delivered immediately to all specified recipients.

NameTypeReqDescription
classificationLabelValuesarrayClassification labels to apply to the message for organizational purposes. Each classification label ID must be unique; duplicate IDs will be deduplicated arbitrarily. Only available for Google Works…
email_bccstringBlind carbon copy recipients (Bcc header), comma-separated
email_bodystringEmail body content (plain text or HTML)
email_body_is_htmlbooleanWhether email_body is HTML (True) or plain text (False)
email_ccstringCarbon copy recipients (Cc header), comma-separated
email_fromstringSender email address (From header)
email_in_reply_tostringIn-Reply-To header (Message-ID of original message)
email_referencesstringReferences header (Message-IDs of related messages), space-separated
email_reply_tostringReply-To header address
email_subjectstringEmail subject line
email_tostringRecipient email address (To header)
labelIdsarrayIDs of labels to apply to the message. Labels help organize and categorize messages in Gmail.
userIdstringyesThe email address of the user sending the message. Use the special value `me` to refer to the authenticated user.

No output schema declared.

No examples provided.

send_verification_email_to_send_as_alias ~90

Sends a verification email to a send-as alias address to confirm ownership. The alias must have a pending verification status and requires service account with domain-wide delegation authority.

NameTypeReqDescription
sendAsEmailstringyesThe send-as alias email address that requires verification.
userIdstringyesThe user's email address. Use the special value 'me' to refer to the authenticated user.

No output schema declared.

No examples provided.

set_default_smime_config ~116

Sets the default S/MIME configuration for the specified send-as alias. This determines which S/MIME certificate will be used by default when sending emails from this alias.

NameTypeReqDescription
idstringyesThe immutable identifier for the S/MIME configuration to set as default.
sendAsEmailstringyesThe email address that appears in the From header for mail sent using this send-as alias.
userIdstringyesThe user's email address. Use the special value `me` to refer to the authenticated user.

No output schema declared.

No examples provided.

update_cse_identity_keypair ~115

Associates a new key pair with an existing client-side encryption identity. The updated key pair must validate against Google's S/MIME certificate profiles. Requires either domain-wide delegation authority for administrators or hardware key encryption enabled for individual users.

NameTypeReqDescription
emailAddressstringThe email address for the sending identity. Must be the primary email address of the authenticated user.
userIdstringyesThe user identifier. Use the special value `me` to refer to the authenticated user, or provide the user's primary email address.

No output schema declared.

No examples provided.

update_draft ~327

Updates the content of an existing draft message. Replaces the draft's message body and metadata with the provided values.

NameTypeReqDescription
classificationLabelValuesarrayClassification label values to apply to the message. Each classification label ID must be unique; duplicate IDs will be deduplicated arbitrarily. Only available for Google Workspace accounts. Classif…
email_bccstringBlind carbon copy recipients (Bcc header), comma-separated
email_bodystringEmail body content (plain text or HTML)
email_body_is_htmlbooleanWhether email_body is HTML (True) or plain text (False)
email_ccstringCarbon copy recipients (Cc header), comma-separated
email_fromstringSender email address (From header)
email_in_reply_tostringIn-Reply-To header (Message-ID of original message)
email_referencesstringReferences header (Message-IDs of related messages), space-separated
email_reply_tostringReply-To header address
email_subjectstringEmail subject line
email_tostringRecipient email address (To header)
idstringyesThe unique identifier of the draft message to update.
labelIdsarrayList of label IDs to apply to this message. Labels are used to organize and categorize messages in Gmail.
userIdstringyesThe user's email address. Use the special value `me` to refer to the authenticated user.

No output schema declared.

No examples provided.

update_label ~180

Updates an existing Gmail label with new properties such as display name and visibility settings. Only user-created labels can be modified; system labels cannot be changed.

NameTypeReqDescription
idstringyesThe unique identifier of the label to update.
labelListVisibilitystringControls whether the label appears in the label list in Gmail's web interface.
messageListVisibilitystringControls whether messages with this label are visible in the message list in Gmail's web interface.
namestringThe display name of the label as shown to the user in Gmail.
typestringThe owner type of the label. User labels can be modified and deleted; system labels are managed by Gmail and cannot be altered.
userIdstringyesThe user's email address. Use the special value `me` to refer to the authenticated user.

No output schema declared.

No examples provided.

update_label_partial ~195

Update properties of a Gmail label using partial update semantics. Modify visibility settings, display name, or other label attributes without replacing the entire label configuration.

NameTypeReqDescription
idstringyesThe unique identifier of the label to update.
labelListVisibilitystringControls whether this label appears in the label list within Gmail's web interface.
messageListVisibilitystringControls whether messages with this label are visible in the message list within Gmail's web interface.
namestringThe human-readable name displayed for this label in the Gmail interface.
typestringIndicates whether this is a system label (created and managed by Gmail) or a user label (created and managed by the user). System labels cannot be modified or deleted, while user labels can be fully…
userIdstringyesThe user's email address. Use the special value `me` to refer to the authenticated user.

No output schema declared.

No examples provided.

update_message_labels ~148

Updates the labels applied to a specific message by adding and/or removing label IDs. You can modify up to 100 labels per request.

NameTypeReqDescription
addLabelIdsarrayA list of label IDs to add to the message. Maximum of 100 labels can be added in a single request.
idstringyesThe unique identifier of the message to modify.
removeLabelIdsarrayA list of label IDs to remove from the message. Maximum of 100 labels can be removed in a single request.
userIdstringyesThe email address of the user whose message will be modified. Use the special value `me` to refer to the authenticated user.

No output schema declared.

No examples provided.

update_message_labels_batch ~128

Modifies labels on specified messages by adding and/or removing label IDs. Supports batch operations on up to 1000 messages per request.

NameTypeReqDescription
addLabelIdsarrayLabel IDs to add to the specified messages. Order is not significant.
idsarrayThe message IDs to modify. Maximum of 1000 IDs per request.
removeLabelIdsarrayLabel IDs to remove from the specified messages. Order is not significant.
userIdstringyesThe user's email address. Use the special value `me` to refer to the authenticated user.

No output schema declared.

No examples provided.

update_send_as_alias ~447

Updates a send-as alias configuration for a Gmail account, including display name, reply-to address, and optional HTML signature. Service accounts with domain-wide delegation can update non-primary addresses; standard users can only modify their own aliases.

NameTypeReqDescription
displayNamestringThe display name shown in the 'From:' header for messages sent using this alias. If empty for custom addresses, Gmail will use the primary account's name. Updates to this field may be silently ignore…
hoststringThe hostname of the SMTP server used for sending mail through this alias.
isDefaultbooleanWhether this alias is the default 'From:' address for new messages and auto-replies. Only 'true' can be written; setting this to true automatically sets the previous default address to false. Every G…
passwordstringThe password for SMTP authentication. This write-only field is used only during creation or updates and is never returned in responses.
portstringThe port number of the SMTP server.
replyToAddressstringAn optional email address to include in the 'Reply-To:' header for messages sent using this alias. Leave empty to omit the 'Reply-To:' header.
securityModestringThe security protocol for SMTP communication.
sendAsEmailstringThe email address displayed in the 'From:' header for messages sent using this alias. This field is read-only and cannot be modified after creation.
signaturestringAn optional HTML signature appended to new emails composed with this alias in Gmail's web interface. Gmail will sanitize the HTML before saving.
treatAsAliasbooleanWhether Gmail should treat this address as an alias for the user's primary email address. This setting applies only to custom 'from' aliases.
userIdstringyesThe Gmail user's email address. Use the special value 'me' to refer to the authenticated user.
usernamestringThe username for SMTP authentication. This write-only field is used only during creation or updates and is never returned in responses.

No output schema declared.

No examples provided.

update_send_as_alias_partial ~473

Partially update a send-as alias configuration for a Gmail account. Use this to modify display name, default status, reply-to address, signature, SMTP settings, or alias treatment without replacing the entire resource.

NameTypeReqDescription
displayNamestringThe display name shown in the 'From:' header for messages sent using this alias. If empty, Gmail uses the primary account's name. Updates may be silently ignored if the admin has restricted name form…
hoststringThe hostname of the SMTP server used to send mail through this alias.
isDefaultbooleanSet to true to make this the default 'From:' address for new messages and auto-replies. Only true is a valid value for updates; setting this true automatically sets the previous default to false.
passwordstringThe password for SMTP authentication. This write-only field is never returned in responses and must be provided when configuring SMTP settings.
portstringThe port number of the SMTP server. Common values are 25, 465, or 587 depending on the security mode.
replyToAddressstringAn optional email address to include in the 'Reply-To:' header for messages sent using this alias. Leave empty to omit the Reply-To header.
securityModestringThe security protocol for SMTP communication. Determines how the connection to the SMTP server is encrypted or secured.
sendAsEmailstringThe email address displayed in the 'From:' header for messages sent using this alias. This field is read-only for updates and can only be set during alias creation.
signaturestringAn optional HTML signature appended to new emails composed with this alias in Gmail's web interface. This signature is not added to replies or forwarded messages.
treatAsAliasbooleanWhether Gmail should treat this address as an alias for the user's primary email address. This setting only applies to custom 'from' aliases and affects how Gmail handles replies and threading.
userIdstringyesThe Gmail account identifier. Use 'me' to refer to the authenticated user, or provide a specific email address.
usernamestringThe username for SMTP authentication. This write-only field is never returned in responses and must be provided when configuring SMTP settings.

No output schema declared.

No examples provided.

update_thread_labels ~134

Modifies the labels applied to a thread, affecting all messages within it. Supports adding and removing labels in a single operation.

NameTypeReqDescription
addLabelIdsarrayA list of label IDs to add to this thread. Up to 100 labels can be added per request.
idstringyesThe ID of the thread to modify.
removeLabelIdsarrayA list of label IDs to remove from this thread. Up to 100 labels can be removed per request.
userIdstringyesThe user's email address. Use the special value `me` to refer to the authenticated user.

No output schema declared.

No examples provided.

Common questions

What is the com.mcparmory/google-gmail MCP server?

com.mcparmory/google-gmail is an MCP server listed in the public MCP registry as com.mcparmory/google-gmail. Send, read, organize emails, manage labels, drafts, and filters. This page covers its container image (ghcr.io/mcparmory/google-gmail:1.0.4).

Is the com.mcparmory/google-gmail MCP server safe to use?

com.mcparmory/google-gmail scores 49 out of 100 on VerifyMCP. 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 com.mcparmory/google-gmail MCP server expose?

com.mcparmory/google-gmail exposes 63 tools: get_profile, list_drafts, create_draft, get_draft, update_draft, and 58 more. Their descriptions and schemas cost roughly 8,935 tokens of context every time the server is loaded.

Is the com.mcparmory/google-gmail MCP server still maintained?

com.mcparmory/google-gmail is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.