Zendesk MCP Server by Fruggr (fruggr/zendesk-mcp-server) 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
25 days ago

Zendesk MCP Server by Fruggr

A Model Context Protocol (MCP) server that connects LLMs to the Zendesk Support & Help Center APIs — with per-user OAuth 2.1 PKCE authentication and fine-grained tool visibility controls.

→ fruggr/zendesk-mcp-server· 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

fruggr

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
✅
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: ZENDESK_OAUTH_TOKEN
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.
configBIOME_BINARY
configCORS_ORIGIN
configComSpec
configDISPLAY
configHC_RESOURCE_SCHEME
configHOST
configLOG_LEVELRestart with =debug for the full OAuth flow trace.
configPROOT_L2S_DIR
configPUBLIC_URL(ZENDESK_SUBDOMAIN, ZENDESK_TOKEN_FILE, , the attachment-vision
configRUNS
configSYSTEMROOT
configTRANSPORT
configWARMUPS
configWINDIR
configXDG_CACHE_HOME
configXDG_CONFIG_HOME
configZENDESK_MCP_TSC
configZENDESK_OAUTH_CALLBACK_PORT/ --callback-port if you override it; Zendesk
configZENDESK_OAUTH_CLIENT_IDIdentifier: <your-subdomain>_zendesk (or set )
🔐 secretZENDESK_OAUTH_TOKEN
configZENDESK_SUBDOMAIN(, ZENDESK_TOKEN_FILE, PUBLIC_URL, the attachment-vision
configZENDESK_TOKEN_FILEand overrides: [](docs/configuration.md#zendesk_token_file)).
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

47/48 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

1/48 tools missing one or more hints — zendesk (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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

Only 12/48 tools referenced in tests (25%)

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

Shell command execution

3 child_process calls — runs shell commands

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

Dependency freshness

4/15 production deps abandoned (no release in 2+ years): rehype-raw@2023-11-20 (2.7y), remark-parse@2023-11-20 (2.7y), remark-stringify@2023-11-20 (2.7y)

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 4 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/fruggr-zendesk-mcp-server-1p1duz?variant=verified)](https://m8ven.ai/mcp/fruggr-zendesk-mcp-server-1p1duz)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b04e64202991cc02b44fb80d2e242606802850b4
code hash: 40d94995e888a4015a9fe5e0f4ba624e1efcde26b5b5db1cf7ebe89bc7914f9d
verified: 8/6/2026, 5:26:30 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