io.usefulapi/twenty
REMOTE · TWENTY.USEFULAPI.IO · SCANNED SEP 21
Read people, companies, opportunities, notes and tasks; create and update records in Twenty CRM.
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 Security78
- 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 enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3156 tokens (~157/item across 20 items; 20 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 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/twenty MCP server?
io.usefulapi/twenty is a hosted endpoint at https://twenty.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 · twenty.usefulapi.io
claude mcp add --transport http io-usefulapi-twenty 'https://twenty.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-twenty": {
"url": "https://twenty.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-twenty": {
"type": "http",
"url": "https://twenty.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-twenty] url = "https://twenty.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-twenty": {
"type": "remote",
"url": "https://twenty.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-twenty --url 'https://twenty.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-twenty:
url: "https://twenty.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-twenty": {
"Transport": "http",
"Url": "https://twenty.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-twenty -t streamable-http -u 'https://twenty.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-twenty": {
"type": "http",
"url": "https://twenty.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.
- 1 Sept 26 0
- Stability: 0.97 → pass security
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Aug 26 0
- Authorization: unverified → pass ▲ security
- Transport: fail → 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 Tool coverage: 100 functional
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 21 Sept 2026 · Probed https://twenty.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 | 1 Aug 2026 | 30 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 54d448f413d2a9cd1310d95c7a7bd1ba |
| SANs: usefulapi.io, twenty.usefulapi.io, *.twenty.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 twenty.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://twenty.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://twenty.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://twenty.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://twenty.usefulapi.io/mcp |
| Authorisation server | https://twenty.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://twenty.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://twenty.usefulapi.io/mcp | Inconclusive | 401 |
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 →
twenty_create_company Create company ~172
Create a new company. `name` is required. Twenty REST: POST /rest/companies.
| Name | Type | Req | Description |
|---|---|---|---|
| addressCity | string | – | City (sent as address:{addressCity}). |
| domainName | string | – | Primary domain / website URL (sent as domainName:{primaryLinkUrl}). |
| employees | number | – | Employee count. |
| extra | object | – | Passthrough object of additional/custom fields merged into the request body verbatim. |
| idealCustomerProfile | boolean | – | Whether this company matches the ideal customer profile. |
| linkedinUrl | string | – | LinkedIn URL (sent as linkedinLink:{primaryLinkUrl}). |
| name | string | yes | The company name (required). |
| xUrl | string | – | X/Twitter URL (sent as xLink:{primaryLinkUrl}). |
No output schema declared.
No examples provided.
twenty_create_note Create note ~94
Create a note. `title` is required; `body` holds the note content. (Attaching to records via noteTargets is out of scope.) Twenty REST: POST /rest/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | The note content/body. |
| extra | object | – | Passthrough object of additional/custom fields merged into the request body verbatim. |
| title | string | yes | The note title (required). |
No output schema declared.
No examples provided.
twenty_create_opportunity Create opportunity ~219
Create a new opportunity (deal). `name` is required; amountMicros combines with currencyCode into amount:{amountMicros,currencyCode}. Twenty REST: POST /rest/opportunities.
| Name | Type | Req | Description |
|---|---|---|---|
| amountMicros | number | – | Opportunity amount in micros (× 1,000,000). Sent as amount:{amountMicros,currencyCode}. |
| closeDate | string | – | Expected close date (ISO 8601). |
| companyId | string | – | Id of the associated company. |
| currencyCode | string | – | Currency code for the amount (default USD; only sent when amountMicros is provided). |
| extra | object | – | Passthrough object of additional/custom fields merged into the request body verbatim. |
| name | string | yes | The opportunity name (required). |
| pointOfContactId | string | – | Id of the point-of-contact person. |
| stage | string | – | Pipeline stage — e.g. SCREENING, MEETING, PROPOSAL, NEGOTIATION, CUSTOMER (custom pipelines vary). |
No output schema declared.
No examples provided.
twenty_create_person Create person ~222
Create a new person (contact). All fields optional; firstName/lastName combine into name:{firstName,lastName}. Twenty REST: POST /rest/people.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City. |
| companyId | string | – | Id of the company to link this person to. |
| extra | object | – | Passthrough object of additional/custom fields merged into the request body verbatim. |
| firstName | string | – | First name (combined into name:{firstName,lastName}). |
| jobTitle | string | – | Job title. |
| lastName | string | – | Last name (combined into name:{firstName,lastName}). |
| linkedinUrl | string | – | LinkedIn URL (sent as linkedinLink:{primaryLinkUrl}). |
| primaryEmail | string | – | Primary email address (sent as emails:{primaryEmail}). |
| primaryPhone | string | – | Primary phone number (sent as phones:{primaryPhoneNumber}). |
| xUrl | string | – | X/Twitter URL (sent as xLink:{primaryLinkUrl}). |
No output schema declared.
No examples provided.
twenty_create_task Create task ~125
Create a task. `title` is required. Twenty REST: POST /rest/tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| assigneeId | string | – | Id of the workspace member assigned to the task. |
| body | string | – | Task body / description. |
| dueAt | string | – | Due date/time (ISO 8601). |
| extra | object | – | Passthrough object of additional/custom fields merged into the request body verbatim. |
| status | string | – | Task status — e.g. TODO, IN_PROGRESS, DONE. |
| title | string | yes | The task title (required). |
No output schema declared.
No examples provided.
twenty_get_company Get company ~60
Get a single company by id. Twenty REST: GET /rest/companies/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | How deep to hydrate related records: 0, 1, or 2. |
| id | string | yes | The company id. |
No output schema declared.
No examples provided.
twenty_get_note Get note ~60
Get a single note by id. Twenty REST: GET /rest/notes/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | How deep to hydrate related records: 0, 1, or 2. |
| id | string | yes | The note id. |
No output schema declared.
No examples provided.
twenty_get_opportunity Get opportunity ~61
Get a single opportunity by id. Twenty REST: GET /rest/opportunities/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | How deep to hydrate related records: 0, 1, or 2. |
| id | string | yes | The opportunity id. |
No output schema declared.
No examples provided.
twenty_get_person Get person ~63
Get a single person (contact) by id. Twenty REST: GET /rest/people/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | How deep to hydrate related records: 0, 1, or 2. |
| id | string | yes | The person id. |
No output schema declared.
No examples provided.
twenty_get_task Get task ~59
Get a single task by id. Twenty REST: GET /rest/tasks/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | How deep to hydrate related records: 0, 1, or 2. |
| id | string | yes | The task id. |
No output schema declared.
No examples provided.
twenty_list_companies List companies ~242
List/filter companies. Supports cursor pagination, raw filter/order_by, and relation depth. Twenty REST: GET /rest/companies.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | How deep to hydrate related records: 0, 1, or 2. |
| ending_before | string | – | Pagination cursor — return records before this cursor (from a previous page's pageInfo). |
| filter | string | – | Raw Twenty filter string, passed verbatim as ?filter=. Syntax: field[comparator]:value, e.g. `employees[gte]:100` or `stage[eq]:"MEETING"`. Comparators: eq, neq, gt, gte, lt, lte, in, is, like, ilike… |
| limit | integer | – | Results per page (1-60, default 20 — Twenty caps at 60). |
| order_by | string | – | Raw Twenty ordering string, passed verbatim as ?order_by=, e.g. `createdAt[DescNullsLast]`. |
| starting_after | string | – | Pagination cursor — return records after this cursor (from a previous page's pageInfo). |
No output schema declared.
No examples provided.
twenty_list_metadata_objects List metadata objects ~50
List all objects (standard + custom) and their fields from the Twenty schema — use this to discover custom objects/fields and valid field names. Twenty REST: GET /rest/metadata/objects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
twenty_list_notes List notes ~241
List/filter notes. Supports cursor pagination, raw filter/order_by, and relation depth. Twenty REST: GET /rest/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | How deep to hydrate related records: 0, 1, or 2. |
| ending_before | string | – | Pagination cursor — return records before this cursor (from a previous page's pageInfo). |
| filter | string | – | Raw Twenty filter string, passed verbatim as ?filter=. Syntax: field[comparator]:value, e.g. `employees[gte]:100` or `stage[eq]:"MEETING"`. Comparators: eq, neq, gt, gte, lt, lte, in, is, like, ilike… |
| limit | integer | – | Results per page (1-60, default 20 — Twenty caps at 60). |
| order_by | string | – | Raw Twenty ordering string, passed verbatim as ?order_by=, e.g. `createdAt[DescNullsLast]`. |
| starting_after | string | – | Pagination cursor — return records after this cursor (from a previous page's pageInfo). |
No output schema declared.
No examples provided.
twenty_list_opportunities List opportunities ~245
List/filter opportunities (deals). Supports cursor pagination, raw filter/order_by, and relation depth. Twenty REST: GET /rest/opportunities.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | How deep to hydrate related records: 0, 1, or 2. |
| ending_before | string | – | Pagination cursor — return records before this cursor (from a previous page's pageInfo). |
| filter | string | – | Raw Twenty filter string, passed verbatim as ?filter=. Syntax: field[comparator]:value, e.g. `employees[gte]:100` or `stage[eq]:"MEETING"`. Comparators: eq, neq, gt, gte, lt, lte, in, is, like, ilike… |
| limit | integer | – | Results per page (1-60, default 20 — Twenty caps at 60). |
| order_by | string | – | Raw Twenty ordering string, passed verbatim as ?order_by=, e.g. `createdAt[DescNullsLast]`. |
| starting_after | string | – | Pagination cursor — return records after this cursor (from a previous page's pageInfo). |
No output schema declared.
No examples provided.
twenty_list_people List people ~243
List/filter people (contacts). Supports cursor pagination, raw filter/order_by, and relation depth. Twenty REST: GET /rest/people.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | How deep to hydrate related records: 0, 1, or 2. |
| ending_before | string | – | Pagination cursor — return records before this cursor (from a previous page's pageInfo). |
| filter | string | – | Raw Twenty filter string, passed verbatim as ?filter=. Syntax: field[comparator]:value, e.g. `employees[gte]:100` or `stage[eq]:"MEETING"`. Comparators: eq, neq, gt, gte, lt, lte, in, is, like, ilike… |
| limit | integer | – | Results per page (1-60, default 20 — Twenty caps at 60). |
| order_by | string | – | Raw Twenty ordering string, passed verbatim as ?order_by=, e.g. `createdAt[DescNullsLast]`. |
| starting_after | string | – | Pagination cursor — return records after this cursor (from a previous page's pageInfo). |
No output schema declared.
No examples provided.
twenty_list_tasks List tasks ~240
List/filter tasks. Supports cursor pagination, raw filter/order_by, and relation depth. Twenty REST: GET /rest/tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | How deep to hydrate related records: 0, 1, or 2. |
| ending_before | string | – | Pagination cursor — return records before this cursor (from a previous page's pageInfo). |
| filter | string | – | Raw Twenty filter string, passed verbatim as ?filter=. Syntax: field[comparator]:value, e.g. `employees[gte]:100` or `stage[eq]:"MEETING"`. Comparators: eq, neq, gt, gte, lt, lte, in, is, like, ilike… |
| limit | integer | – | Results per page (1-60, default 20 — Twenty caps at 60). |
| order_by | string | – | Raw Twenty ordering string, passed verbatim as ?order_by=, e.g. `createdAt[DescNullsLast]`. |
| starting_after | string | – | Pagination cursor — return records after this cursor (from a previous page's pageInfo). |
No output schema declared.
No examples provided.
twenty_update_company Update company ~185
Update fields on an existing company. Only provided fields change. Twenty REST: PATCH /rest/companies/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| addressCity | string | – | City (sent as address:{addressCity}). |
| domainName | string | – | Primary domain / website URL (sent as domainName:{primaryLinkUrl}). |
| employees | number | – | Employee count. |
| extra | object | – | Passthrough object of additional/custom fields merged into the request body verbatim. |
| id | string | yes | The company id to update. |
| idealCustomerProfile | boolean | – | Whether this company matches the ideal customer profile. |
| linkedinUrl | string | – | LinkedIn URL (sent as linkedinLink:{primaryLinkUrl}). |
| name | string | – | The company name. |
| xUrl | string | – | X/Twitter URL (sent as xLink:{primaryLinkUrl}). |
No output schema declared.
No examples provided.
twenty_update_opportunity Update opportunity ~213
Update fields on an existing opportunity. Only provided fields change. Twenty REST: PATCH /rest/opportunities/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| amountMicros | number | – | Opportunity amount in micros (× 1,000,000). Sent as amount:{amountMicros,currencyCode}. |
| closeDate | string | – | Expected close date (ISO 8601). |
| companyId | string | – | Id of the associated company. |
| currencyCode | string | – | Currency code for the amount (default USD; only sent when amountMicros is provided). |
| extra | object | – | Passthrough object of additional/custom fields merged into the request body verbatim. |
| id | string | yes | The opportunity id to update. |
| name | string | – | The opportunity name. |
| pointOfContactId | string | – | Id of the point-of-contact person. |
| stage | string | – | Pipeline stage — e.g. SCREENING, MEETING, PROPOSAL, NEGOTIATION, CUSTOMER (custom pipelines vary). |
No output schema declared.
No examples provided.
twenty_update_person Update person ~223
Update fields on an existing person. Only provided fields change. Twenty REST: PATCH /rest/people/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City. |
| companyId | string | – | Id of the company to link this person to. |
| extra | object | – | Passthrough object of additional/custom fields merged into the request body verbatim. |
| firstName | string | – | First name (combined into name:{firstName,lastName}). |
| id | string | yes | The person id to update. |
| jobTitle | string | – | Job title. |
| lastName | string | – | Last name (combined into name:{firstName,lastName}). |
| linkedinUrl | string | – | LinkedIn URL (sent as linkedinLink:{primaryLinkUrl}). |
| primaryEmail | string | – | Primary email address (sent as emails:{primaryEmail}). |
| primaryPhone | string | – | Primary phone number (sent as phones:{primaryPhoneNumber}). |
| xUrl | string | – | X/Twitter URL (sent as xLink:{primaryLinkUrl}). |
No output schema declared.
No examples provided.
twenty_update_task Update task ~139
Update fields on an existing task. Only provided fields change. Twenty REST: PATCH /rest/tasks/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| assigneeId | string | – | Id of the workspace member assigned to the task. |
| body | string | – | Task body / description. |
| dueAt | string | – | Due date/time (ISO 8601). |
| extra | object | – | Passthrough object of additional/custom fields merged into the request body verbatim. |
| id | string | yes | The task id to update. |
| status | string | – | Task status — e.g. TODO, IN_PROGRESS, DONE. |
| title | string | – | The task title. |
No output schema declared.
No examples provided.
What is the io.usefulapi/twenty MCP server?
io.usefulapi/twenty is an MCP server listed in the public MCP registry as io.usefulapi/twenty. Read people, companies, opportunities, notes and tasks; create and update records in Twenty CRM. This page covers its hosted endpoint (https://twenty.usefulapi.io/mcp).
Is the io.usefulapi/twenty MCP server safe to use?
io.usefulapi/twenty scores 84 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/twenty MCP server expose?
io.usefulapi/twenty exposes 20 tools: twenty_list_metadata_objects, twenty_list_people, twenty_get_person, twenty_list_companies, twenty_get_company, and 15 more. Their descriptions and schemas cost roughly 3,156 tokens of context every time the server is loaded.
Does the io.usefulapi/twenty MCP server require authentication?
Yes. io.usefulapi/twenty 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/twenty MCP server still maintained?
io.usefulapi/twenty is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.