Freshdesk MCP by usefulapi
REMOTE · FRESHDESK.USEFULAPI.IO
Read tickets, contacts, companies, agents and groups; create, update and reply to tickets.
Available components
Last scanned (5 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 7 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +2
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “change_the_status_or_priority_of_tickets” functional
- New prompt “create_a_ticket_for_a_customer” functional
- New prompt “find_open_urgent_or_unassigned_tickets” functional
- New prompt “look_up_or_add_a_contact_or_company” functional
- New prompt “read_a_ticket_with_its_replies_and_notes” functional
- New prompt “reply_to_a_ticket_or_add_an_internal_note” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 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 7 Nov 2026 · Probed https://freshdesk.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of freshdesk.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://freshdesk.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/freshdesk/ |
| http (plaintext) | http://freshdesk.usefulapi.io/mcp | Inconclusive | 302 | http://freshdesk.usefulapi.io/mcp |
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_add_note Add note to ticket ~117
Add a note to a ticket. Notes are internal (private) by default; set `private: false` for a public note. Freshdesk REST: POST /tickets/{id}/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The note content, HTML (required). |
| id | integer | yes | The ticket id to add a note to. |
| notify_emails | array | – | Agent emails to notify about this note. |
| private | boolean | – | Whether the note is internal/private (default true). Set false for a public note. |
No output schema declared.
No examples provided.
freshdesk_create_company Create company ~93
Create a company. `name` is required. Freshdesk REST: POST /companies.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_fields | object | – | Custom field values, keyed by field name. |
| description | string | – | Freeform description / notes. |
| domains | array | – | Email domains associated with the company. |
| name | string | yes | The company name (required). |
| note | string | – | A note about the company. |
No output schema declared.
No examples provided.
freshdesk_create_contact Create contact ~169
Create a contact. `name` is required. Freshdesk REST: POST /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Postal address. |
| company_id | integer | – | Id of the company the contact belongs to. |
| custom_fields | object | – | Custom field values, keyed by field name. |
| description | string | – | Freeform description / notes. |
| string | – | Email address. | |
| job_title | string | – | Job title. |
| mobile | string | – | Mobile number. |
| name | string | yes | The contact's full name (required). |
| phone | string | – | Phone number. |
| tags | array | – | Tags (array of strings). |
| twitter_id | string | – | Twitter handle. |
| unique_external_id | string | – | External id from your own system. |
No output schema declared.
No examples provided.
freshdesk_create_ticket Create ticket ~433
Create a ticket. `subject` and `description` (HTML) are required, plus a requester — provide at least one of `email`, `requester_id`, or `phone`. status: 2=Open, 3=Pending, 4=Resolved, 5=Closed. priority: 1=Low, 2=Medium, 3=High, 4=Urgent. source: 1=Email, 2=Portal, 3=Phone, 7=Chat, 9=Feedbackwidget, 10=Outbound email. Freshdesk REST: POST /tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| cc_emails | array | – | Emails to CC on the ticket. |
| company_id | integer | – | Id of the company the ticket belongs to. |
| custom_fields | object | – | Custom field values, keyed by field name. |
| description | string | yes | Ticket description, HTML content (required). |
| string | – | Requester email (one of email/requester_id/phone required). | |
| group_id | integer | – | Id of the group to assign the ticket to. |
| phone | string | – | Requester phone (one of email/requester_id/phone required). |
| priority | integer | – | Ticket priority: 1=Low, 2=Medium, 3=High, 4=Urgent. |
| requester_id | integer | – | Requester (contact) id (one of email/requester_id/phone required). |
| responder_id | integer | – | Id of the agent the ticket is assigned to. |
| source | integer | – | Ticket source: 1=Email, 2=Portal, 3=Phone, 7=Chat, 9=Feedbackwidget, 10=Outbound email. |
| status | integer | – | Ticket status: 2=Open, 3=Pending, 4=Resolved, 5=Closed. |
| subject | string | yes | Ticket subject (required). |
| tags | array | – | Tags (array of strings). |
| type | string | – | Ticket type (e.g. Question, Incident). |
No output schema declared.
No examples provided.
freshdesk_get_agent Get agent ~37
Get a single agent by id. Freshdesk REST: GET /agents/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The agent id. |
No output schema declared.
No examples provided.
freshdesk_get_company Get company ~37
Get a single company by id. Freshdesk REST: GET /companies/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The company id. |
No output schema declared.
No examples provided.
freshdesk_get_contact Get contact ~37
Get a single contact by id. Freshdesk REST: GET /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The contact id. |
No output schema declared.
No examples provided.
freshdesk_get_ticket Get ticket ~58
Get a single ticket by id. Freshdesk REST: GET /tickets/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The ticket id. |
| include | string | – | Embed extra data, comma-separated: conversations, requester, company, stats. |
No output schema declared.
No examples provided.
freshdesk_list_agents List agents ~106
List/filter agents. Freshdesk REST: GET /agents.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Filter by email. | |
| mobile | string | – | Filter by mobile number. |
| page | integer | – | Page number for pagination (1-based). |
| per_page | integer | – | Results per page (1-100, max 100, default 30). |
| phone | string | – | Filter by phone number. |
| state | string | – | Filter by state: fulltime or occasional. |
No output schema declared.
No examples provided.
freshdesk_list_companies List companies ~59
List companies. Freshdesk REST: GET /companies.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number for pagination (1-based). |
| per_page | integer | – | Results per page (1-100, max 100, default 30). |
No output schema declared.
No examples provided.
freshdesk_list_contacts List contacts ~141
List/filter contacts. Freshdesk REST: GET /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | – | Filter by company id. |
| string | – | Filter by email. | |
| mobile | string | – | Filter by mobile number. |
| page | integer | – | Page number for pagination (1-based). |
| per_page | integer | – | Results per page (1-100, max 100, default 30). |
| phone | string | – | Filter by phone number. |
| state | string | – | Filter by state: verified, unverified, blocked, or deleted. |
| updated_since | string | – | Only contacts updated after this ISO 8601 timestamp. |
No output schema declared.
No examples provided.
freshdesk_list_groups List groups ~65
List groups (agent groups tickets are routed to). Freshdesk REST: GET /groups.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number for pagination (1-based). |
| per_page | integer | – | Results per page (1-100, max 100, default 30). |
No output schema declared.
No examples provided.
freshdesk_list_ticket_conversations List ticket conversations ~85
List the conversations (replies and notes) on a ticket. Freshdesk REST: GET /tickets/{id}/conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The ticket id. |
| page | integer | – | Page number for pagination (1-based). |
| per_page | integer | – | Results per page (1-100, max 100, default 30). |
No output schema declared.
No examples provided.
freshdesk_list_tickets List tickets ~203
List/filter tickets (max page 300). Freshdesk REST: GET /tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | – | Filter by company id. |
| string | – | Filter by requester email. | |
| filter | string | – | Predefined filter: new_and_my_open, watching, spam, or deleted. |
| include | string | – | Embed extra data, comma-separated, e.g. "requester,stats,description". |
| order_by | string | – | Sort field: created_at, due_by, updated_at, or status. |
| order_type | string | – | Sort direction: asc or desc. |
| page | integer | – | Page number for pagination (1-based). |
| per_page | integer | – | Results per page (1-100, max 100, default 30). |
| requester_id | integer | – | Filter by requester (contact) id. |
| updated_since | string | – | Only tickets updated after this ISO 8601 timestamp. |
No output schema declared.
No examples provided.
freshdesk_reply_ticket Reply to ticket ~94
Add a public reply to a ticket (sent to the requester). Freshdesk REST: POST /tickets/{id}/reply.
| Name | Type | Req | Description |
|---|---|---|---|
| bcc_emails | array | – | Emails to BCC on the reply. |
| body | string | yes | The reply content, HTML (required). |
| cc_emails | array | – | Emails to CC on the reply. |
| id | integer | yes | The ticket id to reply to. |
No output schema declared.
No examples provided.
freshdesk_search_contacts Search contacts ~121
Search contacts with the Freshdesk query DSL. The query VALUE is wrapped in double quotes automatically. Examples: `name:'ada'`, `email:'ada@example.com'`, `company_id:123`. Freshdesk REST: GET /search/contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-10; search endpoints return 30 results per page and ignore per_page). |
| query | string | yes | Freshdesk search query, e.g. "company_id:123" (do NOT add surrounding quotes yourself — they are added for you). |
No output schema declared.
No examples provided.
freshdesk_search_tickets Search tickets ~145
Search tickets with the Freshdesk query DSL. The query VALUE is wrapped in double quotes automatically. Examples: `status:2 AND priority:3`, `created_at:>'2026-01-01'`, `agent_id:123`, `group_id:45`, `tag:'urgent'`. Freshdesk REST: GET /search/tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-10; search endpoints return 30 results per page and ignore per_page). |
| query | string | yes | Freshdesk search query, e.g. "priority:3 AND status:2" (do NOT add surrounding quotes yourself — they are added for you). |
No output schema declared.
No examples provided.
freshdesk_update_contact Update contact ~159
Update fields on an existing contact. Only provided fields are changed. Freshdesk REST: PUT /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Postal address. |
| company_id | integer | – | Id of the company the contact belongs to. |
| custom_fields | object | – | Custom field values, keyed by field name. |
| description | string | – | Freeform description / notes. |
| string | – | Email address. | |
| id | integer | yes | The contact id to update. |
| job_title | string | – | Job title. |
| mobile | string | – | Mobile number. |
| name | string | – | The contact's full name. |
| phone | string | – | Phone number. |
| tags | array | – | Tags (array of strings). |
No output schema declared.
No examples provided.
freshdesk_update_ticket Update ticket ~312
Update fields on an existing ticket. Only provided fields are changed. status: 2=Open, 3=Pending, 4=Resolved, 5=Closed. priority: 1=Low, 2=Medium, 3=High, 4=Urgent. Freshdesk REST: PUT /tickets/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | – | Id of the company the ticket belongs to. |
| custom_fields | object | – | Custom field values, keyed by field name. |
| description | string | – | Ticket description, HTML content. |
| group_id | integer | – | Id of the group to assign the ticket to. |
| id | integer | yes | The ticket id to update. |
| priority | integer | – | Ticket priority: 1=Low, 2=Medium, 3=High, 4=Urgent. |
| requester_id | integer | – | Requester (contact) id. |
| responder_id | integer | – | Id of the agent the ticket is assigned to. |
| source | integer | – | Ticket source: 1=Email, 2=Portal, 3=Phone, 7=Chat, 9=Feedbackwidget, 10=Outbound email. |
| status | integer | – | Ticket status: 2=Open, 3=Pending, 4=Resolved, 5=Closed. |
| subject | string | – | Ticket subject. |
| tags | array | – | Tags (array of strings). |
| type | string | – | Ticket type. |
No output schema declared.
No examples provided.
How do I install the Freshdesk MCP by usefulapi server?
Freshdesk MCP by usefulapi is a hosted endpoint at https://freshdesk.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · freshdesk.usefulapi.io
claude mcp add --transport http io-usefulapi-freshdesk 'https://freshdesk.usefulapi.io/mcp'
What is the Freshdesk MCP by usefulapi server?
Freshdesk MCP by usefulapi is listed in the public MCP registry as io.usefulapi/freshdesk. Read tickets, contacts, companies, agents and groups; create, update and reply to tickets. This page covers its hosted endpoint (https://freshdesk.usefulapi.io/mcp).
Is the Freshdesk MCP by usefulapi server safe to use?
Freshdesk MCP by usefulapi scores 18 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 by usefulapi server expose?
Freshdesk MCP by usefulapi exposes 19 tools: freshdesk_list_tickets, freshdesk_get_ticket, freshdesk_search_tickets, freshdesk_list_ticket_conversations, freshdesk_list_contacts, and 14 more. Their descriptions and schemas cost roughly 2,471 tokens of context every time the server is loaded.
Does the Freshdesk MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Freshdesk MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Freshdesk MCP by usefulapi server still maintained?
Freshdesk MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Freshdesk MCP by usefulapi server?
VerifyMCP ran 4 checks on Freshdesk MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Freshdesk MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.