cherry-studio-chat (sizzlebop/cherry-studio-chat) is an MCP server listed on the M8ven Trust Index. It scores 63 out of 100, grade C. It declares 11 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Warning
63/100

cherry-studio-chat

🍒 Cherry Studio is a desktop client that supports for multiple LLM providers.

→ sizzlebop/cherry-studio-chat· listed on github_code

Warning. Serious findings were identified. Review the full report before connecting. 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

sizzlebop

Source: github_code

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

GitHub

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
🚨
Code appears obfuscated
1 file are unreadable to a human reviewer. Cannot audit what they do.
🚨
Known vulnerabilities in dependencies: 2 critical, 13 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 1 credential: DIDI_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes11 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

List available MCP tools from all active servers. Results are paginated via limit/offset.

inspect

Get a single tool's signature as a JSDoc stub. Use this before `invoke` or `exec`.

invoke

Call a single tool with parameters. Prefer `inspect` first to confirm parameters.

exec

Execute JavaScript code to orchestrate multiple tool calls. Use `mcp.callTool(name, params)` inside the code. IMPORTANT: you MUST explicitly `return` the final value.

maps_textsearch

Search for POI locations based on keywords and city

taxi_cancel_order

Cancel a taxi order

taxi_create_order

Create taxi order directly via API without opening any app interface

taxi_estimate

Get available ride-hailing vehicle types and fare estimates

taxi_generate_ride_app_link

Generate deep links to open ride-hailing apps based on origin, destination and vehicle type

taxi_get_driver_location

Get real-time driver location for a taxi order

taxi_query_order

Query taxi order status and information such as driver contact, license plate, ETA

// known CVEs in dependencies2 critical13 high4 medium12 low

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

critical@vitest/browser@3.2.4GHSA-g8mr-85jm-7xhm

Vitest Browser: Exposed Browser Mode API Can Proxy CDP and Overwrite Config Files, Leading to RCE

critical@vitest/browser@3.2.4GHSA-p63j-vcc4-9vmv

@vitest/browser: Browser Mode provider commands bypass the file-access permission gate

highsharp@0.34.3GHSA-f88m-g3jw-g9cj

sharp inherited vulnerabilities in libvips: CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591

high@langchain/core@1.0.2GHSA-r399-636x-v7f6

LangChain serialization injection vulnerability enables secret extraction

highadm-zip@0.4.16GHSA-xcpc-8h2w-3j85

adm-zip: Crafted ZIP file triggers 4GB memory allocation

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.
configCHERRY_AUTO_ALLOW_TOOLS
🔐 secretDIDI_API_KEY
// 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

11/11 tools missing one or more hints — list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); inspect (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); invoke (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 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 test coverage

4/11 tools referenced in tests (36%)

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

Readable source code

1 file are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

Production dependencies are patched

0 critical, 1 high severity in production deps — sharp@0.34.3 (high)

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

Dev dependencies

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

Upgrade dev dependencies when convenient.

Dependency freshness

3/19 production deps abandoned (no release in 2+ years): graceful-fs@2023-06-09 (3.2y), gray-matter@2023-07-12 (3.1y), swagger-ui-express@2024-05-31 (2.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 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/sizzlebop/cherry-studio-chat?variant=verified)](https://m8ven.ai/mcp/sizzlebop/cherry-studio-chat)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 7ef5a732ec136ff6d993c5b8ffc561e138b8d720
code hash: b1139ab62ded0af1fc737aa0f7205471afdd8e191e6199b517cb5ac3d585003a
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