io.usefulapi/freshdesk
REMOTE · FRESHDESK.USEFULAPI.IO · SCANNED SEP 20
Read tickets, contacts, companies, agents and groups; create, update and reply to tickets.
Available components
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2471 tokens (~130/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/freshdesk MCP server?
io.usefulapi/freshdesk 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'
{
"mcpServers": {
"io-usefulapi-freshdesk": {
"url": "https://freshdesk.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-freshdesk": {
"type": "http",
"url": "https://freshdesk.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-freshdesk] url = "https://freshdesk.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-freshdesk": {
"type": "remote",
"url": "https://freshdesk.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-freshdesk --url 'https://freshdesk.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-freshdesk:
url: "https://freshdesk.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-freshdesk": {
"Transport": "http",
"Url": "https://freshdesk.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-freshdesk -t streamable-http -u 'https://freshdesk.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-freshdesk": {
"type": "http",
"url": "https://freshdesk.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.87 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −1
- Stability: pass → 0.93 functional
- 13 Sept 26 0
- Stability: 0.97 → pass security
- 12 Sept 26 0
- Stability: pass → 0.97 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 20 Sept 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 | 1 Aug 2026 | 30 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | f8a741ccd989fd2b0eb2b32dd1c04a84 |
| SANs: usefulapi.io, freshdesk.usefulapi.io, *.freshdesk.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. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://freshdesk.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://freshdesk.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://freshdesk.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://freshdesk.usefulapi.io/mcp |
| Authorisation server | https://freshdesk.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://freshdesk.usefulapi.io/mcp | Inconclusive | 401 |
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.
What is the io.usefulapi/freshdesk MCP server?
io.usefulapi/freshdesk is an MCP server 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 io.usefulapi/freshdesk MCP server safe to use?
io.usefulapi/freshdesk scores 85 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 io.usefulapi/freshdesk MCP server expose?
io.usefulapi/freshdesk 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 io.usefulapi/freshdesk MCP server require authentication?
Yes. io.usefulapi/freshdesk asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/freshdesk MCP server still maintained?
io.usefulapi/freshdesk is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.