# Helpwise MCP by usefulapi (remote · helpwise.usefulapi.io)

Read Helpwise conversations, contacts, tags and reports; note, tag, assign, close; send one email.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `helpwise.usefulapi.io`: 65/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-helpwise/helpwise.md), [page](https://verifymcp.io/servers/io-usefulapi-helpwise/helpwise)

## Channel facts

- Endpoint: `https://helpwise.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-helpwise 'https://helpwise.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-helpwise": {
      "url": "https://helpwise.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-helpwise": {
      "type": "http",
      "url": "https://helpwise.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-helpwise]
url = "https://helpwise.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-helpwise": {
      "type": "remote",
      "url": "https://helpwise.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-helpwise --url 'https://helpwise.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-helpwise:
    url: "https://helpwise.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-helpwise": {
      "Transport": "http",
      "Url": "https://helpwise.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-helpwise -t streamable-http -u 'https://helpwise.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-helpwise": {
      "type": "http",
      "url": "https://helpwise.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 65, +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.

### 2026-10-14 (score 64, +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.

### 2026-10-13 (score 63, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] 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

### 2026-10-12 (score 61)

First indexed and scored.

## MCP tools (21)

### `helpwise_list_conversations` (~166 tokens)

List conversations

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.

Input parameters:

- `folder` (string): Folder: all, assigned, unassigned, starred, snoozed, draft, sent, closed, spam, trash, scheduled.
- `inbox_ids` (array, required): 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.

### `helpwise_get_conversation` (~132 tokens)

Get conversation

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}.

Input parameters:

- `conversation_id` (integer, required): Conversation (thread) id.
- `folder` (string): Folder context (optional).
- `inbox_id` (integer, required): 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.

### `helpwise_list_contacts` (~79 tokens)

List contacts

List contacts (name, company, job title, emails, phones, id). Page with limit and offset. GET /contacts.

Input parameters:

- `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.

### `helpwise_search_contacts` (~90 tokens)

Search contacts

Search contacts by a name, email or phone term. Page with limit and offset. GET /contacts/search.

Input parameters:

- `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, required): Search term (name, email or phone).

### `helpwise_get_contact` (~43 tokens)

Get contact

One contact with emails, phones, company, custom fields and recent conversations. GET /contacts/{id}.

Input parameters:

- `contact_id` (integer, required): Helpwise contact id.

### `helpwise_list_tags` (~36 tokens)

List tags

All tags (id, name, colour, parent, inbox). Use the ids with helpwise_apply_tags. GET /tags.

### `helpwise_get_tag` (~33 tokens)

Get tag

One tag by id. GET /tags/{id}.

Input parameters:

- `tag_id` (integer, required): Helpwise tag id.

### `helpwise_get_report` (~178 tokens)

Overall report

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.

Input parameters:

- `business_hours_only` (boolean): Count business hours only (default false).
- `end` (string, required): 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, required): 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.

### `helpwise_get_tags_report` (~156 tokens)

Tags report

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.

Input parameters:

- `business_hours_only` (boolean): Count business hours only (default false).
- `end` (string, required): End, yyyy-mm-dd or yyyy-mm-dd hh:mm:ss (a date alone means 23:59:59).
- `inbox_id` (integer, required): Inbox (mailbox) id.
- `start` (string, required): 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.

### `helpwise_list_inboxes` (~83 tokens)

List inboxes

List the account's inboxes (mailboxes) with id, name, address and type. Use the ids in the other tools. POST /mailboxes/list (V0).

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1).

### `helpwise_list_users` (~61 tokens)

List users

List the team members (agents) with access to an inbox: id, name, email. Use the ids with helpwise_assign_conversation. POST /users/list (V0).

Input parameters:

- `inbox_id` (integer, required): Inbox (mailbox) id.

### `helpwise_get_current_user` (~35 tokens)

Get current user

The Helpwise user the API key belongs to (name, email, id). POST /users/me (V0).

### `helpwise_create_contact` (~130 tokens)

Create contact

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.

Input parameters:

- `company` (string): Company name.
- `custom_fields` (array): Custom field values.
- `emails` (array): Email addresses (1-10).
- `firstname` (string, required): First name.
- `job_title` (string): Job title.
- `lastname` (string): Last name.
- `phones` (array): Phone numbers (up to 10).

### `helpwise_update_contact` (~194 tokens)

Update contact

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}.

Input parameters:

- `company` (string): New company.
- `contact_id` (integer, required): 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).

### `helpwise_add_note` (~92 tokens)

Add note

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).

Input parameters:

- `conversation_id` (integer, required): Conversation (thread) id.
- `inbox_id` (integer, required): Inbox (mailbox) id of the conversation.
- `message` (string, required): The note text.

### `helpwise_assign_conversation` (~109 tokens)

Assign conversation

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).

Input parameters:

- `assigned_to` (integer, required): User id to assign to, or 0 to unassign.
- `conversation_id` (integer, required): Conversation (thread) id.
- `inbox_id` (integer, required): Inbox (mailbox) id of the conversation.

### `helpwise_close_conversations` (~69 tokens)

Close conversations

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.

Input parameters:

- `conversation_ids` (array, required): Conversation (thread) ids to close (1-25).

### `helpwise_reopen_conversations` (~65 tokens)

Reopen conversations

WRITE: move up to 25 conversations back to the inbox (reopen closed ones). Nothing is sent to customers. PUT /conversations/action/moveToInbox.

Input parameters:

- `conversation_ids` (array, required): Conversation (thread) ids to reopen (1-25).

### `helpwise_apply_tags` (~85 tokens)

Apply tags

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.

Input parameters:

- `conversation_ids` (array, required): Conversation (thread) ids (1-25).
- `tag_ids` (array, required): Tag ids to apply (1-10).

### `helpwise_remove_tags` (~68 tokens)

Remove tags from conversations

WRITE: take tags off up to 25 conversations. The tags themselves are not deleted. POST /tags/remove.

Input parameters:

- `conversation_ids` (array, required): Conversation (thread) ids (1-25).
- `tag_ids` (array, required): Tag ids to remove from them (1-10).

### `helpwise_send_email` (~190 tokens)

Send email

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).

Input parameters:

- `body` (string, required): Plain-text message body.
- `cc` (array): Cc addresses.
- `inbox_id` (integer, required): Inbox (mailbox) id to send from (see helpwise_list_inboxes).
- `reply_to` (string): Reply-to address (optional).
- `subject` (string, required): Subject line.
- `to` (array, required): Recipient addresses (1-10 with cc together).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-helpwise/helpwise#diagnostics

## Score history

- 2026-10-17: 65
- 2026-10-16: 65
- 2026-10-15: 64
- 2026-10-14: 64
- 2026-10-13: 63
- 2026-10-12: 61

## Common questions

### 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 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://helpwise.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/helpwise/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-helpwise/helpwise.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-helpwise/helpwise.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-helpwise/helpwise