Twenty MCP by usefulapi
REMOTE · TWENTY.USEFULAPI.IO
Read people, companies, opportunities, notes and tasks; create and update records in Twenty CRM.
Available components
Last scanned (3 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 Nov 2026.
Category CRM and Sales
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. 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
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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
- 2 Nov 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “add_or_update_a_person_or_company” functional
- New prompt “check_open_tasks_and_their_due_dates” functional
- New prompt “create_or_update_an_opportunity” functional
- New prompt “review_open_opportunities_and_their_amounts” functional
- New prompt “show_what_the_crm_holds_on_a_company” functional
- New prompt “write_a_note_or_create_and_update_a_task” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 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 6 Nov 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 | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.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. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
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 | Redirected | 302 | https://usefulapi.io/twenty/ |
| http (plaintext) | http://twenty.usefulapi.io/mcp | Inconclusive | 302 | http://twenty.usefulapi.io/mcp |
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.
How do I install the Twenty MCP by usefulapi server?
Twenty MCP by usefulapi 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'
What is the Twenty MCP by usefulapi server?
Twenty MCP by usefulapi is 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 Twenty MCP by usefulapi server safe to use?
Twenty MCP by usefulapi scores 18 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 Twenty MCP by usefulapi server expose?
Twenty MCP by usefulapi 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 Twenty MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Twenty MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Twenty MCP by usefulapi server still maintained?
Twenty MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Twenty MCP by usefulapi server?
VerifyMCP ran 4 checks on Twenty MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Twenty MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.