Teamgate MCP by usefulapi
REMOTE · TEAMGATE.USEFULAPI.IO
Manage Teamgate CRM leads, people, companies, deals, activities and notes.
Available components
Last scanned (9 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 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 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 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
- 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 & 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 Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 4381 tokens (~128/item across 34 items; 34 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 34 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 35 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
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.0.0 → 1.1.0 functional
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 60
First indexed and scored.
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 17 Oct 2026 · Probed https://teamgate.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 teamgate.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 | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://teamgate.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://teamgate.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://teamgate.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://teamgate.usefulapi.io/mcp |
| Authorisation server | https://teamgate.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://teamgate.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/teamgate/ |
| http (plaintext) | http://teamgate.usefulapi.io/mcp | Inconclusive | 302 | http://teamgate.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 →
teamgate_add_note Add note ~83
WRITE: add a note to one or more leads, companies or deals. The note cannot be edited or removed with these tools. POST /events.
| Name | Type | Req | Description |
|---|---|---|---|
| company_ids | array | – | Companies to link. |
| deal_ids | array | – | Deals to link. |
| lead_ids | array | – | Leads to link. |
| text | string | yes | The note text. |
No output schema declared.
No examples provided.
teamgate_create_activity Create activity ~153
WRITE: create a task, call or appointment, optionally linked to leads, companies or deals. Teamgate may send reminders to the owner. POST /events.
| Name | Type | Req | Description |
|---|---|---|---|
| company_ids | array | – | Companies to link. |
| deal_ids | array | – | Deals to link. |
| description | string | – | Details. |
| end | string | – | End (RFC 3339 date-time with timezone). |
| lead_ids | array | – | Leads to link. |
| name | string | yes | Activity title. |
| owner_id | integer | – | Owner user id (see teamgate_list_users). |
| start | string | – | Start (RFC 3339 date-time with timezone). |
| type | string | yes | Kind of activity. |
No output schema declared.
No examples provided.
teamgate_create_company Create company ~154
WRITE: create a company. POST /companies.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_status | integer | – | 0 = non customer, 1 = past customer, 2 = customer. |
| string | – | Email address. | |
| industry | string | – | Industry name (created if it does not exist). |
| name | string | yes | Company name. |
| owner_id | integer | – | Owner user id (see teamgate_list_users). |
| phone | string | – | Phone number. |
| source | string | – | Source name (created if it does not exist). |
| starred | boolean | – | Star the record. |
| tags | array | – | Tags to set on the record. |
| vat_code | string | – | VAT identification number. |
No output schema declared.
No examples provided.
teamgate_create_deal Create deal ~190
WRITE: create a deal for a buyer (a person or company). POST /deals.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_id | integer | yes | Id of the person or company that buys, as returned by the list tools. |
| estimated_closure_date | string | – | Expected closing date-time (RFC 3339 with timezone). |
| name | string | yes | Deal name. |
| owner_id | integer | – | Owner user id (see teamgate_list_users). |
| price_currency | string | – | Currency code, e.g. EUR. |
| price_value | number | – | Deal value. |
| source | string | – | Source name (created if it does not exist). |
| stage_id | integer | – | Pipeline stage id (see teamgate_get_pipeline). |
| starred | boolean | – | Star the record. |
| status | string | – | Deal status. |
| tags | array | – | Tags to set on the record. |
No output schema declared.
No examples provided.
teamgate_create_lead Create lead ~216
WRITE: create a lead. Give a person's name, or a company_name for a company lead. Teamgate may start workflows or notifications for new leads. POST /leads.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | – | Company name for a company lead (required unless name is given). |
| string | – | Email address. | |
| industry | string | – | Industry name (created if it does not exist). |
| job_title | string | – | Job title (used only together with company_name). |
| name | string | – | Person's full name (required unless company_name is given). |
| owner_id | integer | – | Owner user id (see teamgate_list_users). |
| phone | string | – | Phone number. |
| source | string | – | Source name (created if it does not exist). |
| starred | boolean | – | Star the record. |
| status | string | – | Lead status name, e.g. 'New' (created if it does not exist). |
| tags | array | – | Tags to set on the record. |
No output schema declared.
No examples provided.
teamgate_create_person Create person ~192
WRITE: create a person (contact). Optionally link them to a company with their job title. POST /people.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | – | Id of the company the person works at. |
| customer_status | integer | – | 0 = non customer, 1 = past customer, 2 = customer. |
| string | – | Email address. | |
| industry | string | – | Industry name (created if it does not exist). |
| job_title | string | – | Job title (used only together with company_id). |
| name | string | yes | Person's full name. |
| owner_id | integer | – | Owner user id (see teamgate_list_users). |
| phone | string | – | Phone number. |
| source | string | – | Source name (created if it does not exist). |
| starred | boolean | – | Star the record. |
| tags | array | – | Tags to set on the record. |
No output schema declared.
No examples provided.
teamgate_get_activity Get activity ~42
One activity (task, call, appointment or note) by id. GET /events/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_id | integer | yes | Teamgate activity id. |
No output schema declared.
No examples provided.
teamgate_get_company Get company ~56
One company by id with all its details. GET /companies/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | yes | Teamgate company id. |
| include_custom_fields | boolean | – | Include custom field values in the reply (default false). |
No output schema declared.
No examples provided.
teamgate_get_deal Get deal ~66
One deal by id with value, stage, status, owner, buyer and dates. GET /deals/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | integer | yes | Teamgate deal id. |
| include_custom_fields | boolean | – | Include custom field values in the reply (default false). |
No output schema declared.
No examples provided.
teamgate_get_lead Get lead ~58
One lead by id with all its details. GET /leads/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_custom_fields | boolean | – | Include custom field values in the reply (default false). |
| lead_id | integer | yes | Teamgate lead id. |
No output schema declared.
No examples provided.
teamgate_get_person Get person ~56
One person by id with all their details. GET /people/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_custom_fields | boolean | – | Include custom field values in the reply (default false). |
| person_id | integer | yes | Teamgate person id. |
No output schema declared.
No examples provided.
teamgate_get_pipeline Get pipeline ~39
One sales pipeline by id, with its stages. GET /pipelines/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_id | integer | yes | Teamgate pipeline id. |
No output schema declared.
No examples provided.
teamgate_get_user Get user ~35
One Teamgate user by id. GET /users/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | integer | yes | Teamgate user id. |
No output schema declared.
No examples provided.
teamgate_list_activities List activities ~71
List activities (tasks, calls, appointments and notes) across the account. GET /events.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
teamgate_list_companies List companies ~257
List or search companies with owner, industry, source, customer and prospect status and contact details. Filter by name, email, phone, owner, VAT code or creation date. GET /companies.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only companies created at or after this RFC 3339 date or date-time. |
| created_before | string | – | Only companies created at or before this RFC 3339 date or date-time. |
| customer_status | integer | – | 0 = non customer, 1 = past customer, 2 = customer. |
| string | – | Part of an email address (at least 3 characters). | |
| include_custom_fields | boolean | – | Include custom field values in the reply (default false). |
| limit | integer | – | Results per page, 1-100 (default 25). |
| name | string | – | Part of the company name. |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
| owner_id | integer | – | Only companies owned by this user id. |
| phone | string | – | The last digits of a phone number (at least 3 characters). |
| vat_code | string | – | Exact VAT identification number. |
No output schema declared.
No examples provided.
teamgate_list_company_people List people of a company ~81
List the people who work at one company. GET /companies/{id}/people.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | yes | Teamgate company id. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
teamgate_list_contact_deals List deals of a person or company ~113
List the deals that belong to one person or one company. GET /people/{id}/deals or /companies/{id}/deals.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | Teamgate person or company id. |
| contact_type | string | yes | Whether contact_id is a person or a company. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
teamgate_list_custom_fields List custom fields ~74
List the custom field definitions of the account (id, name, type, module). GET /customFields.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
teamgate_list_deal_stages List stages of a deal ~62
List the pipeline stages that one deal can be in (id, name, win probability; the deal's current stage is marked selected). GET /deals/{id}/stages.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | integer | yes | Teamgate deal id. |
No output schema declared.
No examples provided.
teamgate_list_deals List deals ~225
List or search deals (sales opportunities) with value, stage, status, owner and expected closing date. Filter by name, status, stage, owner, source or creation date. GET /deals.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only deals created at or after this RFC 3339 date or date-time. |
| created_before | string | – | Only deals created at or before this RFC 3339 date or date-time. |
| include_custom_fields | boolean | – | Include custom field values in the reply (default false). |
| limit | integer | – | Results per page, 1-100 (default 25). |
| name | string | – | Part of the deal name. |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
| owner_id | integer | – | Only deals owned by this user id. |
| source | string | – | Exact source name. |
| stage_id | integer | – | Only deals in this pipeline stage id (see teamgate_get_pipeline). |
| status | string | – | Deal status. |
No output schema declared.
No examples provided.
teamgate_list_industries List industries ~65
List the industries of the account. GET /industries.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
teamgate_list_lead_statuses List lead statuses ~80
List the lead statuses of the account (use the names as the status filter or value on leads). GET /leadsStatuses.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
teamgate_list_leads List leads ~283
List or search leads (unqualified prospects) with owner, status, source, industry and contact details. Filter by name, email, phone, status, owner, source, star or creation date. GET /leads.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only leads created at or after this RFC 3339 date or date-time. |
| created_before | string | – | Only leads created at or before this RFC 3339 date or date-time. |
| string | – | Part of an email address (at least 3 characters). | |
| include_custom_fields | boolean | – | Include custom field values in the reply (default false). |
| limit | integer | – | Results per page, 1-100 (default 25). |
| name | string | – | Part of the lead's name. |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
| owner_id | integer | – | Only leads owned by this user id. |
| phone | string | – | The last digits of a phone number (at least 3 characters). |
| source | string | – | Exact source name. |
| starred | boolean | – | Only starred (true) or not starred (false) leads. |
| status | string | – | Exact lead status name, e.g. 'New'. See teamgate_list_lead_statuses. |
No output schema declared.
No examples provided.
teamgate_list_people List people ~245
List or search people (contacts) with job title, company, owner, source and contact details. Filter by name, email, phone, owner, customer status or creation date. GET /people.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only people created at or after this RFC 3339 date or date-time. |
| created_before | string | – | Only people created at or before this RFC 3339 date or date-time. |
| customer_status | integer | – | 0 = non customer, 1 = past customer, 2 = customer. |
| string | – | Part of an email address (at least 3 characters). | |
| include_custom_fields | boolean | – | Include custom field values in the reply (default false). |
| limit | integer | – | Results per page, 1-100 (default 25). |
| name | string | – | Part of the person's name. |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
| owner_id | integer | – | Only people owned by this user id. |
| phone | string | – | The last digits of a phone number (at least 3 characters). |
No output schema declared.
No examples provided.
teamgate_list_pipelines List pipelines ~89
List the sales pipelines (id and name). Use teamgate_get_pipeline for the stages of one. GET /pipelines.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| name | string | – | Part of the pipeline name. |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
teamgate_list_products List products ~80
List the products of the catalogue (id, name, price). GET /products.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| name | string | – | Part of the product name. |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
teamgate_list_record_activities List activities of a record ~125
List the activities (tasks, calls, appointments, notes) linked to one lead, person, company or deal. GET /{leads|people|companies|deals}/{id}/events.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
| record_id | integer | yes | Teamgate id of the lead, person, company or deal. |
| record_type | string | yes | The kind of record. |
No output schema declared.
No examples provided.
teamgate_list_sources List sources ~70
List the lead/deal sources of the account (where records come from). GET /sources.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
teamgate_list_users List users ~125
List the Teamgate users of the account with id, name and username. Use the ids as owner_id filters and values. GET /users.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Exact email of the user. | |
| is_active | boolean | – | Only active (true) or only inactive (false) users. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| name | string | – | Part of the user's first name. |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
teamgate_search Search records ~98
Search leads, people, companies and deals by name in one request. GET /global.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| modules | array | – | Which kinds of record to search (default all four). |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
| query | string | yes | Text to find in record names. |
No output schema declared.
No examples provided.
teamgate_update_company Update company ~167
WRITE: change fields of one company. Only the fields you pass are sent; this overwrites their current values. PUT /companies/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | yes | Teamgate company id. |
| customer_status | integer | – | 0 = non customer, 1 = past customer, 2 = customer. |
| industry | string | – | Industry name (created if it does not exist). |
| name | string | – | New name. |
| owner_id | integer | – | Owner user id (see teamgate_list_users). |
| source | string | – | Source name (created if it does not exist). |
| starred | boolean | – | Star the record. |
| tags | array | – | Tags to set on the record. |
| vat_code | string | – | VAT identification number. |
No output schema declared.
No examples provided.
teamgate_update_deal Update deal ~220
WRITE: change fields of one deal, for example move it to another stage or mark it won or lost. Only the fields you pass are sent; this overwrites their current values. PUT /deals/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_id | integer | – | New buyer (person or company id). |
| deal_id | integer | yes | Teamgate deal id. |
| estimated_closure_date | string | – | Expected closing date-time (RFC 3339 with timezone). |
| name | string | – | New deal name. |
| owner_id | integer | – | Owner user id (see teamgate_list_users). |
| price_currency | string | – | Currency code, e.g. EUR. |
| price_value | number | – | Deal value. |
| source | string | – | Source name (created if it does not exist). |
| stage_id | integer | – | Pipeline stage id (see teamgate_get_pipeline). |
| starred | boolean | – | Star the record. |
| status | string | – | Deal status. |
| tags | array | – | Tags to set on the record. |
No output schema declared.
No examples provided.
teamgate_update_lead Update lead ~145
WRITE: change fields of one lead. Only the fields you pass are sent; this overwrites their current values. PUT /leads/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | – | Industry name (created if it does not exist). |
| lead_id | integer | yes | Teamgate lead id. |
| name | string | – | New name. |
| owner_id | integer | – | Owner user id (see teamgate_list_users). |
| source | string | – | Source name (created if it does not exist). |
| starred | boolean | – | Star the record. |
| status | string | – | New lead status name. |
| tags | array | – | Tags to set on the record. |
No output schema declared.
No examples provided.
teamgate_update_person Update person ~156
WRITE: change fields of one person. Only the fields you pass are sent; this overwrites their current values. PUT /people/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_status | integer | – | 0 = non customer, 1 = past customer, 2 = customer. |
| industry | string | – | Industry name (created if it does not exist). |
| name | string | – | New name. |
| owner_id | integer | – | Owner user id (see teamgate_list_users). |
| person_id | integer | yes | Teamgate person id. |
| source | string | – | Source name (created if it does not exist). |
| starred | boolean | – | Star the record. |
| tags | array | – | Tags to set on the record. |
No output schema declared.
No examples provided.
How do I install the Teamgate MCP by usefulapi server?
Teamgate MCP by usefulapi is a hosted endpoint at https://teamgate.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 · teamgate.usefulapi.io
claude mcp add --transport http io-usefulapi-teamgate 'https://teamgate.usefulapi.io/mcp'
What is the Teamgate MCP by usefulapi server?
Teamgate MCP by usefulapi is listed in the public MCP registry as io.usefulapi/teamgate. Manage Teamgate CRM leads, people, companies, deals, activities and notes. This page covers its hosted endpoint (https://teamgate.usefulapi.io/mcp).
Is the Teamgate MCP by usefulapi server safe to use?
Teamgate MCP by usefulapi scores 65 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 Teamgate MCP by usefulapi server expose?
Teamgate MCP by usefulapi exposes 34 tools: teamgate_list_users, teamgate_get_user, teamgate_list_leads, teamgate_get_lead, teamgate_list_lead_statuses, and 29 more. Their descriptions and schemas cost roughly 4,171 tokens of context every time the server is loaded.
Does the Teamgate MCP by usefulapi server require authentication?
Yes. Teamgate MCP by usefulapi 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 Teamgate MCP by usefulapi server still maintained?
Teamgate MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.