zoho-multi-mcp (vasparshin/zoho-multi-mcp) is an MCP server listed on the M8ven Trust Index. It scores 58 out of 100, grade D. It declares 7 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
58/100

zoho-multi-mcp

Connects AI assistants to one or more Zoho Mail accounts, enabling read, send, search, reply, and delete operations directly from an AI workflow. Multiple mailboxes can run from a single lightweight process to reduce memory usage.

→ vasparshin/zoho-multi-mcp· 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

vasparshin

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

Glamanot scored here

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
🚨
Secret credentials may flow to a network call
2 flows detected: ZOHO_CLIENT_SECRET. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 2 credentials: ZOHO_CLIENT_SECRET, ZOHO_REFRESH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes7 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

list_folders

List all mail folders with unread/total counts.

list_emails

List emails in a folder (default: Inbox). Returns subject, sender, date, and IDs.

read_email

Read the full content of a specific email. Requires messageId and folderId.

search_emails

Search emails by keyword across all folders.

send_email

Send a new email from your Zoho account.

reply_email

Reply to an existing email. Supports reply and reply-all.

delete_email

Delete an email (moves to trash by default, or permanently with permanent=true).

// known CVEs in dependencies3 high

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

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

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

high@modelcontextprotocol/sdk@1.12.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.12.1GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

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.
configZOHO_ACCOUNTS_JSONJSON array of {id, clientId, clientSecret, refreshToken, datacenter?}
configZOHO_CLIENT_IDOAuth2 Client ID from Zoho API Console
🔐 secretZOHO_CLIENT_SECRETOAuth2 Client Secret
configZOHO_DATACENTERZoho datacenter: eu (default), us, in, au, jp
configZOHO_HTTP_PORTRun as an HTTP server on this port instead of stdio
configZOHO_MULTI_PORT_JSONJSON array of {id, port, name?}; each id must appear in ZOHO_ACCOUNTS_JSON
🔐 secretZOHO_REFRESH_TOKENOAuth2 Refresh Token (generated via setup)
configZOHO_SERVER_NAMELog-line label for stdio / single-port HTTP mode
// 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

7/7 tools missing one or more hints — list_folders (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_emails (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_email (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 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/7 tool handlers declare input schemas (0%)

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

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets not logged

6 secret values sent to error/log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.12.1 (high), @modelcontextprotocol/sdk@1.12.1 (high)

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

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/vasparshin/zoho-multi-mcp?variant=verified)](https://m8ven.ai/mcp/vasparshin/zoho-multi-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 1ef76678457e49e913ef85eb9464a067af73c5a7
code hash: 64da5d11c290f9823d333de81a670d27a3311f36c7ef5152360d8331e285b456
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