MCP Google Multi-Account Server (bkbaheti/google-multi-account-mcp) is an MCP server listed on the M8ven Trust Index. It scores 61 out of 100, grade C. It declares 63 tools. No publisher has claimed this listing.

C
Caution
61/100

MCP Google Multi-Account Server

Enables natural language interaction with multiple Google accounts (Gmail, Drive, Calendar) from MCP-compatible clients like Claude.

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

⚡ 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

bkbaheti

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 →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — gmail_get_attachment (line 1040: mkdirSync(outputDir, { recursive: true }))
🚨
Known vulnerabilities in dependencies: 1 critical, 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 1 credential: GOOGLE_CLIENT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical1 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@4.0.18GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

high@modelcontextprotocol/sdk@1.25.3GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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_CLIENT_IDEnvironment variables: Set and GOOGLE_CLIENT_SECRET
🔐 secretGOOGLE_CLIENT_SECRETEnvironment variables: Set GOOGLE_CLIENT_ID and
configMCP_GOOGLE_CONFIG_PATHOverride default config file location
configMCP_GOOGLE_LOG_EMAIL_CONTENT
configMCP_GOOGLE_LOG_LEVELLog level: debug, info, warn, error
configMCP_GOOGLE_LOG_RECIPIENTS
configMCP_GOOGLE_PASSPHRASEclaude mcp add -s user proGoogleMCP -e =optional-passphrase -- npx -y @procedure-tech/mcp-google
// 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

63/63 tools missing one or more hints — calendar_list_calendars (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); calendar_list_events (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); calendar_get_event (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +60 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.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — gmail_get_attachment (line 1040: mkdirSync(outputDir, { recursive: true }))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

61/63 tool handlers declare input schemas (97%)

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

Tool handlers catch errors

56/63 tool handlers wrap calls in try/catch (89%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 6/63 tools referenced in tests (10%)

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

Production dependencies are patched

0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.25.3 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Domain consistency

npm scope @procedure-tech doesn't match GitHub owner bkbaheti

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

Tool description accuracy

gmail_get_attachment: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

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 11 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/bkbaheti/google-multi-account-mcp?variant=verified)](https://m8ven.ai/mcp/bkbaheti/google-multi-account-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 63f68d6c7807f972644198e0567cc92da212b97f
code hash: 78fc62684c24c6f21f07c76be153afc881002f17d49f6cb250e79254d833c970
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