io.usefulapi/trengo
REMOTE · TRENGO.USEFULAPI.IO · SCANNED OCT 4
Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close.
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 Security89
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2735 tokens (~113/item across 24 items; 24 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 Management13
- Stability observed for 4 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 24 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/trengo MCP server?
io.usefulapi/trengo is a hosted endpoint at https://trengo.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 · trengo.usefulapi.io
claude mcp add --transport http io-usefulapi-trengo 'https://trengo.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-trengo": {
"url": "https://trengo.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-trengo": {
"type": "http",
"url": "https://trengo.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-trengo] url = "https://trengo.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-trengo": {
"type": "remote",
"url": "https://trengo.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-trengo --url 'https://trengo.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-trengo:
url: "https://trengo.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-trengo": {
"Transport": "http",
"Url": "https://trengo.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-trengo -t streamable-http -u 'https://trengo.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-trengo": {
"type": "http",
"url": "https://trengo.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.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 0
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +54
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 100 functional
- 29 Sept 26 18
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 4 Oct 2026 · Probed https://trengo.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 trengo.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://trengo.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://trengo.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://trengo.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://trengo.usefulapi.io/mcp |
| Authorisation server | https://trengo.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trengo.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://trengo.usefulapi.io/mcp | HTTPS enforced | 301 | https://trengo.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 →
trengo_assign_ticket Assign a ticket ~115
Assign a ticket to a user or a team, with an optional assignment note. Reversible by reassigning. Trengo: POST /tickets/{ticket_id}/assign.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | Optional assignment note. |
| team_id | integer | – | The team id — required when type is team. |
| ticket_id | integer | yes | The ticket id. |
| type | string | yes | Assign to a user or to a team. |
| user_id | integer | – | The user id — required when type is user. |
No output schema declared.
No examples provided.
trengo_close_ticket Close a ticket ~73
Close a ticket, optionally applying a ticket result (see trengo_list_ticket_results). Reversible with trengo_reopen_ticket. Trengo: POST /tickets/{ticket_id}/close.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | integer | yes | The ticket id. |
| ticket_result_id | integer | – | Optional ticket result to apply. |
No output schema declared.
No examples provided.
trengo_create_board_card Create a board card ~101
Create a card (e.g. a deal or task) in a stage of a Trengo board. The board id is in the board's URL in Trengo. Trengo: POST /boards/{boardId}/cards.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | integer | yes | The board id. |
| description | string | – | The card's description. |
| name | string | yes | The card's name. |
| stage_id | integer | yes | The stage id. |
No output schema declared.
No examples provided.
trengo_create_contact Create a contact ~98
Create a contact on a channel. The identifier is the contact's address on that channel: an email address for email channels, a phone number for WhatsApp/SMS/voice. Trengo: POST /channels/{channel_id}/contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | integer | yes | The channel id. |
| identifier | string | yes | Email address or phone number, depending on the channel. |
| name | string | – | The contact's full name. |
No output schema declared.
No examples provided.
trengo_create_ticket Create a ticket ~78
Open a new ticket for an existing contact on a channel. Nothing is sent to the customer until you post a message with trengo_send_ticket_message. Trengo: POST /tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | integer | yes | The channel id. |
| contact_id | integer | yes | The contact id. |
| subject | string | – | Optional subject. |
No output schema declared.
No examples provided.
trengo_get_agent_performance Get agent performance ~207
Per-agent performance over a period: messages sent, notes, tickets assigned and closed, average first response and resolution times (with and without business hours). Trengo: GET /reporting/agent_performance.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_ids | array | – | Only these channel ids. |
| end_date | string | – | Period end as ISO 8601, e.g. 2026-09-01T00:00:00+00:00. Give it together with its pair. |
| label_ids | array | – | Only these label ids. |
| page | integer | – | Page number (1-based). Omit for the first page. |
| start_date | string | – | Period start as ISO 8601, e.g. 2026-09-01T00:00:00+00:00. Give it together with its pair. |
| team_ids | array | – | Only these team ids. |
| user_ids | array | – | Only these user ids. |
No output schema declared.
No examples provided.
trengo_get_contact Get a contact ~62
Fetch one contact with name, email, phone and custom field data, optionally with notes. Trengo: GET /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | The contact id. |
| include_notes | boolean | – | Also return the contact's notes. |
No output schema declared.
No examples provided.
trengo_get_email_message Get an email message ~82
Fetch the full email behind one message of a ticket: original HTML body, from, to, subject and Message-ID. The message must be an email message. Trengo: GET /tickets/{ticket_id}/full_email_messages/{message_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | integer | yes | The message id. |
| ticket_id | integer | yes | The ticket id. |
No output schema declared.
No examples provided.
trengo_get_reporting_metrics Get reporting metrics ~208
Aggregate support metrics over a period: new, created, assigned, closed and reopened tickets, average first response time and average total resolution time (seconds). Filter by team, channel, label or direction. Trengo: GET /reporting/metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_ids | array | – | Only these channel ids. |
| direction | string | – | Only INBOUND or OUTBOUND conversations. |
| end_date | string | – | Period end as ISO 8601, e.g. 2026-09-01T00:00:00+00:00. Give it together with its pair. |
| label_ids | array | – | Only these label ids. |
| metrics | array | yes | Which metrics to return. |
| start_date | string | – | Period start as ISO 8601, e.g. 2026-09-01T00:00:00+00:00. Give it together with its pair. |
| team_ids | array | – | Only these team ids. |
No output schema declared.
No examples provided.
trengo_get_ticket_details_report Get ticket details report ~485
Per-ticket reporting rows: status, assignee, labels, first reply, first resolution and total resolution times (with and without business hours). Filter by team, channel, label, direction, status and created/closed/assigned date ranges; sort by a timing metric. For large accounts page with start_after_ticket_id instead of page. Trengo: GET /reporting/details/ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_end_date | string | – | Assigned-until as ISO 8601, e.g. 2026-09-01T00:00:00+00:00. Give it together with its pair. |
| assigned_start_date | string | – | Assigned-from as ISO 8601, e.g. 2026-09-01T00:00:00+00:00. Give it together with its pair. |
| channel_ids | array | – | Only these channel ids. |
| closed_end_date | string | – | Closed-until as ISO 8601, e.g. 2026-09-01T00:00:00+00:00. Give it together with its pair. |
| closed_start_date | string | – | Closed-from as ISO 8601, e.g. 2026-09-01T00:00:00+00:00. Give it together with its pair. |
| created_end_date | string | – | Created-until as ISO 8601, e.g. 2026-09-01T00:00:00+00:00. Give it together with its pair. |
| created_start_date | string | – | Created-from as ISO 8601, e.g. 2026-09-01T00:00:00+00:00. Give it together with its pair. |
| direction | string | – | Only INBOUND or OUTBOUND conversations. |
| label_ids | array | – | Only these label ids. |
| page | integer | – | Page number (1-based). Omit for the first page. |
| sort_by | string | – | Sort column. |
| sort_order | string | – | Sort direction. |
| start_after_ticket_id | integer | – | Keyset cursor: return tickets after this ticket id (replaces page for huge accounts). |
| statuses | array | – | Only tickets in these statuses. |
| team_ids | array | – | Only these team ids. |
No output schema declared.
No examples provided.
trengo_list_contact_groups List contact groups ~55
List the contact groups in the account — use their ids with trengo_update_contact. Trengo: GET /contact_groups.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Omit for the first page. |
No output schema declared.
No examples provided.
trengo_list_contacts List or search contacts ~85
List contacts, or search them by name, email or phone number. Trengo: GET /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| include_last_interaction | boolean | – | Also return each contact's last interaction. |
| page | integer | – | Page number (1-based). Omit for the first page. |
| term | string | – | Search term, matched on email, phone number and name. |
No output schema declared.
No examples provided.
trengo_list_custom_fields List custom fields ~50
List the custom fields defined for tickets, contacts and profiles. Trengo: GET /custom_fields.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Omit for the first page. |
No output schema declared.
No examples provided.
trengo_list_labels List labels ~53
List the ticket labels (tags) in the account, for filtering tickets and reports. Trengo: GET /labels.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Omit for the first page. |
No output schema declared.
No examples provided.
trengo_list_quick_replies List quick replies ~59
List the saved quick replies (canned responses), optionally only the messaging or email ones — useful for drafting consistent answers. Trengo: GET /quick_replies.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | – | Only quick replies of this type. |
No output schema declared.
No examples provided.
trengo_list_teams List teams ~54
List the teams in the account — use their ids to assign tickets to a team. Trengo: GET /teams.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Omit for the first page. |
No output schema declared.
No examples provided.
trengo_list_ticket_messages List a ticket's messages ~75
List the messages of one ticket — inbound, outbound and internal notes — with the contact or agent behind each. Trengo: GET /tickets/{ticket_id}/messages.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Omit for the first page. |
| ticket_id | integer | yes | The ticket id. |
No output schema declared.
No examples provided.
trengo_list_ticket_results List ticket results ~64
List the ticket results (closing outcomes, e.g. 'Resolved', 'Sale') that can be applied when closing a ticket. Trengo: GET /ticket_results.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Omit for the first page. |
No output schema declared.
No examples provided.
trengo_list_tickets List tickets ~201
List tickets (conversations) visible to the token's user, newest activity first, with channel and latest message. Filter by status, contact, assignee, channel, label, last message direction or update time. Trengo: GET /tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | – | Only these channel ids. |
| contact_id | integer | – | Only tickets of this contact. |
| labels | array | – | Only these label ids. |
| last_message_type | string | – | Only tickets whose last message was INBOUND or OUTBOUND. |
| page | integer | – | Page number (1-based). Omit for the first page. |
| sort | string | – | By last message time: -date newest first (default), date oldest first. |
| status | string | – | Only tickets in this status. INVALID = spam. |
| updated_at_gt | string | – | Only tickets updated after this date-time. |
| users | array | – | Only these assigned user ids. |
No output schema declared.
No examples provided.
trengo_list_users List users ~69
List the agents (users) in the Trengo account — use their ids to assign tickets or filter. Trengo: GET /users.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Omit for the first page. |
| sort | string | – | Sort column (default id). |
No output schema declared.
No examples provided.
trengo_reopen_ticket Reopen a ticket ~41
Reopen a closed ticket. Trengo: POST /tickets/{ticket_id}/reopen.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | integer | yes | The ticket id. |
No output schema declared.
No examples provided.
trengo_send_ticket_message Send a ticket message ~168
Post a message on a ticket. With internal_note=true it is an internal note visible only to agents. OTHERWISE IT IS DELIVERED TO THE CUSTOMER on the ticket's channel (email, WhatsApp, chat...) and cannot be recalled — confirm the text first. Trengo: POST /tickets/{ticket_id}/messages.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_ids | array | – | Email channels only: ids of previously uploaded attachments. |
| internal_note | boolean | – | true = internal note for agents only; false/omitted = sent to the customer. |
| message | string | yes | The message. May contain HTML when the channel is email. |
| subject | string | – | Email channels only. Trengo prefixes it with 'Re:' when replying. |
| ticket_id | integer | yes | The ticket id. |
No output schema declared.
No examples provided.
trengo_update_board_card Update a board card ~164
Partially update a board card: rename it, move it to another stage, or set its users (owners) and contacts (leads). user_ids / contact_ids replace the current sets. Trengo: PUT /boards/{boardId}/cards/{cardId}.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | integer | yes | The board id. |
| card_id | integer | yes | The card id. |
| contact_ids | array | – | Trengo contact ids on the card, e.g. leads (replaces the set). |
| name | string | – | The card's new name. |
| stage_id | integer | – | Move the card to this stage. |
| user_ids | array | – | Trengo user ids on the card, e.g. deal owners (replaces the set). |
No output schema declared.
No examples provided.
trengo_update_contact Update a contact ~88
Rename a contact and/or set the contact groups it belongs to. contact_group_ids REPLACES the contact's groups. Trengo: PUT /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_group_ids | array | – | The full set of contact group ids (replaces the current groups). |
| contact_id | integer | yes | The contact id. |
| name | string | – | The contact's new name. |
No output schema declared.
No examples provided.
What is the io.usefulapi/trengo MCP server?
io.usefulapi/trengo is an MCP server listed in the public MCP registry as io.usefulapi/trengo. Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close. This page covers its hosted endpoint (https://trengo.usefulapi.io/mcp).
Is the io.usefulapi/trengo MCP server safe to use?
io.usefulapi/trengo scores 78 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/trengo MCP server expose?
io.usefulapi/trengo exposes 24 tools: trengo_list_tickets, trengo_list_ticket_messages, trengo_get_email_message, trengo_list_contacts, trengo_get_contact, and 19 more. Their descriptions and schemas cost roughly 2,735 tokens of context every time the server is loaded.
Does the io.usefulapi/trengo MCP server require authentication?
Yes. io.usefulapi/trengo 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/trengo MCP server still maintained?
io.usefulapi/trengo is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.