Skip to content

Insightly MCP by usefulapi

io.usefulapi/insightlyusefulapi.iostreamable-httpv1.40.4Scanned

Read and write Insightly contacts, organisations, leads, opportunities, tasks and notes.

21 tools: 11 can delete or cancel things and 10 only read.

Tools: 11 delete, 0 irreversible, 0 write, 10 read.
  • Reads private data · 5
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

11 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Insightly MCP by usefulapi can do

The Insightly MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 21 tools. It can delete or cancel things (11 tools: insightly_create_contact, insightly_update_contact, insightly_create_organisation, insightly_update_organisation and 7 more). 10 tools only read.

5 tools read private data (insightly_get_current_user, insightly_list_records, insightly_get_record and 2 more); 1 tool brings in text other people can write (insightly_get_current_user).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

21 tools

Deletes or cancels 11Claude Code: deny
  • insightly_add_noteAdd a note (title + body) to a Contact, Organisation, Lead, Opportunity or Project.No findings

    Why it is in this group

    • The name "insightly_add_note" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Add a note (title + body) to a Contact, Organisation, Lead, Opportunity or Project. Insightly: POST /<Object>/{id}/Notes.

    Annotations the server declares

    • title: Add a note to a record
    • destructiveHint: true
  • insightly_create_contactCreate a contact (first_name is required).No findings

    Why it is in this group

    • The name "insightly_create_contact" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create a contact (first_name is required). Insightly: POST /Contacts.

    Annotations the server declares

    • title: Create a contact
    • destructiveHint: true
  • insightly_create_leadCreate a lead (last_name is required).No findings

    Why it is in this group

    • The name "insightly_create_lead" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a lead
    • destructiveHint: true
  • insightly_create_opportunityCreate a sales opportunity (opportunity_name is required).No findings

    Why it is in this group

    • The name "insightly_create_opportunity" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create a sales opportunity (opportunity_name is required). Insightly: POST /Opportunities.

    Annotations the server declares

    • title: Create an opportunity
    • destructiveHint: true
  • insightly_create_organisationCreate an organisation (company).No findings

    Why it is in this group

    • The name "insightly_create_organisation" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create an organisation (company). Insightly: POST /Organisations.

    Annotations the server declares

    • title: Create an organisation
    • destructiveHint: true
  • insightly_create_taskCreate a task (title is required).No findings

    Why it is in this group

    • The name "insightly_create_task" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a task
    • destructiveHint: true
  • insightly_update_contactUpdate a contact.No findings

    Why it is in this group

    • The name "insightly_update_contact" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Update a contact. Only the fields you pass are changed (v3.1 partial update). Insightly: PUT /Contacts with CONTACT_ID.

    Annotations the server declares

    • title: Update a contact
    • destructiveHint: true
  • insightly_update_leadUpdate a lead.No findings

    Why it is in this group

    • The name "insightly_update_lead" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Update a lead. Only the fields you pass are changed. Insightly: PUT /Leads with LEAD_ID.

    Annotations the server declares

    • title: Update a lead
    • destructiveHint: true
  • insightly_update_opportunityUpdate an opportunity's value, probability, dates, owner or details.No findings

    Why it is in this group

    • The name "insightly_update_opportunity" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Update an opportunity's value, probability, dates, owner or details. Only the fields you pass are changed. Insightly: PUT /Opportunities with OPPORTUNITY_ID.

    Annotations the server declares

    • title: Update an opportunity
    • destructiveHint: true
  • insightly_update_organisationUpdate an organisation.No findings

    Why it is in this group

    • The name "insightly_update_organisation" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Update an organisation. Only the fields you pass are changed. Insightly: PUT /Organisations with ORGANISATION_ID.

    Annotations the server declares

    • title: Update an organisation
    • destructiveHint: true
  • insightly_update_taskUpdate a task — mark it completed, change due date, status, assignee or details.No findings

    Why it is in this group

    • The name "insightly_update_task" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update a task
    • destructiveHint: true
