Trengo MCP by usefulapi
io.usefulapi/trengousefulapi.iostreamable-httpv1.40.4Scanned
Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close.
24 tools: 9 can delete or cancel things and 15 only read.
- Reads private data · 9
- Reads text others write · 14
- Can send data out · 1
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
9 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Trengo MCP by usefulapi can do
The Trengo MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 24 tools. It can delete or cancel things (9 tools: trengo_create_ticket, trengo_assign_ticket, trengo_close_ticket, trengo_reopen_ticket and 5 more). 15 tools only read.
9 tools read private data (trengo_list_tickets, trengo_list_ticket_messages, trengo_get_email_message and 6 more); 14 tools bring in text other people can write (trengo_list_tickets, trengo_list_ticket_messages, trengo_get_email_message and 11 more); 1 tool can send data out of your system (trengo_send_ticket_message). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
24 tools
Deletes or cancels 9Claude Code: deny
trengo_assign_ticketAssign a ticket to a user or a team, with an optional assignment note.No findings
Why it is in this group
- The name "trengo_assign_ticket" says "assign": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Assign a ticket to a user or a team, with an optional assignment note. Reversible by reassigning. Trengo: POST /tickets/{ticket_id}/assign.
Annotations the server declares
- title: Assign a ticket
- destructiveHint: true
trengo_close_ticketClose a ticket, optionally applying a ticket result (see trengo_list_ticket_results).No findings
Why it is in this group
- The name "trengo_close_ticket" says "close": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Close a ticket, optionally applying a ticket result (see trengo_list_ticket_results). Reversible with trengo_reopen_ticket. Trengo: POST /tickets/{ticket_id}/close.
Annotations the server declares
- title: Close a ticket
- destructiveHint: true
trengo_create_board_cardCreate a card (e.g.No findings
Why it is in this group
- The name "trengo_create_board_card" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Create a board card
- destructiveHint: true
trengo_create_contactCreate a contact on a channel.No findings
Why it is in this group
- The name "trengo_create_contact" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Create a contact
- destructiveHint: true
trengo_create_ticketOpen a new ticket for an existing contact on a channel.No findings
Why it is in this group
- The name "trengo_create_ticket" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Create a ticket
- destructiveHint: true
trengo_reopen_ticketReopen a closed ticket.No findings
Why it is in this group
- The name "trengo_reopen_ticket" says "reopen": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Reopen a closed ticket. Trengo: POST /tickets/{ticket_id}/reopen.
Annotations the server declares
- title: Reopen a ticket
- destructiveHint: true
trengo_send_ticket_messagePost a message on a ticket.Can send data outNo findings
Why it is in this group
- The name "trengo_send_ticket_message" says "send": a word for sending, and what is sent cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "trengo_send_ticket_message" says "send": it sends or publishes something to other people.
Description, as the server wrote it 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.
Annotations the server declares
- title: Send a ticket message
- destructiveHint: true
trengo_update_board_cardPartially update a board card: rename it, move it to another stage, or set its users (owners) and contacts (leads).No findings
Why it is in this group
- The name "trengo_update_board_card" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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}.
Annotations the server declares
- title: Update a board card
- destructiveHint: true
trengo_update_contactRename a contact and/or set the contact groups it belongs to.No findings
Why it is in this group
- The name "trengo_update_contact" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Rename a contact and/or set the contact groups it belongs to. contact_group_ids REPLACES the contact's groups. Trengo: PUT /contacts/{id}.
Annotations the server declares
- title: Update a contact
- destructiveHint: true
Only reads 15Show 15 read-only tools
trengo_get_agent_performancePer-agent performance over a period: messages sent, notes, tickets assigned and closed, average first response and resolution times (with and without business hours).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "trengo_get_agent_performance" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "message": it reads messages.
- untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get agent performance
- readOnlyHint: true
trengo_get_contactFetch one contact with name, email, phone and custom field data, optionally with notes.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "trengo_get_contact" says "get": a word for reading.
What it can reach
- private-dataThe name "trengo_get_contact" says "get" and "contact": it reads contacts.
- private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
- untrusted-inputThe description's first sentence says "fetch" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it Fetch one contact with name, email, phone and custom field data, optionally with notes. Trengo: GET /contacts/{id}.
Annotations the server declares
- title: Get a contact
- readOnlyHint: true
trengo_get_email_messageFetch the full email behind one message of a ticket: original HTML body, from, to, subject and Message-ID.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "trengo_get_email_message" says "get": a word for reading.
What it can reach
- private-dataThe name "trengo_get_email_message" says "get" and "email": it reads mail.
- private-dataThe description's first sentence says "fetch" and "email": it reads mail.
- untrusted-inputThe name "trengo_get_email_message" says "get" and "email": it reads inbound email, which other people can write.
- untrusted-inputThe description's first sentence says "fetch" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get an email message
- readOnlyHint: true
trengo_get_reporting_metricsAggregate support metrics over a period: new, created, assigned, closed and reopened tickets, average first response time and average total resolution time (seconds).Reads text others writeNo findings
Why it is in this group
- The name "trengo_get_reporting_metrics" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get reporting metrics
- readOnlyHint: true
trengo_get_ticket_details_reportPer-ticket reporting rows: status, assignee, labels, first reply, first resolution and total resolution times (with and without business hours).Reads text others writeNo findings
Why it is in this group
- The name "trengo_get_ticket_details_report" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "trengo_get_ticket_details_report" says "get" and "ticket": it reads issues, which other people can write.
- untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get ticket details report
- readOnlyHint: true
trengo_list_contact_groupsList the contact groups in the account — use their ids with trengo_update_contact.Reads private dataNo findings
Why it is in this group
- The name "trengo_list_contact_groups" says "list": a word for reading.
What it can reach
- private-dataThe name "trengo_list_contact_groups" says "list" and "contact": it reads contacts.
- private-dataThe description's first sentence says "list" and "contact": it reads contacts.
Description, as the server wrote it List the contact groups in the account — use their ids with trengo_update_contact. Trengo: GET /contact_groups.
Annotations the server declares
- title: List contact groups
- readOnlyHint: true
trengo_list_contactsList contacts, or search them by name, email or phone number.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "trengo_list_contacts" says "list": a word for reading.
What it can reach
- private-dataThe name "trengo_list_contacts" says "list" and "contact": it reads contacts.
- private-dataThe description's first sentence says "list" and "contact": it reads contacts.
- untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it List contacts, or search them by name, email or phone number. Trengo: GET /contacts.
Annotations the server declares
- title: List or search contacts
- readOnlyHint: true
trengo_list_custom_fieldsList the custom fields defined for tickets, contacts and profiles.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "trengo_list_custom_fields" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "contact": it reads contacts.
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it List the custom fields defined for tickets, contacts and profiles. Trengo: GET /custom_fields.
Annotations the server declares
- title: List custom fields
- readOnlyHint: true
trengo_list_labelsList the ticket labels (tags) in the account, for filtering tickets and reports.Reads text others writeNo findings
Why it is in this group
- The name "trengo_list_labels" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it List the ticket labels (tags) in the account, for filtering tickets and reports. Trengo: GET /labels.
Annotations the server declares
- title: List labels
- readOnlyHint: true
trengo_list_quick_repliesList the saved quick replies (canned responses), optionally only the messaging or email ones — useful for drafting consistent answers.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "trengo_list_quick_replies" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "email": it reads mail.
- untrusted-inputThe name "trengo_list_quick_replies" says "list" and "reply": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "reply": it reads comments, which other people can write.
Description, as the server wrote it List the saved quick replies (canned responses), optionally only the messaging or email ones — useful for drafting consistent answers. Trengo: GET /quick_replies.
Annotations the server declares
- title: List quick replies
- readOnlyHint: true
trengo_list_teamsList the teams in the account — use their ids to assign tickets to a team.Reads text others writeNo findings
Why it is in this group
- The name "trengo_list_teams" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it List the teams in the account — use their ids to assign tickets to a team. Trengo: GET /teams.
Annotations the server declares
- title: List teams
- readOnlyHint: true
trengo_list_ticket_messagesList the messages of one ticket — inbound, outbound and internal notes — with the contact or agent behind each.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "trengo_list_ticket_messages" says "list": a word for reading.
What it can reach
- private-dataThe name "trengo_list_ticket_messages" says "list" and "message": it reads messages.
- private-dataThe description's first sentence says "list" and "message": it reads messages.
- untrusted-inputThe name "trengo_list_ticket_messages" says "list" and "ticket": it reads issues, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "message": it reads messages, which other people can write.
Description, as the server wrote it List the messages of one ticket — inbound, outbound and internal notes — with the contact or agent behind each. Trengo: GET /tickets/{ticket_id}/messages.
Annotations the server declares
- title: List a ticket's messages
- readOnlyHint: true
trengo_list_ticket_resultsList the ticket results (closing outcomes, e.g.Reads text others writeNo findings
Why it is in this group
- The name "trengo_list_ticket_results" says "list": a word for reading.
What it can reach
- untrusted-inputThe name "trengo_list_ticket_results" says "list" and "ticket": it reads issues, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it List the ticket results (closing outcomes, e.g. 'Resolved', 'Sale') that can be applied when closing a ticket. Trengo: GET /ticket_results.
Annotations the server declares
- title: List ticket results
- readOnlyHint: true
trengo_list_ticketsList tickets (conversations) visible to the token's user, newest activity first, with channel and latest message.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "trengo_list_tickets" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "conversation": it reads messages.
- untrusted-inputThe name "trengo_list_tickets" says "list" and "ticket": it reads issues, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: List tickets
- readOnlyHint: true
trengo_list_usersList the agents (users) in the Trengo account — use their ids to assign tickets or filter.Reads text others writeNo findings
Why it is in this group
- The name "trengo_list_users" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it List the agents (users) in the Trengo account — use their ids to assign tickets or filter. Trengo: GET /users.
Annotations the server declares
- title: List users
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
126 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data9
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write14
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__trengo__trengo_send_ticket_message"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:38 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 9 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://trengo.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://trengo.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 9 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://trengo.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://trengo.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http trengo https://trengo.usefulapi.io/mcpclaude mcp add --transport http trengo https://trengo.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__trengo__trengo_list_tickets",
"mcp__trengo__trengo_list_ticket_messages",
"mcp__trengo__trengo_get_email_message",
"mcp__trengo__trengo_list_contacts",
"mcp__trengo__trengo_get_contact",
"mcp__trengo__trengo_list_contact_groups",
"mcp__trengo__trengo_list_users",
"mcp__trengo__trengo_list_teams",
"mcp__trengo__trengo_list_labels",
"mcp__trengo__trengo_list_ticket_results",
"mcp__trengo__trengo_list_custom_fields",
"mcp__trengo__trengo_list_quick_replies",
"mcp__trengo__trengo_get_reporting_metrics",
"mcp__trengo__trengo_get_agent_performance",
"mcp__trengo__trengo_get_ticket_details_report"
],
"ask": [],
"deny": [
"mcp__trengo__trengo_create_ticket",
"mcp__trengo__trengo_assign_ticket",
"mcp__trengo__trengo_close_ticket",
"mcp__trengo__trengo_reopen_ticket",
"mcp__trengo__trengo_send_ticket_message",
"mcp__trengo__trengo_create_contact",
"mcp__trengo__trengo_update_contact",
"mcp__trengo__trengo_create_board_card",
"mcp__trengo__trengo_update_board_card"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as trengo. Review it before you use it.
Capability tags behind 16 rules
- mcp__trengo__trengo_list_tickets private-data, untrusted-input
- mcp__trengo__trengo_list_ticket_messages private-data, untrusted-input
- mcp__trengo__trengo_get_email_message private-data, untrusted-input
- mcp__trengo__trengo_list_contacts private-data, untrusted-input
- mcp__trengo__trengo_get_contact private-data, untrusted-input
- mcp__trengo__trengo_list_contact_groups private-data
- mcp__trengo__trengo_list_users untrusted-input
- mcp__trengo__trengo_list_teams untrusted-input
- mcp__trengo__trengo_list_labels untrusted-input
- mcp__trengo__trengo_list_ticket_results untrusted-input
- mcp__trengo__trengo_list_custom_fields private-data, untrusted-input
- mcp__trengo__trengo_list_quick_replies private-data, untrusted-input
- mcp__trengo__trengo_get_reporting_metrics untrusted-input
- mcp__trengo__trengo_get_agent_performance private-data, untrusted-input
- mcp__trengo__trengo_get_ticket_details_report untrusted-input
- mcp__trengo__trengo_send_ticket_message outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/trengo/verify?hash=3dcb9ceba2815231e287770db294727e79667d186f2fe54435a11dd8ccb071c7" | jq -e '.changed == false'Pinned hash 3dcb9ceba281, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/trengo/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/trengo)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.
Trengo MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Trengo MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 24 tools, 9 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Trengo MCP by usefulapi delete data?
- Yes. 9 tools can delete, cancel or revoke something: trengo_create_ticket, trengo_assign_ticket, trengo_close_ticket, trengo_reopen_ticket, trengo_send_ticket_message, trengo_create_contact and 3 more.
Can the Trengo MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Trengo MCP by usefulapi have?
- 24 tools: 9 destructive, 15 read. trengo_create_ticket, trengo_assign_ticket, trengo_close_ticket, trengo_reopen_ticket, trengo_send_ticket_message, trengo_create_contact, trengo_update_contact, trengo_create_board_card and 16 more.
Does the Trengo MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Trengo MCP by usefulapi send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): trengo_send_ticket_message.
Has the Trengo MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.