io.usefulapi/insightly
REMOTE · INSIGHTLY.USEFULAPI.IO · SCANNED OCT 4
Read and write Insightly contacts, organisations, leads, opportunities, tasks and notes.
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 Security89
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3794 tokens (~180/item across 21 items; 21 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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/insightly MCP server?
io.usefulapi/insightly is a hosted endpoint at https://insightly.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 · insightly.usefulapi.io
claude mcp add --transport http io-usefulapi-insightly 'https://insightly.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-insightly": {
"url": "https://insightly.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-insightly": {
"type": "http",
"url": "https://insightly.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-insightly] url = "https://insightly.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-insightly": {
"type": "remote",
"url": "https://insightly.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-insightly --url 'https://insightly.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-insightly:
url: "https://insightly.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-insightly": {
"Transport": "http",
"Url": "https://insightly.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-insightly -t streamable-http -u 'https://insightly.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-insightly": {
"type": "http",
"url": "https://insightly.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.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +56
- HTTPS: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.07 ▲ functional
- Server version: 1.0.0 → 1.5.1 functional
- 1 Oct 26 −51
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 30 Sept 26 +51
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 71 functional
- First check of Schema quality: good functional
- 29 Sept 26 18
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 4 Oct 2026 · Probed https://insightly.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 insightly.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://insightly.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://insightly.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://insightly.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://insightly.usefulapi.io/mcp |
| Authorisation server | https://insightly.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://insightly.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://insightly.usefulapi.io/mcp | HTTPS enforced | 301 | https://insightly.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 →
insightly_add_note Add a note to a record ~94
Add a note (title + body) to a Contact, Organisation, Lead, Opportunity or Project. Insightly: POST /<Object>/{id}/Notes.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Note body (may contain HTML). |
| id | integer | yes | The record's numeric id. |
| object | string | yes | The record type to attach the note to. |
| title | string | yes | Note title (required). |
No output schema declared.
No examples provided.
insightly_create_contact Create a contact ~227
Create a contact (first_name is required). Insightly: POST /Contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| address_mail_city | string | – | – |
| address_mail_country | string | – | – |
| address_mail_postcode | string | – | – |
| address_mail_state | string | – | – |
| address_mail_street | string | – | – |
| background | string | – | Background / description text. |
| custom_fields | array | – | Custom field values to set. |
| email_address | string | – | Primary email. |
| email_opted_out | boolean | – | Opted out of email. |
| first_name | string | yes | First name (required). |
| last_name | string | – | Last name. |
| organisation_id | integer | – | Id of the contact's organisation. |
| owner_user_id | integer | – | Owning user's id. |
| phone | string | – | Business phone. |
| phone_mobile | string | – | Mobile phone. |
| salutation | string | – | e.g. Mr, Ms, Dr. |
| social_linkedin | string | – | LinkedIn URL. |
| title | string | – | Job title. |
No output schema declared.
No examples provided.
insightly_create_lead Create a lead ~318
Create a lead (last_name is required). Insightly's schema also marks lead_status_id and lead_source_id as required — get valid ids from insightly_list_lead_statuses / insightly_list_lead_sources. Insightly: POST /Leads.
| Name | Type | Req | Description |
|---|---|---|---|
| address_city | string | – | – |
| address_country | string | – | – |
| address_postcode | string | – | – |
| address_state | string | – | – |
| address_street | string | – | – |
| custom_fields | array | – | Custom field values to set. |
| string | – | Email address. | |
| email_opted_out | boolean | – | – |
| employee_count | integer | – | – |
| first_name | string | – | – |
| industry | string | – | – |
| last_name | string | yes | Last name (required). |
| lead_description | string | – | Description / notes on the lead. |
| lead_rating | integer | – | Rating, e.g. 1-5. |
| lead_source_id | integer | – | Source id — see insightly_list_lead_sources. |
| lead_status_id | integer | – | Status id — see insightly_list_lead_statuses. |
| mobile | string | – | – |
| organisation_name | string | – | Company name (free text — leads are not linked to organisations). |
| owner_user_id | integer | – | – |
| phone | string | – | – |
| responsible_user_id | integer | – | – |
| salutation | string | – | – |
| title | string | – | Job title. |
| website | string | – | – |
No output schema declared.
No examples provided.
insightly_create_opportunity Create an opportunity ~230
Create a sales opportunity (opportunity_name is required). Insightly: POST /Opportunities.
| Name | Type | Req | Description |
|---|---|---|---|
| bid_amount | number | – | Bid value. |
| bid_currency | string | – | ISO currency code, e.g. USD. |
| bid_duration | integer | – | Number of bid periods (for non-fixed bid types). |
| bid_type | string | – | BID_TYPE — how the bid is priced, using a value your Insightly instance accepts. |
| category_id | integer | – | Opportunity category id. |
| custom_fields | array | – | Custom field values to set. |
| forecast_close_date | string | – | Forecast close date, as "yyyy-MM-dd HH:mm:ss" in UTC (e.g. 2026-04-10 21:15:00). |
| opportunity_details | string | – | Description. |
| opportunity_name | string | yes | Opportunity name (required). |
| organisation_id | integer | – | Id of the linked organisation. |
| owner_user_id | integer | – | – |
| probability | integer | – | Win probability, 0-100. |
| responsible_user_id | integer | – | – |
No output schema declared.
No examples provided.
insightly_create_organisation Create an organisation ~152
Create an organisation (company). Insightly: POST /Organisations.
| Name | Type | Req | Description |
|---|---|---|---|
| address_billing_city | string | – | – |
| address_billing_country | string | – | – |
| address_billing_postcode | string | – | – |
| address_billing_state | string | – | – |
| address_billing_street | string | – | – |
| background | string | – | Background / description text. |
| custom_fields | array | – | Custom field values to set. |
| organisation_name | string | yes | Organisation name (required). |
| owner_user_id | integer | – | Owning user's id. |
| phone | string | – | – |
| social_linkedin | string | – | LinkedIn URL. |
| website | string | – | – |
No output schema declared.
No examples provided.
insightly_create_task Create a task ~301
Create a task (title is required). Insightly requires OWNER_USER_ID and COMPLETED on a task: if owner_user_id is omitted it is filled with the API key's own user (via GET /Users/Me), and completed defaults to false. Insightly: POST /Tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | integer | – | Task category id. |
| completed | boolean | – | Whether the task is done. |
| custom_fields | array | – | Custom field values to set. |
| details | string | – | Task description. |
| due_date | string | – | Due date, as "yyyy-MM-dd HH:mm:ss" in UTC (e.g. 2026-04-10 21:15:00). |
| opportunity_id | integer | – | Link the task to this opportunity. |
| owner_user_id | integer | – | Owner's user id. |
| percent_complete | integer | – | – |
| priority | integer | – | Priority number. |
| project_id | integer | – | Link the task to this project. |
| responsible_user_id | integer | – | Assignee's user id. |
| start_date | string | – | Start date, as "yyyy-MM-dd HH:mm:ss" in UTC (e.g. 2026-04-10 21:15:00). |
| status | string | – | Task STATUS text, using a value your Insightly instance accepts (read an existing task to see them). |
| title | string | yes | Task title (required). |
No output schema declared.
No examples provided.
insightly_get_current_user Get the current user ~61
Fetch the user the API key belongs to (USER_ID, name, email, admin flag). A cheap way to confirm the key and pod are right, and to get your own id for owner fields. Insightly: GET /Users/Me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
insightly_get_record Get one record ~72
Fetch a single Contact, Organisation, Lead, Opportunity, Project, Task, Event or Note by id, with its custom fields, tags and links. Insightly: GET /<Object>/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The record's numeric id. |
| object | string | yes | Record type. |
No output schema declared.
No examples provided.
insightly_list_lead_sources List lead sources ~70
List the lead sources defined in the instance (LEAD_SOURCE_ID, name). Insightly: GET /LeadSources.
| Name | Type | Req | Description |
|---|---|---|---|
| skip | integer | – | Records to skip, for paging. |
| top | integer | – | Max records to return, 1-500 (API default 100). |
No output schema declared.
No examples provided.
insightly_list_lead_statuses List lead statuses ~89
List the lead statuses defined in the instance (LEAD_STATUS_ID, name, type). Insightly: GET /LeadStatuses.
| Name | Type | Req | Description |
|---|---|---|---|
| include_converted | boolean | – | Also include statuses used for converted leads. |
| skip | integer | – | Records to skip, for paging. |
| top | integer | – | Max records to return, 1-500 (API default 100). |
No output schema declared.
No examples provided.
insightly_list_pipeline_stages List pipeline stages ~86
List every pipeline stage (STAGE_ID, PIPELINE_ID, name, order) — map an opportunity's or project's STAGE_ID to a stage name. Insightly: GET /PipelineStages.
| Name | Type | Req | Description |
|---|---|---|---|
| skip | integer | – | Records to skip, for paging. |
| top | integer | – | Max records to return, 1-500 (API default 100). |
No output schema declared.
No examples provided.
insightly_list_pipelines List pipelines ~72
List the sales and project pipelines (PIPELINE_ID, name, whether for opportunities or projects). Insightly: GET /Pipelines.
| Name | Type | Req | Description |
|---|---|---|---|
| skip | integer | – | Records to skip, for paging. |
| top | integer | – | Max records to return, 1-500 (API default 100). |
No output schema declared.
No examples provided.
insightly_list_record_activity List a record's notes, tasks or events ~205
List the Notes, Tasks or Events attached to one Contact, Organisation, Lead, Opportunity or Project — the activity history of that record. Insightly: GET /<Object>/{id}/Notes | Tasks | Events.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | boolean | – | true = only top-level fields (no CUSTOMFIELDS, TAGS, LINKS, ...). Smaller and faster. |
| count_total | boolean | – | true = also return the total number of matching records (response becomes {total_count, items}). |
| id | integer | yes | The parent record's numeric id. |
| kind | string | yes | Which activity to list. |
| object | string | yes | The parent record's type. |
| skip | integer | – | Records to skip, for paging. |
| top | integer | – | Max records to return, 1-500 (API default 100). |
| updated_after_utc | string | – | Only items updated after this time, yyyy-mm-ddThh:mm:ssZ. |
No output schema declared.
No examples provided.
insightly_list_records List or search records ~295
List records of one type — Contacts, Organisations, Leads, Opportunities, Projects, Tasks, Events or Notes — optionally filtered by one field value and/or last-updated time. With field_name + field_value (both required together) or updated_after_utc this uses GET /<Object>/Search; otherwise GET /<Object>. Field names are Insightly's UPPER_SNAKE names, e.g. EMAIL_ADDRESS, LAST_NAME, ORGANISATION_NAME, OPPORTUNITY_STATE, LEAD_RATING, or a custom field such as Industry__c.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | boolean | – | true = only top-level fields (no CUSTOMFIELDS, TAGS, LINKS, ...). Smaller and faster. |
| count_total | boolean | – | true = also return the total number of matching records (response becomes {total_count, items}). |
| field_name | string | – | Field to filter on, e.g. EMAIL_ADDRESS. |
| field_value | string | – | Value the field must equal. |
| object | string | yes | Record type. |
| skip | integer | – | Records to skip, for paging. |
| top | integer | – | Max records to return, 1-500 (API default 100). |
| updated_after_utc | string | – | Only records updated after this time, yyyy-mm-ddThh:mm:ssZ (e.g. 2026-04-09T16:58:14Z). |
No output schema declared.
No examples provided.
insightly_list_users List users ~99
List the users in the Insightly instance — needed to resolve OWNER_USER_ID / RESPONSIBLE_USER_ID. Insightly: GET /Users.
| Name | Type | Req | Description |
|---|---|---|---|
| count_total | boolean | – | true = also return the total number of matching records (response becomes {total_count, items}). |
| skip | integer | – | Records to skip, for paging. |
| top | integer | – | Max records to return, 1-500 (API default 100). |
No output schema declared.
No examples provided.
insightly_search_by_tag Find records by tag ~149
List Contacts, Organisations, Leads, Opportunities or Projects carrying a tag. Insightly: GET /<Object>/SearchByTag?tagName=.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | boolean | – | true = only top-level fields (no CUSTOMFIELDS, TAGS, LINKS, ...). Smaller and faster. |
| count_total | boolean | – | true = also return the total number of matching records (response becomes {total_count, items}). |
| object | string | yes | Record type. |
| skip | integer | – | Records to skip, for paging. |
| tag | string | yes | The tag name. |
| top | integer | – | Max records to return, 1-500 (API default 100). |
No output schema declared.
No examples provided.
insightly_update_contact Update a contact ~251
Update a contact. Only the fields you pass are changed (v3.1 partial update). Insightly: PUT /Contacts with CONTACT_ID.
| Name | Type | Req | Description |
|---|---|---|---|
| address_mail_city | string | – | – |
| address_mail_country | string | – | – |
| address_mail_postcode | string | – | – |
| address_mail_state | string | – | – |
| address_mail_street | string | – | – |
| background | string | – | Background / description text. |
| contact_id | integer | yes | The contact's numeric id. |
| custom_fields | array | – | Custom field values to set. |
| email_address | string | – | Primary email. |
| email_opted_out | boolean | – | Opted out of email. |
| first_name | string | – | First name. |
| last_name | string | – | Last name. |
| organisation_id | integer | – | Id of the contact's organisation. |
| owner_user_id | integer | – | Owning user's id. |
| phone | string | – | Business phone. |
| phone_mobile | string | – | Mobile phone. |
| salutation | string | – | e.g. Mr, Ms, Dr. |
| social_linkedin | string | – | LinkedIn URL. |
| title | string | – | Job title. |
No output schema declared.
No examples provided.
insightly_update_lead Update a lead ~301
Update a lead. Only the fields you pass are changed. Insightly: PUT /Leads with LEAD_ID.
| Name | Type | Req | Description |
|---|---|---|---|
| address_city | string | – | – |
| address_country | string | – | – |
| address_postcode | string | – | – |
| address_state | string | – | – |
| address_street | string | – | – |
| custom_fields | array | – | Custom field values to set. |
| string | – | Email address. | |
| email_opted_out | boolean | – | – |
| employee_count | integer | – | – |
| first_name | string | – | – |
| industry | string | – | – |
| last_name | string | – | Last name. |
| lead_description | string | – | Description / notes on the lead. |
| lead_id | integer | yes | The lead's numeric id. |
| lead_rating | integer | – | Rating, e.g. 1-5. |
| lead_source_id | integer | – | Source id — see insightly_list_lead_sources. |
| lead_status_id | integer | – | Status id — see insightly_list_lead_statuses. |
| mobile | string | – | – |
| organisation_name | string | – | Company name (free text — leads are not linked to organisations). |
| owner_user_id | integer | – | – |
| phone | string | – | – |
| responsible_user_id | integer | – | – |
| salutation | string | – | – |
| title | string | – | Job title. |
| website | string | – | – |
No output schema declared.
No examples provided.
insightly_update_opportunity Update an opportunity ~257
Update an opportunity's value, probability, dates, owner or details. Only the fields you pass are changed. Insightly: PUT /Opportunities with OPPORTUNITY_ID.
| Name | Type | Req | Description |
|---|---|---|---|
| bid_amount | number | – | Bid value. |
| bid_currency | string | – | ISO currency code, e.g. USD. |
| bid_duration | integer | – | Number of bid periods (for non-fixed bid types). |
| bid_type | string | – | BID_TYPE — how the bid is priced, using a value your Insightly instance accepts. |
| category_id | integer | – | Opportunity category id. |
| custom_fields | array | – | Custom field values to set. |
| forecast_close_date | string | – | Forecast close date, as "yyyy-MM-dd HH:mm:ss" in UTC (e.g. 2026-04-10 21:15:00). |
| opportunity_details | string | – | Description. |
| opportunity_id | integer | yes | The opportunity's numeric id. |
| opportunity_name | string | – | Opportunity name. |
| organisation_id | integer | – | Id of the linked organisation. |
| owner_user_id | integer | – | – |
| probability | integer | – | Win probability, 0-100. |
| responsible_user_id | integer | – | – |
No output schema declared.
No examples provided.
insightly_update_organisation Update an organisation ~174
Update an organisation. Only the fields you pass are changed. Insightly: PUT /Organisations with ORGANISATION_ID.
| Name | Type | Req | Description |
|---|---|---|---|
| address_billing_city | string | – | – |
| address_billing_country | string | – | – |
| address_billing_postcode | string | – | – |
| address_billing_state | string | – | – |
| address_billing_street | string | – | – |
| background | string | – | Background / description text. |
| custom_fields | array | – | Custom field values to set. |
| organisation_id | integer | yes | The organisation's numeric id. |
| organisation_name | string | – | Organisation name. |
| owner_user_id | integer | – | Owning user's id. |
| phone | string | – | – |
| social_linkedin | string | – | LinkedIn URL. |
| website | string | – | – |
No output schema declared.
No examples provided.
insightly_update_task Update a task ~291
Update a task — mark it completed, change due date, status, assignee or details. Only the fields you pass are changed. Insightly: PUT /Tasks with TASK_ID.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | integer | – | Task category id. |
| completed | boolean | – | Whether the task is done. |
| custom_fields | array | – | Custom field values to set. |
| details | string | – | Task description. |
| due_date | string | – | Due date, as "yyyy-MM-dd HH:mm:ss" in UTC (e.g. 2026-04-10 21:15:00). |
| opportunity_id | integer | – | Link the task to this opportunity. |
| owner_user_id | integer | – | Owner's user id. |
| percent_complete | integer | – | – |
| priority | integer | – | Priority number. |
| project_id | integer | – | Link the task to this project. |
| responsible_user_id | integer | – | Assignee's user id. |
| start_date | string | – | Start date, as "yyyy-MM-dd HH:mm:ss" in UTC (e.g. 2026-04-10 21:15:00). |
| status | string | – | Task STATUS text, using a value your Insightly instance accepts (read an existing task to see them). |
| task_id | integer | yes | The task's numeric id. |
| title | string | – | Task title. |
No output schema declared.
No examples provided.
What is the io.usefulapi/insightly MCP server?
io.usefulapi/insightly is an MCP server listed in the public MCP registry as io.usefulapi/insightly. Read and write Insightly contacts, organisations, leads, opportunities, tasks and notes. This page covers its hosted endpoint (https://insightly.usefulapi.io/mcp).
Is the io.usefulapi/insightly MCP server safe to use?
io.usefulapi/insightly scores 75 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/insightly MCP server expose?
io.usefulapi/insightly exposes 21 tools: insightly_get_current_user, insightly_list_users, insightly_list_records, insightly_get_record, insightly_list_record_activity, and 16 more. Their descriptions and schemas cost roughly 3,794 tokens of context every time the server is loaded.
Does the io.usefulapi/insightly MCP server require authentication?
Yes. io.usefulapi/insightly 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/insightly MCP server still maintained?
io.usefulapi/insightly is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.