Cogmento MCP by usefulapi
REMOTE · COGMENTO.USEFULAPI.IO
Read Cogmento CRM contacts, companies, deals, tasks and cases; create records and complete tasks.
Available components
Last scanned (13 minutes ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 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.
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 Nov 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.17 → 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 “check_the_account_setup” functional
- New prompt “keep_follow_up_tasks_on_track” functional
- New prompt “log_a_new_company_and_deal” functional
- New prompt “review_the_deal_pipeline” functional
- New prompt “update_a_deal” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.7.0 → 1.9.0 functional
- Server version: 1.6.0 → 1.7.0 functional
- Server version: 1.5.2 → 1.6.0 functional
- 30 Oct 26 +1
- Server version: 1.5.1 → 1.5.2 functional
- Server version: 1.5.0 → 1.5.1 functional
- 29 Oct 26 0
- Server version: 1.4.0 → 1.5.0 functional
- Server version: 1.3.0 → 1.4.0 functional
- 28 Oct 26 +1
- Server version: 1.1.0 → 1.3.0 functional
- 27 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.1.0 functional
- 26 Oct 26 62
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 5 Nov 2026 · Probed https://cogmento.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 cogmento.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | 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://cogmento.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/cogmento/ |
| http (plaintext) | http://cogmento.usefulapi.io/mcp | Inconclusive | 302 | http://cogmento.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 →
cogmento_aggregate_deals Aggregate deal values ~83
Sums and counts deals grouped by a field (default grouping as Cogmento chooses; e.g. field=stage). GET /deals/aggregate/.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | – | Field to group by, e.g. stage. |
| filters | array | – | Conditions, all of which must match (AND). Dates are yyyy-mm-dd. |
No output schema declared.
No examples provided.
cogmento_complete_task Complete task ~54
WRITE: mark a task complete, stamping who completed it and when. A recurring task also gets its next occurrence. POST /tasks/{id}/complete/.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | Record id (UUID). |
No output schema declared.
No examples provided.
cogmento_create_case Create case ~75
WRITE: create a case. POST /cases/.
| Name | Type | Req | Description |
|---|---|---|---|
| close_date | string | – | A date, yyyy-mm-dd. |
| description | string | – | – |
| rating | integer | – | A 1-5 rating. |
| tags | array | – | Tags to put on the record. |
| title | string | yes | – |
No output schema declared.
No examples provided.
cogmento_create_company Create company ~71
WRITE: create a company. POST /companies/.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| name | string | yes | – |
| rating | integer | – | A 1-5 rating. |
| tags | array | – | Tags to put on the record. |
| url | string | – | The company's website. |
No output schema declared.
No examples provided.
cogmento_create_contact Create contact ~124
WRITE: create a contact. Needs first and last name; email and phone are optional. POST /contacts/.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| string | – | Email address; stored as an Email channel. | |
| first_name | string | yes | – |
| last_name | string | yes | – |
| middle_name | string | – | – |
| phone | string | – | Phone number, ideally in international format (+14155550100). |
| rating | integer | – | A 1-5 rating. |
| tags | array | – | Tags to put on the record. |
No output schema declared.
No examples provided.
cogmento_create_deal Create deal ~87
WRITE: create a deal. POST /deals/.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | The deal value. |
| close_date | string | – | A date, yyyy-mm-dd. |
| description | string | – | – |
| rating | integer | – | A 1-5 rating. |
| tags | array | – | Tags to put on the record. |
| title | string | yes | – |
No output schema declared.
No examples provided.
cogmento_create_task Create task ~75
WRITE: create a task. POST /tasks/.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| due_date | string | – | A date, yyyy-mm-dd. |
| rating | integer | – | A 1-5 rating. |
| tags | array | – | Tags to put on the record. |
| title | string | yes | – |
No output schema declared.
No examples provided.
cogmento_get_account Get account ~38
The Cogmento account: name, country, settings, billing plan, trial days left and number of users. GET /account/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cogmento_get_case Get case ~34
One case record. GET /cases/{id}/.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | Record id (UUID). |
No output schema declared.
No examples provided.
cogmento_get_company Get company ~41
One full company record with its contacts and related records. GET /companies/{id}/.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | Record id (UUID). |
No output schema declared.
No examples provided.
cogmento_get_contact Get contact ~48
One full contact record, including its related tasks, cases, calls, events and documents. GET /contacts/{id}/.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | Record id (UUID). |
No output schema declared.
No examples provided.
cogmento_get_current_user Get current user ~39
The Cogmento user this API token belongs to: id, name, email, timezone and account id. GET /auth/user/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cogmento_get_deal Get deal ~45
One full deal record with its contacts, products and related records. GET /deals/{id}/.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | string | yes | Record id (UUID). |
No output schema declared.
No examples provided.
cogmento_get_deal_pipeline_summary Get deal pipeline summary ~69
Totals by pipeline stage: how many deals sit at each stage and what they are worth. Optional filters narrow the deals counted. GET /deals/summary/.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | – | Conditions, all of which must match (AND). Dates are yyyy-mm-dd. |
No output schema declared.
No examples provided.
cogmento_get_task Get task ~34
One task record. GET /tasks/{id}/.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | Record id (UUID). |
No output schema declared.
No examples provided.
cogmento_get_templates Get field templates ~63
The field definitions (names, labels, types, options) of the account's templates for each record type: contacts, companies, deals, cases, tasks. Use it to learn the custom field names for filters, creates and field updates. GET /templates/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cogmento_list_calls List calls ~132
The account's call records, most recent first: logged manual calls and calls placed through the browser dialer. GET /calls/.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | – | Conditions, all of which must match (AND). Dates are yyyy-mm-dd. |
| limit | integer | – | Rows per page, 1-100 (default 25). |
| sort | string | – | Field to sort by, e.g. created_at; prefix with - for descending, e.g. -last_modified. |
| start | integer | – | Row offset to start from (default 0). Pass the previous reply's next_start. |
No output schema declared.
No examples provided.
cogmento_list_cases List cases ~132
List or search cases (support or project cases: title, close date, assigned users, deal, company). GET /cases/.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | – | Conditions, all of which must match (AND). Dates are yyyy-mm-dd. |
| limit | integer | – | Rows per page, 1-100 (default 25). |
| sort | string | – | Field to sort by, e.g. created_at; prefix with - for descending, e.g. -last_modified. |
| start | integer | – | Row offset to start from (default 0). Pass the previous reply's next_start. |
No output schema declared.
No examples provided.
cogmento_list_companies List companies ~122
List or search companies (name, website, contacts). GET /companies/.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | – | Conditions, all of which must match (AND). Dates are yyyy-mm-dd. |
| limit | integer | – | Rows per page, 1-100 (default 25). |
| sort | string | – | Field to sort by, e.g. created_at; prefix with - for descending, e.g. -last_modified. |
| start | integer | – | Row offset to start from (default 0). Pass the previous reply's next_start. |
No output schema declared.
No examples provided.
cogmento_list_contacts List contacts ~138
List or search contacts (name, email and phone channels, company). Filter on any field, e.g. first_name contains 'Eric'. GET /contacts/.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | – | Conditions, all of which must match (AND). Dates are yyyy-mm-dd. |
| limit | integer | – | Rows per page, 1-100 (default 25). |
| sort | string | – | Field to sort by, e.g. created_at; prefix with - for descending, e.g. -last_modified. |
| start | integer | – | Row offset to start from (default 0). Pass the previous reply's next_start. |
No output schema declared.
No examples provided.
cogmento_list_deal_stages List deal contact stages ~41
The account-wide stages a contact can be at within a deal (for example Champion or Decision maker). GET /deals/stages/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cogmento_list_deals List deals ~129
List or search deals (title, amount, close date, assigned users, products). GET /deals/.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | – | Conditions, all of which must match (AND). Dates are yyyy-mm-dd. |
| limit | integer | – | Rows per page, 1-100 (default 25). |
| sort | string | – | Field to sort by, e.g. created_at; prefix with - for descending, e.g. -last_modified. |
| start | integer | – | Row offset to start from (default 0). Pass the previous reply's next_start. |
No output schema declared.
No examples provided.
cogmento_list_products List products ~126
List the product catalogue (name, prices) that deals and invoices draw on. GET /products/.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | – | Conditions, all of which must match (AND). Dates are yyyy-mm-dd. |
| limit | integer | – | Rows per page, 1-100 (default 25). |
| sort | string | – | Field to sort by, e.g. created_at; prefix with - for descending, e.g. -last_modified. |
| start | integer | – | Row offset to start from (default 0). Pass the previous reply's next_start. |
No output schema declared.
No examples provided.
cogmento_list_tasks List tasks ~140
List or search tasks (title, due date, completion date, assigned users, linked deal/contact/case). Filter e.g. on due_date. GET /tasks/.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | – | Conditions, all of which must match (AND). Dates are yyyy-mm-dd. |
| limit | integer | – | Rows per page, 1-100 (default 25). |
| sort | string | – | Field to sort by, e.g. created_at; prefix with - for descending, e.g. -last_modified. |
| start | integer | – | Row offset to start from (default 0). Pass the previous reply's next_start. |
No output schema declared.
No examples provided.
cogmento_set_deal_contact_stage Set a contact's stage in a deal ~106
WRITE: record where a contact sits in a deal (a stage from cogmento_list_deal_stages). The contact is attached to the deal if it is not already. POST /deals/{id}/contact/{id}/stage/.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | Record id (UUID). |
| deal_id | string | yes | Record id (UUID). |
| stage | string | yes | A stage name from cogmento_list_deal_stages. |
No output schema declared.
No examples provided.
cogmento_update_record_field Update one field of a record ~157
WRITE: change a single field of a contact, company, deal, task or case, e.g. a deal's status or a contact's first_name. Custom field names come from cogmento_get_templates. System fields (id, acl, private, timestamps) are refused. PATCH /<type>/{id}/.
| Name | Type | Req | Description |
|---|---|---|---|
| field_name | string | yes | Field to set, e.g. first_name, title, status, amount, due_date. |
| record_id | string | yes | Record id (UUID). |
| record_type | string | yes | contact, company, deal, task or case. |
| value | – | yes | The new value (type must match the field; dates yyyy-mm-dd; null clears a field). |
No output schema declared.
No examples provided.
How do I install the Cogmento MCP by usefulapi server?
Cogmento MCP by usefulapi is a hosted endpoint at https://cogmento.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 · cogmento.usefulapi.io
claude mcp add --transport http io-usefulapi-cogmento 'https://cogmento.usefulapi.io/mcp'
What is the Cogmento MCP by usefulapi server?
Cogmento MCP by usefulapi is listed in the public MCP registry as io.usefulapi/cogmento. Read Cogmento CRM contacts, companies, deals, tasks and cases; create records and complete tasks. This page covers its hosted endpoint (https://cogmento.usefulapi.io/mcp).
Is the Cogmento MCP by usefulapi server safe to use?
Cogmento 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 Cogmento MCP by usefulapi server expose?
Cogmento MCP by usefulapi exposes 26 tools: cogmento_get_current_user, cogmento_get_account, cogmento_get_templates, cogmento_list_contacts, cogmento_get_contact, and 21 more. Their descriptions and schemas cost roughly 2,203 tokens of context every time the server is loaded.
Does the Cogmento MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Cogmento 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 Cogmento MCP by usefulapi server still maintained?
Cogmento MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.