CRM and sales
helpcrunch
helpcrunch was answering at the last check. Checked on 2026-10-05 (daily check).
Manage HelpCrunch chats, customers, agents and knowledge-base articles.
Agents use servers like this to look up contacts and update leads and deals.
9 read-only0 change data3 high risk
https://helpcrunch.usefulapi.io/mcp
Follow (RSS): status changes, tool-list changes, new advisories and owner verification, in any feed reader.
Tools
12 tools: 9 read-only, 0 change data, 3 high risk (delete, pay, send or run code).
1 tool can send messages; they are listed first.
- 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 2,211 tokens of tool definitions and a 409 ms handshake.
- high risk
helpcrunch_create_messagesends messagesPOSTS a message into a LIVE chat - a customer-visible reply (type "message") or an internal private note (type "private"). Set `agent` (agent id) for agent messages; omit it for customer messages. HelpCrunch REST: POST /messages. - high risk
helpcrunch_update_chat_statusCHANGES the status of a LIVE chat (e.g. mark it opened, pending, on hold, or closed). HelpCrunch REST: PUT /chats/status. - high risk
helpcrunch_assign_chatASSIGNS (or unassigns) a LIVE chat to an agent. Pass `assignee` (agent id) to assign; omit it (or pass null) to unassign. HelpCrunch REST: PUT /chats/assignee. - read-only
helpcrunch_list_customersList / search customers (people who chatted in). Optionally filter with a single field/operator/value clause (comparison AND), sort (e.g. customers.firstSeen, customers.lastSeen) with order, and paginate with limit/offset. HelpCrunch REST: POST /customers/search. - read-only
helpcrunch_get_customerGet a single customer by id. HelpCrunch REST: GET /customers/{id}. - read-only
helpcrunch_list_chatsList / search chats (conversations). Optionally filter with a single field/operator/value clause (comparison AND), sort (e.g. chats.createdAt) with order, and paginate with limit/offset. HelpCrunch REST: POST /chats/search. - read-only
helpcrunch_get_chatGet a single chat (conversation) by id. HelpCrunch REST: GET /chats/{id}. - read-only
helpcrunch_get_chat_messagesGet the messages of a chat (conversation), newest first (sorted by createdAt DESC). Paginate with limit (max 100) / offset. HelpCrunch REST: GET /chats/{id}/messages. - read-only
helpcrunch_list_agentsList agents (support staff / operators) in the account, with role and email. Paginate with limit/offset. HelpCrunch REST: GET /agents. - read-only
helpcrunch_list_departmentsList departments (groups of agents that chats can be routed to), each with its agents. Paginate with limit/offset. HelpCrunch REST: GET /departments. - read-only
helpcrunch_list_applicationsList applications configured in the account - web chat widgets, iOS/Android apps, and social integrations (id, name, displayName, active, type). HelpCrunch REST: GET /applications. - read-only
helpcrunch_get_organizationGet the organization's live-chat availability status - domain, whether the team is online (teamOnline), and whether chat is enabled (chatEnabled). HelpCrunch REST: GET /organization.
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-05, 409 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-062026-10-05
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-05.
Badge
Live: status, days reachable, the tokens its tool list costs an agent. For a README:
[](https://7it.co.il/7maps/s/helpcrunch.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=helpcrunch.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/helpcrunch.usefulapi.io/mcp.js" async></script>
Or an iframe:
<iframe src="https://7it.co.il/7maps/widget/helpcrunch.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=helpcrunch.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.