# io.usefulapi/trengo (remote · trengo.usefulapi.io)

Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close.

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `trengo.usefulapi.io`: 78/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-trengo/trengo.md), [page](https://verifymcp.io/servers/io-usefulapi-trengo/trengo)

## Channel facts

- Endpoint: `https://trengo.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-trengo 'https://trengo.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-trengo": {
      "url": "https://trengo.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-trengo": {
      "type": "http",
      "url": "https://trengo.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-trengo]
url = "https://trengo.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-trengo": {
      "type": "remote",
      "url": "https://trengo.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-trengo --url 'https://trengo.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-trengo:
    url: "https://trengo.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-trengo": {
      "Transport": "http",
      "Url": "https://trengo.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-trengo -t streamable-http -u 'https://trengo.usefulapi.io/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-03 (score 78, +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.

### 2026-10-02 (score 77, 0)

- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-01 (score 77, +5)

- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.3.0

### 2026-09-30 (score 72, +54)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] 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

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (24)

### `trengo_list_tickets` (~201 tokens)

List tickets

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.

Input parameters:

- `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.

### `trengo_list_ticket_messages` (~75 tokens)

List a ticket's messages

List the messages of one ticket — inbound, outbound and internal notes — with the contact or agent behind each. Trengo: GET /tickets/{ticket_id}/messages.

Input parameters:

- `page` (integer): Page number (1-based). Omit for the first page.
- `ticket_id` (integer, required): The ticket id.

### `trengo_get_email_message` (~82 tokens)

Get an email message

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}.

Input parameters:

- `message_id` (integer, required): The message id.
- `ticket_id` (integer, required): The ticket id.

### `trengo_list_contacts` (~85 tokens)

List or search contacts

List contacts, or search them by name, email or phone number. Trengo: GET /contacts.

Input parameters:

- `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.

### `trengo_get_contact` (~62 tokens)

Get a contact

Fetch one contact with name, email, phone and custom field data, optionally with notes. Trengo: GET /contacts/{id}.

Input parameters:

- `contact_id` (integer, required): The contact id.
- `include_notes` (boolean): Also return the contact's notes.

### `trengo_list_contact_groups` (~55 tokens)

List contact groups

List the contact groups in the account — use their ids with trengo_update_contact. Trengo: GET /contact_groups.

Input parameters:

- `page` (integer): Page number (1-based). Omit for the first page.

### `trengo_list_users` (~69 tokens)

List users

List the agents (users) in the Trengo account — use their ids to assign tickets or filter. Trengo: GET /users.

Input parameters:

- `page` (integer): Page number (1-based). Omit for the first page.
- `sort` (string): Sort column (default id).

### `trengo_list_teams` (~54 tokens)

List teams

List the teams in the account — use their ids to assign tickets to a team. Trengo: GET /teams.

Input parameters:

- `page` (integer): Page number (1-based). Omit for the first page.

### `trengo_list_labels` (~53 tokens)

List labels

List the ticket labels (tags) in the account, for filtering tickets and reports. Trengo: GET /labels.

Input parameters:

- `page` (integer): Page number (1-based). Omit for the first page.

### `trengo_list_ticket_results` (~64 tokens)

List ticket results

List the ticket results (closing outcomes, e.g. 'Resolved', 'Sale') that can be applied when closing a ticket. Trengo: GET /ticket_results.

Input parameters:

- `page` (integer): Page number (1-based). Omit for the first page.

### `trengo_list_custom_fields` (~50 tokens)

List custom fields

List the custom fields defined for tickets, contacts and profiles. Trengo: GET /custom_fields.

Input parameters:

- `page` (integer): Page number (1-based). Omit for the first page.

### `trengo_list_quick_replies` (~59 tokens)

List quick replies

List the saved quick replies (canned responses), optionally only the messaging or email ones — useful for drafting consistent answers. Trengo: GET /quick_replies.

Input parameters:

- `type` (string): Only quick replies of this type.

### `trengo_get_reporting_metrics` (~208 tokens)

Get reporting metrics

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.

Input parameters:

- `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, required): 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.

### `trengo_get_agent_performance` (~207 tokens)

Get agent performance

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.

Input parameters:

- `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.

### `trengo_get_ticket_details_report` (~485 tokens)

Get ticket details report

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.

Input parameters:

- `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.

### `trengo_create_ticket` (~78 tokens)

Create a ticket

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.

Input parameters:

- `channel_id` (integer, required): The channel id.
- `contact_id` (integer, required): The contact id.
- `subject` (string): Optional subject.

### `trengo_assign_ticket` (~115 tokens)

Assign a ticket

Assign a ticket to a user or a team, with an optional assignment note. Reversible by reassigning. Trengo: POST /tickets/{ticket_id}/assign.

Input parameters:

- `note` (string): Optional assignment note.
- `team_id` (integer): The team id — required when type is team.
- `ticket_id` (integer, required): The ticket id.
- `type` (string, required): Assign to a user or to a team.
- `user_id` (integer): The user id — required when type is user.

### `trengo_close_ticket` (~73 tokens)

Close a ticket

Close a ticket, optionally applying a ticket result (see trengo_list_ticket_results). Reversible with trengo_reopen_ticket. Trengo: POST /tickets/{ticket_id}/close.

Input parameters:

- `ticket_id` (integer, required): The ticket id.
- `ticket_result_id` (integer): Optional ticket result to apply.

### `trengo_reopen_ticket` (~41 tokens)

Reopen a ticket

Reopen a closed ticket. Trengo: POST /tickets/{ticket_id}/reopen.

Input parameters:

- `ticket_id` (integer, required): The ticket id.

### `trengo_send_ticket_message` (~168 tokens)

Send a ticket message

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.

Input parameters:

- `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, required): 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, required): The ticket id.

### `trengo_create_contact` (~98 tokens)

Create a contact

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.

Input parameters:

- `channel_id` (integer, required): The channel id.
- `identifier` (string, required): Email address or phone number, depending on the channel.
- `name` (string): The contact's full name.

### `trengo_update_contact` (~88 tokens)

Update a contact

Rename a contact and/or set the contact groups it belongs to. contact_group_ids REPLACES the contact's groups. Trengo: PUT /contacts/{id}.

Input parameters:

- `contact_group_ids` (array): The full set of contact group ids (replaces the current groups).
- `contact_id` (integer, required): The contact id.
- `name` (string): The contact's new name.

### `trengo_create_board_card` (~101 tokens)

Create a board card

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.

Input parameters:

- `board_id` (integer, required): The board id.
- `description` (string): The card's description.
- `name` (string, required): The card's name.
- `stage_id` (integer, required): The stage id.

### `trengo_update_board_card` (~164 tokens)

Update a board card

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}.

Input parameters:

- `board_id` (integer, required): The board id.
- `card_id` (integer, required): 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).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-trengo/trengo#diagnostics

## Score history

- 2026-10-04: 78
- 2026-10-03: 78
- 2026-10-02: 77
- 2026-10-01: 77
- 2026-09-30: 72
- 2026-09-29: 18

## Common questions

### 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.

## Links

- Remote endpoint: https://trengo.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-trengo/trengo.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-trengo/trengo.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-trengo/trengo