Freshdesk
OCI · GHCR.IO/WYRE-TECHNOLOGY/FRESHDESK-MCP:V1.0.8
MCP server for Freshdesk — tickets, contacts, companies, agents, groups, and knowledge base.
Available components
Last scanned (5 hours ago)
Scores higher than 67% of OCI 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency6
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 64 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 4313 tokens (~65/item across 66 items; 66 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
Tool Safety98
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 11 of 12 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "freshdesk_contacts_send_invite" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 66 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −2
No change was recorded against any check on this day. Stability & Change Management went from 97 to 80.
- 9 Oct 26 −1
- Stability: pass → 0.93 functional
- 4 Oct 26 +1
- Stability: 0.97 → pass security
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 17 Oct 2026 · Analysed oci/ghcr.io/wyre-technology/freshdesk-mcp:v1.0.8
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
freshdesk_solutions_folders_delete ~58
⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a solution folder and all of its articles. This action cannot be undone. Confirm with the user before invoking.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Folder ID |
No output schema declared.
No examples provided.
freshdesk_solutions_folders_get ~30
Get a single solution folder by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Folder ID |
No output schema declared.
No examples provided.
freshdesk_solutions_folders_list ~30
List a category's folders.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | number | yes | Parent category ID |
No output schema declared.
No examples provided.
freshdesk_solutions_folders_update ~56
Update a solution folder.
| Name | Type | Req | Description |
|---|---|---|---|
| company_ids | array | – | – |
| description | string | – | – |
| id | number | yes | Folder ID |
| name | string | – | – |
| visibility | number | – | – |
No output schema declared.
No examples provided.
freshdesk_status ~24
Check Freshdesk API connectivity (calls agents/me) and list available domains.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
freshdesk_tickets_add_note ~93
Add a note to a ticket (private/internal by default).
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | HTML body of the note |
| id | number | yes | Ticket ID |
| notify_emails | array | – | Agents to notify |
| private | boolean | – | True (default) for an internal note, false for a note visible to the requester |
| user_id | number | – | Agent posting the note |
No output schema declared.
No examples provided.
freshdesk_tickets_create ~285
Create a ticket. Provide subject, description, status, priority, and one of requester_id/email/phone.
| Name | Type | Req | Description |
|---|---|---|---|
| cc_emails | array | – | CC emails |
| company_id | number | – | Associated company ID |
| custom_fields | object | – | Custom field values |
| description | string | yes | HTML ticket description |
| string | – | Requester email (one of email/requester_id/phone required) | |
| group_id | number | – | Assign to group |
| name | string | – | Requester name (required when creating via phone) |
| phone | string | – | Requester phone |
| priority | number | yes | 1=Low, 2=Medium, 3=High, 4=Urgent |
| requester_id | number | – | Requester contact ID |
| responder_id | number | – | Assign to agent |
| source | number | – | 1=Email, 2=Portal, 3=Phone, 7=Chat, 9=Feedback Widget, 10=Outbound Email |
| status | number | yes | 2=Open, 3=Pending, 4=Resolved, 5=Closed |
| subject | string | yes | Ticket subject |
| tags | array | – | Tags |
| type | string | – | Ticket type, e.g. "Question", "Incident", "Problem" |
No output schema declared.
No examples provided.
freshdesk_tickets_delete ~60
⚠ DESTRUCTIVE — IRREVERSIBLE. Moves a ticket to trash, removing it from views and reports. This action cannot be undone via the API. Confirm with the user before invoking.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Ticket ID |
No output schema declared.
No examples provided.
freshdesk_tickets_delete_conversation ~61
⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a conversation (reply or note) from a ticket. This action cannot be undone. Confirm with the user before invoking.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | number | yes | Conversation ID |
No output schema declared.
No examples provided.
freshdesk_tickets_get ~52
Get a single ticket by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Ticket ID |
| include | string | – | Comma-separated embeds, e.g. "conversations,requester,company,stats" |
No output schema declared.
No examples provided.
freshdesk_tickets_list ~123
List tickets (single page) with optional filters and pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | number | – | Filter by company ID |
| filter | string | – | Predefined filter, e.g. "new_and_my_open", "watching", "spam", "deleted" |
| page | number | – | 1-based page number |
| perPage | number | – | Records per page (max 100) |
| requester_id | number | – | Filter by requester contact ID |
| updated_since | string | – | ISO-8601 timestamp; tickets updated since this time |
No output schema declared.
No examples provided.
freshdesk_tickets_list_conversations ~60
List a ticket's conversations (replies and notes).
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Ticket ID |
| page | number | – | 1-based page number |
| perPage | number | – | Records per page (max 100) |
No output schema declared.
No examples provided.
freshdesk_tickets_reply ~88
Add a public reply to a ticket (visible to the requester).
| Name | Type | Req | Description |
|---|---|---|---|
| bcc_emails | array | – | – |
| body | string | yes | HTML body of the reply |
| cc_emails | array | – | – |
| from_email | string | – | Reply-from support email |
| id | number | yes | Ticket ID |
| user_id | number | – | Agent posting the reply |
No output schema declared.
No examples provided.
freshdesk_tickets_search ~72
Search tickets using the Freshdesk query language (e.g. "status:2 AND priority:4").
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | 1-based page number (search paginates up to 10 pages of 30) |
| query | string | yes | Freshdesk query string, without surrounding quotes |
No output schema declared.
No examples provided.
freshdesk_tickets_update ~142
Update a ticket (any subset of fields).
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | number | – | – |
| custom_fields | object | – | – |
| description | string | – | – |
| group_id | number | – | – |
| id | number | yes | Ticket ID |
| priority | number | – | 1=Low, 2=Medium, 3=High, 4=Urgent |
| responder_id | number | – | – |
| status | number | – | 2=Open, 3=Pending, 4=Resolved, 5=Closed |
| subject | string | – | – |
| tags | array | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
freshdesk_tickets_update_conversation ~49
Edit the body of an existing conversation (reply/note) by conversation ID.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | New HTML body |
| conversation_id | number | yes | Conversation ID |
No output schema declared.
No examples provided.
How do I install the Freshdesk MCP server?
Freshdesk runs locally as a container image, launched with docker run --rm -i -e FRESHDESK_DOMAIN -e FRESHDESK_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/freshdesk-mcp:v1.0.8. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/wyre-technology/freshdesk-mcp:v1.0.8
claude mcp add wyre-technology-freshdesk-mcp -- docker run --rm -i -e FRESHDESK_DOMAIN -e FRESHDESK_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/freshdesk-mcp:v1.0.8
This image reads FRESHDESK_DOMAIN, FRESHDESK_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Freshdesk MCP server?
Freshdesk is an MCP server listed in the public MCP registry as io.github.wyre-technology/freshdesk-mcp. MCP server for Freshdesk, tickets, contacts, companies, agents, groups, and knowledge base. This page covers its container image (ghcr.io/wyre-technology/freshdesk-mcp:v1.0.8).
Is the Freshdesk MCP server safe to use?
Freshdesk scores 47 out of 100 on VerifyMCP. 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 Freshdesk MCP server expose?
Freshdesk exposes 66 tools: freshdesk_navigate, freshdesk_status, freshdesk_tickets_search, freshdesk_tickets_list, freshdesk_tickets_get, and 61 more. Their descriptions and schemas cost roughly 4,313 tokens of context every time the server is loaded.
Is the Freshdesk MCP server still maintained?
Freshdesk is still listed as active in the MCP registry. We last reached this channel on 17 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 Freshdesk MCP server under?
Freshdesk declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.