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

io.github.markswendsen-code/gmail

NPM · @STRIDERLABS/MCP-GMAIL · SCANNED AUG 3

Gmail MCP server — send, read, and search email. By Strider Labs.

+19 this week 65 Trust /100
Trust breakdown (6 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 →

Supply Chain Security79
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects uuid 9.0.1, reached via googleapis > googleapis-common > uuid. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (119 of 123), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 267 tokens (~66/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @striderlabs/mcp-gmail

# add to Claude Code
claude mcp add markswendsen-code-gmail -- npx -y @striderlabs/mcp-gmail
# add to Codex CLI
codex mcp add markswendsen-code-gmail -- npx -y @striderlabs/mcp-gmail
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "markswendsen-code-gmail": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@striderlabs/mcp-gmail"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add markswendsen-code-gmail --command npx --arg -y --arg @striderlabs/mcp-gmail
# ~/.hermes/config.yaml
mcp_servers:
  markswendsen-code-gmail:
    command: "npx"
    args: ["-y", "@striderlabs/mcp-gmail"]
// mcp.json
{
  "mcpServers": {
    "markswendsen-code-gmail": {
      "command": "npx",
      "args": [
        "-y",
        "@striderlabs/mcp-gmail"
      ]
    }
  }
}
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.

  • 2 Aug 26 +60
    • CVE-2026-41907 affects this package: high security
    • Provenance: unverified → fail security
    • Known CVEs: unverified → fail security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Tool coverage: unverified → 100 functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Stability: unverified → 0.20 functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Schema quality: unverified → good functional
    • Licence: MIT functional
  • 1 Aug 26 −16
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 31 Jul 26 −7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 46

    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 3 Aug 2026 · Analysed npm/@striderlabs/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
Dependencies 119 packages

119 packages in the resolved dependency tree · 119 deprecated · 38 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 4 exposed · ~267 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.

Tool Tokens
gmail_list ~70

List recent emails from the inbox. Use this to see what emails the user has received.

NameTypeReqDescription
labelstringFilter by label (e.g., "INBOX", "UNREAD", "STARRED")
maxResultsnumberMaximum number of emails to list (default: 10)

No output schema declared.

No examples provided.

gmail_read ~35

Read the full content of a specific email by its message ID.

NameTypeReqDescription
messageIdstringyesThe Gmail message ID to read

No output schema declared.

No examples provided.

gmail_search ~69

Search emails in the user's Gmail inbox using Gmail search syntax. Use this to find specific emails.

NameTypeReqDescription
maxResultsnumberMaximum number of results to return (default: 10)
querystringyesGmail search query (e.g., "from:[email protected] subject:meeting")

No output schema declared.

No examples provided.

gmail_send ~93

Send an email from the user's Gmail account. Use this when the user wants to send an email to someone.

NameTypeReqDescription
bccstringBCC recipients (comma-separated, optional)
bodystringyesEmail body content (plain text)
ccstringCC recipients (comma-separated, optional)
subjectstringyesEmail subject line
tostringyesRecipient email address

No output schema declared.

No examples provided.