io.github.headlessherm-creator/helpdesk-mender-mcp
NPM · HELPDESK-MENDER-MCP
Local MCP server: Zendesk + Freshdesk + Help Scout write tools, one vocabulary.
Available components
Last scanned (6 hours ago)
Scores higher than 37% of npm servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 469 tokens (~93/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 22 Oct 26 51
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Analysed npm/helpdesk-mender-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_note ~104
Add a private, internal-only note (not visible to the customer). Freshdesk: ticketId, body. Zendesk: use add_reply with isPublic=false instead (Zendesk has no separate note endpoint). Help Scout: conversationId, text (uses isPublic=false).
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| conversationId | string|number | – | – |
| platform | string | yes | – |
| text | string | – | – |
| ticketId | string|number | – | – |
No output schema declared.
No examples provided.
add_reply ~114
Add a public reply (visible to the customer) to an existing ticket/conversation. Freshdesk: ticketId, body. Zendesk: ticketId, body (adds as a public comment). Help Scout: conversationId, text.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Freshdesk/Zendesk reply text |
| conversationId | string|number | – | Help Scout |
| platform | string | yes | – |
| text | string | – | Help Scout reply text |
| ticketId | string|number | – | Freshdesk/Zendesk |
No output schema declared.
No examples provided.
create_ticket ~100
Create a new ticket/conversation. Freshdesk: subject, description, email. Zendesk: subject, comment (string or {body}), requesterEmail. Help Scout: subject, customerEmail, customerFirstName, customerLastName, mailboxId, text (Help Scout calls this a 'conversation', not a ticket).
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | yes | – |
| ticket | object | yes | Ticket/conversation fields. Field names differ by platform — see tool description. |
No output schema declared.
No examples provided.
list_tickets ~37
List tickets/conversations for a platform.
| Name | Type | Req | Description |
|---|---|---|---|
| mailboxId | string|number | – | Help Scout only |
| platform | string | yes | – |
No output schema declared.
No examples provided.
update_status ~114
Change a ticket/conversation's status. Freshdesk status codes: 2=Open, 3=Pending, 4=Resolved, 5=Closed. Zendesk: 'new', 'open', 'pending', 'hold', 'solved', 'closed'. Help Scout: 'active', 'pending', 'closed', 'spam'.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationId | string|number | – | – |
| platform | string | yes | – |
| status | string|number | yes | – |
| ticketId | string|number | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.headlessherm-creator/helpdesk-mender-mcp server?
io.github.headlessherm-creator/helpdesk-mender-mcp runs locally as an npm package, launched with npx -y helpdesk-mender-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · helpdesk-mender-mcp
claude mcp add headlessherm-creator-helpdesk-mender-mcp -- npx -y helpdesk-mender-mcp
What is the io.github.headlessherm-creator/helpdesk-mender-mcp server?
io.github.headlessherm-creator/helpdesk-mender-mcp is listed in the public MCP registry as io.github.headlessherm-creator/helpdesk-mender-mcp. Local MCP server: Zendesk + Freshdesk + Help Scout write tools, one vocabulary. This page covers its npm package (helpdesk-mender-mcp).
Is the io.github.headlessherm-creator/helpdesk-mender-mcp server safe to use?
io.github.headlessherm-creator/helpdesk-mender-mcp scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.headlessherm-creator/helpdesk-mender-mcp server expose?
io.github.headlessherm-creator/helpdesk-mender-mcp exposes 5 tools: create_ticket, add_reply, add_note, update_status, list_tickets. Their descriptions and schemas cost roughly 469 tokens of context every time the server is loaded.
Is the io.github.headlessherm-creator/helpdesk-mender-mcp server still maintained?
io.github.headlessherm-creator/helpdesk-mender-mcp is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.headlessherm-creator/helpdesk-mender-mcp server under?
io.github.headlessherm-creator/helpdesk-mender-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.