Helpwise MCP by usefulapi
REMOTE · HELPWISE.USEFULAPI.IO
Read Helpwise conversations, contacts, tags and reports; note, tag, assign, close; send one email.
Available components
Last scanned (23 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 16 Oct 2026.
Category CRM and Sales
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 Security78
- 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 enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2298 tokens (~109/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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 22 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
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.
- 16 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.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.0.0 → 1.1.0 functional
- 12 Oct 26 61
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 16 Oct 2026 · Probed https://helpwise.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 helpwise.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 | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://helpwise.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://helpwise.usefulapi.io/.well-known/oauth-protected-resource/mcp" Protected resource metadata
| Document | https://helpwise.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://helpwise.usefulapi.io/mcp |
| Authorisation server | https://helpwise.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://helpwise.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/helpwise/ |
| http (plaintext) | http://helpwise.usefulapi.io/mcp | Inconclusive | 302 | http://helpwise.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 →
helpwise_add_note Add note ~92
WRITE: add an internal note to a conversation. Visible to your Helpwise team only; it is not sent to the customer. Notes cannot be deleted through this API. POST /notes/add (V0).
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | integer | yes | Conversation (thread) id. |
| inbox_id | integer | yes | Inbox (mailbox) id of the conversation. |
| message | string | yes | The note text. |
No output schema declared.
No examples provided.
helpwise_apply_tags Apply tags ~85
WRITE: apply existing tags (ids from helpwise_list_tags) to up to 25 conversations. Tags can drive Helpwise automations. Applying a tag already present changes nothing. POST /tags/apply.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_ids | array | yes | Conversation (thread) ids (1-25). |
| tag_ids | array | yes | Tag ids to apply (1-10). |
No output schema declared.
No examples provided.
helpwise_assign_conversation Assign conversation ~109
WRITE: assign a conversation to a team member (user id from helpwise_list_users), or pass assigned_to 0 to unassign it. The assignee may be notified by Helpwise. POST /threads/assign (V0).
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to | integer | yes | User id to assign to, or 0 to unassign. |
| conversation_id | integer | yes | Conversation (thread) id. |
| inbox_id | integer | yes | Inbox (mailbox) id of the conversation. |
No output schema declared.
No examples provided.
helpwise_close_conversations Close conversations ~69
WRITE: close up to 25 conversations (mark them done). They can be reopened with helpwise_reopen_conversations. Nothing is sent to customers. PUT /conversations/action/close.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_ids | array | yes | Conversation (thread) ids to close (1-25). |
No output schema declared.
No examples provided.
helpwise_create_contact Create contact ~130
WRITE: create a new contact in Helpwise (name, company, job title, emails, phones, custom fields). Nothing is sent to the person. Creating the same email twice may create a duplicate. POST /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Company name. |
| custom_fields | array | – | Custom field values. |
| emails | array | – | Email addresses (1-10). |
| firstname | string | yes | First name. |
| job_title | string | – | Job title. |
| lastname | string | – | Last name. |
| phones | array | – | Phone numbers (up to 10). |
No output schema declared.
No examples provided.
helpwise_get_contact Get contact ~43
One contact with emails, phones, company, custom fields and recent conversations. GET /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | Helpwise contact id. |
No output schema declared.
No examples provided.
helpwise_get_conversation Get conversation ~132
One conversation with its messages, notes, drafts, assignment and contacts. Page long conversations with `page_token` from the previous reply. GET /inboxes/{inbox_id}/conversations/{conversation_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | integer | yes | Conversation (thread) id. |
| folder | string | – | Folder context (optional). |
| inbox_id | integer | yes | Inbox (mailbox) id the conversation lives in. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page_token | string | – | Page token from the previous reply, for older messages. |
No output schema declared.
No examples provided.
helpwise_get_current_user Get current user ~35
The Helpwise user the API key belongs to (name, email, id). POST /users/me (V0).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
helpwise_get_report Overall report ~178
Overall and team-performance report for a date range: new/closed/assigned conversations (with change vs the previous period), inbound/outbound messages per day, busiest hour/day, average first response, response and resolution time, CSAT and per-agent performance. Optional inbox and tag filters. GET /reports.
| Name | Type | Req | Description |
|---|---|---|---|
| business_hours_only | boolean | – | Count business hours only (default false). |
| end | string | yes | End, yyyy-mm-dd or yyyy-mm-dd hh:mm:ss (a date alone means 23:59:59). |
| inbox_id | integer | – | Only this inbox (default: all inboxes). |
| start | string | yes | Start, yyyy-mm-dd or yyyy-mm-dd hh:mm:ss (a date alone means 00:00:00). |
| tag_ids | array | – | Only conversations with these tag ids. |
No output schema declared.
No examples provided.
helpwise_get_tag Get tag ~33
One tag by id. GET /tags/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| tag_id | integer | yes | Helpwise tag id. |
No output schema declared.
No examples provided.
helpwise_get_tags_report Tags report ~156
Per-tag report for one inbox and a date range: conversations per tag (and share), open conversations, average response, first-response and resolution time. GET /inboxes/{inbox_id}/reports/tags.
| Name | Type | Req | Description |
|---|---|---|---|
| business_hours_only | boolean | – | Count business hours only (default false). |
| end | string | yes | End, yyyy-mm-dd or yyyy-mm-dd hh:mm:ss (a date alone means 23:59:59). |
| inbox_id | integer | yes | Inbox (mailbox) id. |
| start | string | yes | Start, yyyy-mm-dd or yyyy-mm-dd hh:mm:ss (a date alone means 00:00:00). |
| tag_ids | array | – | Only these tag ids. |
No output schema declared.
No examples provided.
helpwise_list_contacts List contacts ~79
List contacts (name, company, job title, emails, phones, id). Page with limit and offset. GET /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | How many results to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
helpwise_list_conversations List conversations ~166
List conversations (threads) of one or more inboxes, newest first, with subject, snippet, tags, assignee, read/starred/closed flags and contact. Pick the folder with `folder` (default: all). Page with `next_page_token`. Inbox ids come from helpwise_list_inboxes. GET /conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | Folder: all, assigned, unassigned, starred, snoozed, draft, sent, closed, spam, trash, scheduled. |
| inbox_ids | array | yes | Inbox (mailbox) ids to list (1-20). |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page_token | string | – | The previous reply's next_page_token. |
No output schema declared.
No examples provided.
helpwise_list_inboxes List inboxes ~83
List the account's inboxes (mailboxes) with id, name, address and type. Use the ids in the other tools. POST /mailboxes/list (V0).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). |
No output schema declared.
No examples provided.
helpwise_list_tags List tags ~36
All tags (id, name, colour, parent, inbox). Use the ids with helpwise_apply_tags. GET /tags.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
helpwise_list_users List users ~61
List the team members (agents) with access to an inbox: id, name, email. Use the ids with helpwise_assign_conversation. POST /users/list (V0).
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | integer | yes | Inbox (mailbox) id. |
No output schema declared.
No examples provided.
helpwise_remove_tags Remove tags from conversations ~68
WRITE: take tags off up to 25 conversations. The tags themselves are not deleted. POST /tags/remove.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_ids | array | yes | Conversation (thread) ids (1-25). |
| tag_ids | array | yes | Tag ids to remove from them (1-10). |
No output schema declared.
No examples provided.
helpwise_reopen_conversations Reopen conversations ~65
WRITE: move up to 25 conversations back to the inbox (reopen closed ones). Nothing is sent to customers. PUT /conversations/action/moveToInbox.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_ids | array | yes | Conversation (thread) ids to reopen (1-25). |
No output schema declared.
No examples provided.
helpwise_search_contacts Search contacts ~90
Search contacts by a name, email or phone term. Page with limit and offset. GET /contacts/search.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | How many results to skip (default 0). Pass the previous reply's next_offset. |
| term | string | yes | Search term (name, email or phone). |
No output schema declared.
No examples provided.
helpwise_send_email Send email ~190
WRITE: SEND A REAL EMAIL from a Helpwise inbox to the given customer address(es). Irreversible; once sent it cannot be recalled. At most 10 recipients in total (to + cc), one message per call; never use it for lists or campaigns. This starts a new message (it is not a reply on an existing conversation). The body is plain text (blank line = new paragraph); it is sent as HTML. POST /emails/send_mail (V0).
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Plain-text message body. |
| cc | array | – | Cc addresses. |
| inbox_id | integer | yes | Inbox (mailbox) id to send from (see helpwise_list_inboxes). |
| reply_to | string | – | Reply-to address (optional). |
| subject | string | yes | Subject line. |
| to | array | yes | Recipient addresses (1-10 with cc together). |
No output schema declared.
No examples provided.
helpwise_update_contact Update contact ~194
WRITE: change a contact's name, company, job title, emails, phones or custom fields. Helpwise updates with PUT, so this tool first reads the contact and sends the current values together with your changes; a list you pass (emails, phones, custom_fields) REPLACES the old list. Nothing is sent to the person. PUT /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | New company. |
| contact_id | integer | yes | Helpwise contact id. |
| custom_fields | array | – | Custom field values to set (replaces the current list). |
| emails | array | – | The full list of email addresses (replaces the current list). |
| firstname | string | – | New first name. |
| job_title | string | – | New job title. |
| lastname | string | – | New last name. |
| phones | array | – | The full list of phone numbers (replaces the current list). |
No output schema declared.
No examples provided.
How do I install the Helpwise MCP by usefulapi server?
Helpwise MCP by usefulapi is a hosted endpoint at https://helpwise.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 · helpwise.usefulapi.io
claude mcp add --transport http io-usefulapi-helpwise 'https://helpwise.usefulapi.io/mcp'
What is the Helpwise MCP by usefulapi server?
Helpwise MCP by usefulapi is listed in the public MCP registry as io.usefulapi/helpwise. Read Helpwise conversations, contacts, tags and reports; note, tag, assign, close; send one email. This page covers its hosted endpoint (https://helpwise.usefulapi.io/mcp).
Is the Helpwise MCP by usefulapi server safe to use?
Helpwise MCP by usefulapi scores 65 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 Helpwise MCP by usefulapi server expose?
Helpwise MCP by usefulapi exposes 21 tools: helpwise_list_conversations, helpwise_get_conversation, helpwise_list_contacts, helpwise_search_contacts, helpwise_get_contact, and 16 more. Their descriptions and schemas cost roughly 2,094 tokens of context every time the server is loaded.
Does the Helpwise MCP by usefulapi server require authentication?
Yes. Helpwise MCP by usefulapi 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 Helpwise MCP by usefulapi server still maintained?
Helpwise MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.