CRM and sales
insightly
insightly was answering at the last check. Checked on 2026-10-04 (daily check).
Read and write Insightly contacts, organisations, leads, opportunities, tasks and notes.
Agents use servers like this to look up contacts and update leads and deals.
10 read-only0 change data11 high risk
https://insightly.usefulapi.io/mcp
Follow (RSS): status changes, tool-list changes, new advisories and owner verification, in any feed reader.
Tools
21 tools: 10 read-only, 0 change data, 11 high risk (delete, pay, send or run code).
No tool name points to sending messages.
- read-only
- Only reads or looks things up. Safe for an agent to call on its own.
- changes data
- Creates, edits or sends something. Worth a person's approval the first time.
- high risk
- Can delete, pay, send on your behalf or run code. Hard or impossible to undo.
Connecting costs an agent about 7,395 tokens of tool definitions and a 515 ms handshake.
- high risk
insightly_create_contactCreate a contact (first_name is required). Insightly: POST /Contacts. - high risk
insightly_update_contactUpdate a contact. Only the fields you pass are changed (v3.1 partial update). Insightly: PUT /Contacts with CONTACT_ID. - high risk
insightly_create_organisationCreate an organisation (company). Insightly: POST /Organisations. - high risk
insightly_update_organisationUpdate an organisation. Only the fields you pass are changed. Insightly: PUT /Organisations with ORGANISATION_ID. - high risk
insightly_create_leadCreate 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. - high risk
insightly_update_leadUpdate a lead. Only the fields you pass are changed. Insightly: PUT /Leads with LEAD_ID. - high risk
insightly_create_opportunityCreate a sales opportunity (opportunity_name is required). Insightly: POST /Opportunities. - high risk
insightly_update_opportunityUpdate an opportunity's value, probability, dates, owner or details. Only the fields you pass are changed. Insightly: PUT /Opportunities with OPPORTUNITY_ID. - high risk
insightly_create_taskCreate 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. - high risk
insightly_update_taskUpdate 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. - high risk
insightly_add_noteAdd a note (title + body) to a Contact, Organisation, Lead, Opportunity or Project. Insightly: POST /<Object>/{id}/Notes. - read-only
insightly_get_current_userFetch 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. - read-only
insightly_list_usersList the users in the Insightly instance - needed to resolve OWNER_USER_ID / RESPONSIBLE_USER_ID. Insightly: GET /Users. - read-only
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. With field_name + field_value (both required together) or updated_after_utc this uses GET /<Object>/Search; otherwise GET /... - read-only
insightly_get_recordFetch a single Contact, Organisation, Lead, Opportunity, Project, Task, Event or Note by id, with its custom fields, tags and links. Insightly: GET /<Object>/{id}. - read-only
insightly_list_record_activityList 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. - read-only
insightly_search_by_tagList Contacts, Organisations, Leads, Opportunities or Projects carrying a tag. Insightly: GET /<Object>/SearchByTag?tagName=. - read-only
insightly_list_pipelinesList the sales and project pipelines (PIPELINE_ID, name, whether for opportunities or projects). Insightly: GET /Pipelines. - read-only
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. Insightly: GET /PipelineStages. - read-only
insightly_list_lead_statusesList the lead statuses defined in the instance (LEAD_STATUS_ID, name, type). Insightly: GET /LeadStatuses. - read-only
insightly_list_lead_sourcesList the lead sources defined in the instance (LEAD_SOURCE_ID, name). Insightly: GET /LeadSources.
Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.
Status
Newest check: answered with tools, from the daily check, 2026-10-04, 515 ms.
From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.
Last 30 days
2026-09-052026-10-04
answered with toolssign-in or payment askednot answeringnot checked
Compare: the most reliable servers in CRM and sales, ranked by days answering.
Trust and supply chain
No owner has verified this server yet.
No tool change since tracking began on 2026-10-04.
Badge
Live: status, days reachable, the tokens its tool list costs an agent. For a README:
[](https://7it.co.il/7maps/s/insightly.usefulapi.io/mcp)
Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).
Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=insightly.usefulapi.io%2Fmcp (add the same &style= for another style).
Own this server? Verify that it is yours.
Status widget
A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.
Script (renders where it is placed, in its own shadow DOM):
<script src="https://7it.co.il/7maps/widget/insightly.usefulapi.io/mcp.js" async></script>
Or an iframe:
<iframe src="https://7it.co.il/7maps/widget/insightly.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>
The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=insightly.usefulapi.io%2Fmcp.
Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.
For AI agents
Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.
7Maps by 7IT maps the MCP servers AI agents use, from public listings. Observations with a date, not a judgement. Methodology · How we collect, and opting out.