Home / MCP registry index / io.usefulapi/twenty
Twenty MCP by usefulapi
io.usefulapi/twenty in the official MCP registry.
Endpoint https://twenty.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read people, companies, opportunities, notes and tasks; create and update records in Twenty CRM.
We read its 20 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
twenty_list_metadata_objects twenty_list_people twenty_get_person twenty_list_companies twenty_get_company twenty_list_opportunities twenty_get_opportunity twenty_list_notes twenty_get_note twenty_list_tasks twenty_get_task twenty_create_person twenty_update_person twenty_create_company twenty_update_company twenty_create_opportunity twenty_update_opportunity twenty_create_note twenty_create_task twenty_update_task
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-twenty)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.