gmail-mcp-local (alexpekach/gmail-mcp-local) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 20 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
1 month ago

gmail-mcp-local

Local-first Gmail MCP server using PKCE + loopback OAuth flow that stores refresh tokens in the OS keychain, enabling secure read/write Gmail access via MCP tools without tokens leaving the device.

→ alexpekach/gmail-mcp-local· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

alexpekach

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: GMAIL_MCP_CLIENT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configGMAIL_MCP_CLIENT_ID1. Env vars — , GMAIL_MCP_CLIENT_SECRET (set them in the "env" block of the entry above if you prefer everything in one file)
🔐 secretGMAIL_MCP_CLIENT_SECRET1. Env vars — GMAIL_MCP_CLIENT_ID, (set them in the "env" block of the entry above if you prefer everything in one file)
configGMAIL_MCP_CONFIGOther knobs: GMAIL_MCP_SCOPES (override requested scopes), (alternate config path), GMAIL_MCP_METADATA (alternate accounts metadata path).
configGMAIL_MCP_METADATAOther knobs: GMAIL_MCP_SCOPES (override requested scopes), GMAIL_MCP_CONFIG (alternate config path), (alternate accounts metadata path).
configGMAIL_MCP_SCOPESOther knobs: (override requested scopes), GMAIL_MCP_CONFIG (alternate config path), GMAIL_MCP_METADATA (alternate accounts metadata path).
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

20/20 tools missing one or more hints — list_accounts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); connect_account (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); remove_account (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Secrets not logged

2 secret values sent to console.log

Redact or omit secret values from log output.

Domain consistency

npm scope @alepek doesn't match GitHub owner alexpekach

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/alexpekach/gmail-mcp-local)](https://m8ven.ai/mcp/alexpekach/gmail-mcp-local)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: af28b0a3c62dc6f67eb6cfc96409e0e1a95f14e7
code hash: 597b44ec103b12622de6c10931ebd22291a0eb5a4a667ae3ee11a78361f1c2d3
verified: 8/6/2026, 2:54:59 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client