Home / MCP registry index / io.usefulapi/insightly

Insightly MCP by usefulapi

io.usefulapi/insightly in the official MCP registry. Endpoint https://insightly.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read and write Insightly contacts, organisations, leads, opportunities, tasks and notes.

We read its 21 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

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

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "insightly": {
      "url": "https://insightly.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"insightly","type":"http","url":"https://insightly.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

insightly_get_current_user insightly_list_users insightly_list_records insightly_get_record insightly_list_record_activity insightly_search_by_tag insightly_list_pipelines insightly_list_pipeline_stages insightly_list_lead_statuses insightly_list_lead_sources insightly_create_contact insightly_update_contact insightly_create_organisation insightly_update_organisation insightly_create_lead insightly_update_lead insightly_create_opportunity insightly_update_opportunity insightly_create_task insightly_update_task insightly_add_note

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 45c01e15905d8227. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-insightly/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-insightly)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.