Home / MCP registry index / io.usefulapi/trengo
Trengo MCP by usefulapi
io.usefulapi/trengo in the official MCP registry.
Endpoint https://trengo.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close.
We read its 24 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
trengo_list_tickets trengo_list_ticket_messages trengo_get_email_message trengo_list_contacts trengo_get_contact trengo_list_contact_groups trengo_list_users trengo_list_teams trengo_list_labels trengo_list_ticket_results trengo_list_custom_fields trengo_list_quick_replies trengo_get_reporting_metrics trengo_get_agent_performance trengo_get_ticket_details_report 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 trengo_update_board_card
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-trengo)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.