Zoho CRM MCP Server (whiteside-daniel/zohocrm-mcpserver) is an MCP server listed on the M8ven Trust Index. It scores 43 out of 100, grade D. It declares 7 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
43/100

Zoho CRM MCP Server

Enables read-only interaction with Zoho CRM data through natural language queries, allowing users to search records, list modules, retrieve field information, and count records using secure OAuth authentication.

→ whiteside-daniel/zohocrm-mcpserver· 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

whiteside-daniel

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
1 flow detected: ZOHO_CLIENT_SECRET. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Known vulnerabilities in dependencies: 15 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.

validate-zoho-oauth

This will validate whether or not the user has a token already. If so you should be able to use the other endpoints.

setup-zoho-oauth

Before you can use the other tools, you must authorize your Zoho Account with the proper scopes and permissions. The user must visit this link to authorize Zoho, then get redirected to this application. You can also use this to re-authorize and get a new token if something has gone wrong.

zoho-modules-list-all

Get a list of all the modules and their API names from CRM

zoho-module-list-fields

Get a list of all the fields and their API names for a module. Search by Module API Name

simple-search-zoho-records

Search Zoho CRM Records using the API. Search using the Module API Name and a Search String

count-zoho-records

Fetch the total number of records in the module, or fetch the number of records that match a criteria. Count filters can be custom view ID, criteria, email, phone number, or a word in the record. For a total count, set count_type='total' and search_value=''. Criteria pattern is (API_NAME:operator:va…

get-zoho-record

Get a record from any Zoho CRM Module by the record id.

// known CVEs in dependencies15 high5 medium10 low

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

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

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

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

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

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

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

highaxios@1.10.0GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.10.0GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

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.
configDEV_TOKEN_PATH
configSCOPES
configZOHO_CLIENT_IDYOURCLIENTID - Your actual Zoho Client ID
🔐 secretZOHO_CLIENT_SECRETYOURCLIENTSECRET - Your actual Zoho Client Secret
🔐 secretZOHO_REFRESH_TOKEN
// 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 — validate-zoho-oauth (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); setup-zoho-oauth (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); zoho-modules-list-all (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

4/7 tool handlers declare input schemas (57%)

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

License file

No license file

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

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets not logged

1 secret value sent to error

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 15 high severity in production deps — @modelcontextprotocol/sdk@1.14.0 (high), @modelcontextprotocol/sdk@1.14.0 (high)

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

Dependency freshness

1/7 production deps stale: path@2023-05-20 (3.3y)

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 7 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/whiteside-daniel/zohocrm-mcpserver?variant=verified)](https://m8ven.ai/mcp/whiteside-daniel/zohocrm-mcpserver)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 95e74fad53b5a835fbaed39065eac6c58da7ed68
code hash: 74947d2973d4a9c7be5dba1c4fbbc660030f3d048aaac93ea69dfe5cd716a5b3
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