io.github.markswendsen-code/gmail
NPM · @STRIDERLABS/MCP-GMAIL · SCANNED SEP 20
Gmail MCP server — send, read, and search email. By Strider Labs.
Available components
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 Security89
- 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
- 41 of 120 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 94 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).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 Management93
- Stability observed for 28 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 4 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
How do I install the io.github.markswendsen-code/gmail MCP server?
io.github.markswendsen-code/gmail runs locally as an npm package, launched with npx -y @striderlabs/mcp-gmail. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @striderlabs/mcp-gmail
claude mcp add markswendsen-code-gmail -- npx -y @striderlabs/mcp-gmail
{
"mcpServers": {
"markswendsen-code-gmail": {
"command": "npx",
"args": [
"-y",
"@striderlabs/mcp-gmail"
]
}
}
} {
"servers": {
"markswendsen-code-gmail": {
"command": "npx",
"args": [
"-y",
"@striderlabs/mcp-gmail"
]
}
}
} codex mcp add markswendsen-code-gmail -- npx -y @striderlabs/mcp-gmail
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"markswendsen-code-gmail": {
"type": "local",
"command": [
"npx",
"-y",
"@striderlabs/mcp-gmail"
],
"enabled": true
}
}
} openclaw mcp add markswendsen-code-gmail --command npx --arg -y --arg @striderlabs/mcp-gmail
mcp_servers:
markswendsen-code-gmail:
command: "npx"
args: ["-y", "@striderlabs/mcp-gmail"] {
"McpServers": {
"markswendsen-code-gmail": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@striderlabs/mcp-gmail"
]
}
}
} assistant mcp add markswendsen-code-gmail -t stdio -c npx -a -y @striderlabs/mcp-gmail
{
"mcpServers": {
"markswendsen-code-gmail": {
"command": "npx",
"args": [
"-y",
"@striderlabs/mcp-gmail"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 10 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.
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 npm/@striderlabs/mcp-gmail@0.1.0
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 →
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 |
Background: What a vulnerability scan can and cannot prove →
Dependencies 120 packages
| Packages resolved | 120 |
|---|---|
| Deprecated | 1 |
| Stale | 40 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
gmail_list ~70
List recent emails from the inbox. Use this to see what emails the user has received.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Filter by label (e.g., "INBOX", "UNREAD", "STARRED") |
| maxResults | number | – | Maximum 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.
| Name | Type | Req | Description |
|---|---|---|---|
| messageId | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | number | – | Maximum number of results to return (default: 10) |
| query | string | yes | Gmail search query (e.g., "from:example@gmail.com 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.
| Name | Type | Req | Description |
|---|---|---|---|
| bcc | string | – | BCC recipients (comma-separated, optional) |
| body | string | yes | Email body content (plain text) |
| cc | string | – | CC recipients (comma-separated, optional) |
| subject | string | yes | Email subject line |
| to | string | yes | Recipient email address |
No output schema declared.
No examples provided.
What is the io.github.markswendsen-code/gmail MCP server?
io.github.markswendsen-code/gmail is an MCP server listed in the public MCP registry as io.github.markswendsen-code/gmail. Gmail MCP server, send, read, and search email. By Strider Labs. This page covers its npm package (@striderlabs/mcp-gmail).
Is the io.github.markswendsen-code/gmail MCP server safe to use?
io.github.markswendsen-code/gmail scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 20 September 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 io.github.markswendsen-code/gmail MCP server expose?
io.github.markswendsen-code/gmail exposes 4 tools: gmail_send, gmail_search, gmail_read, gmail_list. Their descriptions and schemas cost roughly 267 tokens of context every time the server is loaded.
Is the io.github.markswendsen-code/gmail MCP server still maintained?
io.github.markswendsen-code/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.
What licence is the io.github.markswendsen-code/gmail MCP server under?
io.github.markswendsen-code/gmail declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.