Only reads 10Show 10 read-only tools
  • insightly_get_current_userFetch the user the API key belongs to (USER_ID, name, email, admin flag).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "insightly_get_current_user" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "fetch" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get the current user
    • readOnlyHint: true
  • insightly_get_recordFetch a single Contact, Organisation, Lead, Opportunity, Project, Task, Event or Note by id, with its custom fields, tags and links.Reads private dataNo findings

    Why it is in this group

    • The name "insightly_get_record" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get one record
    • readOnlyHint: true
  • insightly_list_lead_sourcesList the lead sources defined in the instance (LEAD_SOURCE_ID, name).No findings

    Why it is in this group

    • The name "insightly_list_lead_sources" says "list": a word for reading.
    Description, as the server wrote it
    List the lead sources defined in the instance (LEAD_SOURCE_ID, name). Insightly: GET /LeadSources.

    Annotations the server declares

    • title: List lead sources
    • readOnlyHint: true
  • insightly_list_lead_statusesList the lead statuses defined in the instance (LEAD_STATUS_ID, name, type).No findings

    Why it is in this group

    • The name "insightly_list_lead_statuses" says "list": a word for reading.
    Description, as the server wrote it
    List the lead statuses defined in the instance (LEAD_STATUS_ID, name, type). Insightly: GET /LeadStatuses.

    Annotations the server declares

    • title: List lead statuses
    • readOnlyHint: true
  • insightly_list_pipeline_stagesList every pipeline stage (STAGE_ID, PIPELINE_ID, name, order) — map an opportunity's or project's STAGE_ID to a stage name.No findings

    Why it is in this group

    • The name "insightly_list_pipeline_stages" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List pipeline stages
    • readOnlyHint: true
  • insightly_list_pipelinesList the sales and project pipelines (PIPELINE_ID, name, whether for opportunities or projects).No findings

    Why it is in this group

    • The name "insightly_list_pipelines" says "list": a word for reading.
    Description, as the server wrote it
    List the sales and project pipelines (PIPELINE_ID, name, whether for opportunities or projects). Insightly: GET /Pipelines.

    Annotations the server declares

    • title: List pipelines
    • readOnlyHint: true
  • insightly_list_record_activityList the Notes, Tasks or Events attached to one Contact, Organisation, Lead, Opportunity or Project — the activity history of that record.Reads private dataNo findings

    Why it is in this group

    • The name "insightly_list_record_activity" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "note": it reads notes.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List a record's notes, tasks or events
    • readOnlyHint: true
  • insightly_list_recordsList records of one type — Contacts, Organisations, Leads, Opportunities, Projects, Tasks, Events or Notes — optionally filtered by one field value and/or last-updated time.Reads private dataNo findings

    Why it is in this group

    • The name "insightly_list_records" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List or search records
    • readOnlyHint: true
  • insightly_list_usersList the users in the Insightly instance — needed to resolve OWNER_USER_ID / RESPONSIBLE_USER_ID.No findings

    Why it is in this group

    • The name "insightly_list_users" says "list": a word for reading.
    Description, as the server wrote it
    List the users in the Insightly instance — needed to resolve OWNER_USER_ID / RESPONSIBLE_USER_ID. Insightly: GET /Users.

    Annotations the server declares

    • title: List users
    • readOnlyHint: true
  • insightly_search_by_tagList Contacts, Organisations, Leads, Opportunities or Projects carrying a tag.Reads private dataNo findings

    Why it is in this group

    • The name "insightly_search_by_tag" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    List Contacts, Organisations, Leads, Opportunities or Projects carrying a tag. Insightly: GET /<Object>/SearchByTag?tagName=.

    Annotations the server declares

    • title: Find records by tag
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data5
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 11 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://insightly.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://insightly.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 11 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://insightly.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://insightly.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http insightly https://insightly.usefulapi.io/mcp
claude mcp add --transport http insightly https://insightly.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__insightly__insightly_get_current_user",
      "mcp__insightly__insightly_list_users",
      "mcp__insightly__insightly_list_records",
      "mcp__insightly__insightly_get_record",
      "mcp__insightly__insightly_list_record_activity",
      "mcp__insightly__insightly_search_by_tag",
      "mcp__insightly__insightly_list_pipelines",
      "mcp__insightly__insightly_list_pipeline_stages",
      "mcp__insightly__insightly_list_lead_statuses",
      "mcp__insightly__insightly_list_lead_sources"
    ],
    "ask": [],
    "deny": [
      "mcp__insightly__insightly_create_contact",
      "mcp__insightly__insightly_update_contact",
      "mcp__insightly__insightly_create_organisation",
      "mcp__insightly__insightly_update_organisation",
      "mcp__insightly__insightly_create_lead",
      "mcp__insightly__insightly_update_lead",
      "mcp__insightly__insightly_create_opportunity",
      "mcp__insightly__insightly_update_opportunity",
      "mcp__insightly__insightly_create_task",
      "mcp__insightly__insightly_update_task",
      "mcp__insightly__insightly_add_note"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as insightly. Review it before you use it.

Capability tags behind 5 rules
  • mcp__insightly__insightly_get_current_user private-data, untrusted-input
  • mcp__insightly__insightly_list_records private-data
  • mcp__insightly__insightly_get_record private-data
  • mcp__insightly__insightly_list_record_activity private-data
  • mcp__insightly__insightly_search_by_tag private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/insightly/verify?hash=202acf08e21475a23503cb46d2f99b2ac41febc640061e23534f8a8b2d1ec81f" | jq -e '.changed == false'

Pinned hash 202acf08e214, from Oct 25, 2026, 23:20 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/insightly/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/insightly
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/insightly.svg)](https://radar.anlyon.com/servers/io.usefulapi/insightly)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Insightly MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Insightly MCP by usefulapi safe?

No scan can promise that. What its definitions show: 21 tools, 11 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Insightly MCP by usefulapi delete data?

Yes. 11 tools can delete, cancel or revoke something: insightly_create_contact, insightly_update_contact, insightly_create_organisation, insightly_update_organisation, insightly_create_lead, insightly_update_lead and 5 more.

Can the Insightly MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Insightly MCP by usefulapi have?

21 tools: 11 destructive, 10 read. insightly_create_contact, insightly_update_contact, insightly_create_organisation, insightly_update_organisation, insightly_create_lead, insightly_update_lead, insightly_create_opportunity, insightly_update_opportunity and 13 more.

Does the Insightly MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Insightly MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Insightly MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.