mcp-gmail-oauth (flujo-app/mcp-gmail-oauth) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Caution
74/100
27 days ago

mcp-gmail-oauth

A self-hostable Gmail MCP server that enables Gmail search/read, sending, replies, drafts, labels, and attachment downloads via MCP tools with OAuth authorization. Supports stdio and streamable HTTP transports.

→ flujo-app/mcp-gmail-oauth· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. 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

flujo-app

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
⚠️
Tests do not pass
Either the test suite is broken or the code regressed. Either way the published behaviour can’t be verified by the publisher’s own tests.
✅
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: MCP_GMAIL_ENCRYPTION_KEY
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.
configGOOGLE_OAUTH_CLIENT_FILE/run/secrets/google-web-client.json \
configMCP_GMAIL_ALLOWED_HOSTSExtra allowed hostname repeat --allowed-host <hostname> (comma-separated) public-origin hostname
configMCP_GMAIL_ALLOW_INSECURE_HTTPInsecure loopback HTTP --allow-insecure-http (true\false\1\0) false
configMCP_GMAIL_DB_PATH/var/lib/mcp-gmail-oauth/mcp-gmail-oauth.sqlite \
🔐 secretMCP_GMAIL_ENCRYPTION_KEY'<32-byte-base64url-or-64-hex-secret>' \
configMCP_GMAIL_LISTEN127.0.0.1:3000 \
configMCP_GMAIL_LOCAL_USER_IDStdio local identity --local-user-id <id> local
configMCP_GMAIL_LOG_LEVELLog level --log-level <level> info
configMCP_GMAIL_OAUTH_DCR_RATE_LIMIT_PER_HOURDCR requests per IP/hour --oauth-dcr-rate-limit-per-hour <count> 10
configMCP_GMAIL_OAUTH_DYNAMIC_CLIENT_LIMITUnverified DCR client cap --oauth-dynamic-client-limit <count> 1000
configMCP_GMAIL_OAUTH_DYNAMIC_CLIENT_MAX_IDLE_DAYSDCR inactive age --oauth-dynamic-client-max-idle-days <days> 30
configMCP_GMAIL_OAUTH_GLOBAL_DCR_RATE_LIMIT_PER_HOURDCR requests total/hour --oauth-global-dcr-rate-limit-per-hour <count> 100
configMCP_GMAIL_OAUTH_GLOBAL_RATE_LIMIT_PER_MINUTERequests total/minute --oauth-global-rate-limit-per-minute <count> 10000
configMCP_GMAIL_OAUTH_MAX_CONCURRENTIn-flight requests total --oauth-max-concurrent <count> 128
configMCP_GMAIL_OAUTH_MAX_CONCURRENT_PER_IPIn-flight requests per IP --oauth-max-concurrent-per-ip <count> 8
configMCP_GMAIL_OAUTH_RATE_LIMIT_PER_MINUTERequests per IP/minute --oauth-rate-limit-per-minute <count> 120
configMCP_GMAIL_OAUTH_TRUSTED_PROXY_HOPSTrusted proxy hops --oauth-trusted-proxy-hops <count> 0
configMCP_GMAIL_PUBLIC_BASE_URLExternal origin --public-base-url <origin> derived listener origin in HTTP mode
configMCP_GMAIL_TRANSPORTTransport --transport stdio\http\remote stdio
// 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

18/18 tools missing one or more hints — gmail_search_messages (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); gmail_get_message (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); gmail_get_thread (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +15 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.

Tool inputs are validated

Only 0/18 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool test coverage

Only 2/18 tools referenced in tests (11%)

Write tests that reference each tool by name so every tool has at least one test.

Tests pass

npm test failed — tests do not pass

Make sure npm test runs cleanly. Common cause: missing build step or missing env vars.

Shell command execution

2 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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 6 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 Verified](https://m8ven.ai/badge/mcp/flujo-app-mcp-gmail-oauth-1e2y01?variant=verified)](https://m8ven.ai/mcp/flujo-app-mcp-gmail-oauth-1e2y01)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 87948890f43a3e71fe43ebddc035ad10a217af3f
code hash: 8f02eb473ceb17a00dec5ccdf9c358a11e42fd1e770606a6fe8ced939b46d7c2
verified: 8/3/2026, 10:19:06 AM
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