# io.usefulapi/happyfox (remote · happyfox.usefulapi.io)

Triage HappyFox tickets, contacts and KB articles, run reports, and reply or add private notes.

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

## Components

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

## Channel facts

- Endpoint: `https://happyfox.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-04.

- **Endpoint Security**: 89/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 is enforced; there's no plaintext access path.
  - 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**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3094 tokens (~134/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 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.
  - We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 23 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 io.usefulapi/happyfox MCP server?

io.usefulapi/happyfox is a hosted endpoint at https://happyfox.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-happyfox 'https://happyfox.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-happyfox": {
      "type": "http",
      "url": "https://happyfox.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-04 (score 77, +44)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: behind authorisation → reachable
- [functional improvement] Stability: unverified → 0.07
- [functional improvement] Tool coverage: unverified → 100

### 2026-10-03 (score 33, −43)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Authorization: pass → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it.

### 2026-10-02 (score 76, +43)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-10-01 (score 33, +5)

- [security improvement] HTTPS: unverified → pass
- [security] Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities.
- [functional] Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.

### 2026-09-30 (score 28, +10)

- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- [security] Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- [functional] Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (23)

### `happyfox_list_tickets` (~327 tokens)

List or search tickets

List tickets, newest activity first, with optional filters and HappyFox's search syntax. Paginated (page_info + data). Search `q` examples: `status:"New","In Progress"`, `priority:"High"`, `assignee:none`, `tag:"billing"`, `contact:"jane@example.com"`, `unresponded:true`, `breached:true`, `duedate:overdue`, `created-after:"2026/01/31"`, `last-modified-on-or-after:"2026/09/01"`, `"Custom Field":"value"`. Separate several filters with a space. HappyFox: GET /api/1.1/json/tickets/.

Input parameters:

- `category` (integer): Only tickets in this category id (happyfox_list_categories).
- `fields` (string): Comma-separated top-level fields to return, e.g. id,display_id,subject,status — keeps responses small.
- `minify_response` (boolean): If true, return only ticket ids.
- `page` (integer): Page number, starting at 1.
- `q` (string): HappyFox search/filter string (see description).
- `size` (integer): Results per page, 1-50 (HappyFox default 10).
- `sort` (string): Sort key, e.g. created (newest first), createa, updated, due, priorityd.
- `status` (string): `_all` (default), `_pending` (every pending-behaviour status), or a status id from happyfox_list_statuses.

### `happyfox_get_ticket` (~129 tokens)

Get one ticket

Fetch a ticket with its full conversation: status, priority, category, contact, assignee, custom fields, SLA breaches and every update (messages, private notes, property changes, attachment links that expire in 5 minutes). HappyFox: GET /api/1.1/json/ticket/<ticket_number>/.

Input parameters:

- `show_cf_changes` (boolean): Include the history of custom-field changes in the updates.
- `ticket_number` (integer, required): The ticket NUMBER (the `id` field, e.g. 3 for #DC00000003) — not the prefixed display id.

### `happyfox_list_contacts` (~133 tokens)

List or search contacts

List contacts (customers), paginated, or search them. Search `q` fields: name, email, phone (digits only, no +), updated_since, created_since — e.g. `name:adam email:adam@example.com` (space-separated, all must match). HappyFox: GET /api/1.1/json/users/.

Input parameters:

- `page` (integer): Page number, starting at 1.
- `q` (string): Search string, `field:value` pairs separated by spaces.
- `size` (integer): Results per page, 1-50 (HappyFox default 10).

### `happyfox_get_contact` (~71 tokens)

Get one contact

Fetch a contact by id or by email address — phones, contact groups, ticket counts and custom fields. HappyFox: GET /api/1.1/json/user/<id or email>/.

Input parameters:

- `contact` (string, required): The contact's numeric id (e.g. "33") or email address.

### `happyfox_list_contact_groups` (~39 tokens)

List contact groups

List contact groups (typically customer companies) with their tagged email domains. HappyFox: GET /api/1.1/json/contact_groups/.

### `happyfox_get_contact_group` (~50 tokens)

Get one contact group

Fetch a contact group and its member contacts. HappyFox: GET /api/1.1/json/contact_group/<id>/.

Input parameters:

- `contact_group_id` (integer, required): The contact group id.

### `happyfox_list_categories` (~42 tokens)

List categories

List ticket categories (queues) with their ids — needed to create a ticket or filter tickets. HappyFox: GET /api/1.1/json/categories/.

### `happyfox_list_staff` (~56 tokens)

List agents

List agents (staff) with their ids, roles, categories and active flag — the `staff` id every reply/note needs, and assignee ids. HappyFox: GET /api/1.1/json/staff/.

### `happyfox_list_statuses` (~47 tokens)

List statuses

List ticket statuses with ids and behaviour (pending / completed) — ids used to change a ticket's status. HappyFox: GET /api/1.1/json/statuses/.

### `happyfox_list_priorities` (~41 tokens)

List priorities

List ticket priorities with ids — ids used to set a ticket's priority. HappyFox: GET /api/1.1/json/priorities/.

### `happyfox_list_ticket_custom_fields` (~59 tokens)

List ticket custom fields

List ticket custom fields: id, type, choices (with choice ids), required flags and categories. Use the ids as t-cf-<id>. HappyFox: GET /api/1.1/json/ticket_custom_fields/.

### `happyfox_list_contact_custom_fields` (~52 tokens)

List contact custom fields

List contact custom fields: id, type, choices and required flag. Use the ids as c-cf-<id>. HappyFox: GET /api/1.1/json/user_custom_fields/.

### `happyfox_list_reports` (~40 tokens)

List reports

List the saved reports (id, name, description) from the Reports module. HappyFox: GET /api/1.1/json/reports/.

### `happyfox_get_report_summary` (~64 tokens)

Get a report summary

Summary counts for a saved report: ticket, completed, assigned, pending and unassigned counts. HappyFox: GET /api/1.1/json/report/<id>/.

Input parameters:

- `report_id` (integer, required): The report (from happyfox_list_reports) id.

### `happyfox_get_report_tabular_data` (~116 tokens)

Get a report's ticket rows

The tabular view of a saved report — one row per ticket (display_id, subject, status, assignee, due date), paginated. HappyFox: GET /api/1.1/json/report/<id>/tabulardata/.

Input parameters:

- `page` (integer): Page number, starting at 1.
- `report_id` (integer, required): The report (from happyfox_list_reports) id.
- `size` (integer): Results per page, 1-50 (HappyFox default 10).

### `happyfox_list_kb_articles` (~75 tokens)

Export knowledge-base articles

Export the knowledge base: external (customer-facing) articles by default, or internal (agent-only) articles. HappyFox: GET /api/1.1/json/kb/articles/ or /kb/internal-articles/.

Input parameters:

- `internal` (boolean): true = internal articles; false/omitted = external articles.

### `happyfox_create_ticket` (~361 tokens)

Create a ticket

Open a new ticket on behalf of a contact (created if the email is new). Needs a category id (a public category), a subject and a message in `text` or `html`. HappyFox: POST /api/1.1/json/tickets/.

Input parameters:

- `assignee`: Agent id to assign the ticket to (from happyfox_list_staff); null to unassign.
- `bcc` (string): BCC email addresses, as a comma-separated string.
- `category` (integer, required): The category (happyfox_list_categories; must be public) id.
- `cc` (string): CC email addresses, as a comma-separated string.
- `custom_fields` (object): Custom field values keyed "t-cf-<id>" / "c-cf-<id>". Ticket (t-cf-) and contact (c-cf-) fields; required ones must be present. Values: text = string, number = number, dropdown = choice id, multiple c…
- `due_date` (string): Due date, yyyy-mm-dd or dd/mm/yyyy.
- `email` (string, required): Contact email address.
- `html` (string): Message in HTML (text or html is required).
- `name` (string, required): Contact name.
- `phone` (string): Contact phone number.
- `priority` (integer): Priority id (happyfox_list_priorities); defaults to the default priority.
- `subject` (string, required): Ticket subject.
- `tags` (string): Tags, as a comma-separated string.
- `text` (string): Message in plain text (text or html is required).
- `visible_only_staff` (boolean): true = private ticket, visible to staff only.

### `happyfox_add_staff_reply` (~440 tokens)

Reply to a ticket as an agent

Add an agent reply to a ticket and/or change its status, priority, assignee, due date or tags. The contact is emailed ONLY if update_customer is true (HappyFox default: false). With no message it just updates properties. Moving to a completed status may require the category's compulsory custom fields. HappyFox: POST /api/1.1/json/ticket/<ticket_number>/staff_update/.

Input parameters:

- `assignee`: Agent id to assign the ticket to (from happyfox_list_staff); null to unassign.
- `bcc` (string): BCC email addresses, as a comma-separated string.
- `cc` (string): CC email addresses, as a comma-separated string.
- `custom_fields` (object): Custom field values keyed "t-cf-<id>". Ticket fields (ids from happyfox_list_ticket_custom_fields); compulsory-on-completion fields are required when closing. Values: text = string, number = number,…
- `due_date` (string): Due date, yyyy-mm-dd or dd/mm/yyyy.
- `html` (string): Reply in HTML.
- `plaintext` (string): Reply in plain text.
- `priority` (integer): New priority id (happyfox_list_priorities).
- `send_survey` (boolean): true = send the satisfaction survey.
- `staff` (integer, required): The agent making the reply (happyfox_list_staff) id.
- `status` (integer): New status id (happyfox_list_statuses).
- `subject` (string): Override the subject of the email sent to the contact.
- `tags` (string): Tags to set, as a comma-separated string.
- `ticket_number` (integer, required): The ticket NUMBER (the `id` field, e.g. 3 for #DC00000003) — not the prefixed display id.
- `time_spent` (integer): Minutes to add to the ticket's time spent (some categories require it).
- `update_customer` (boolean): true = send the reply to the contact by email. Default false.

### `happyfox_add_private_note` (~358 tokens)

Add a private note to a ticket

Add an internal note (never sent to the contact), optionally alerting agents and changing status, priority, assignee, due date or tags. HappyFox: POST /api/1.1/json/ticket/<ticket_number>/staff_pvtnote/.

Input parameters:

- `alert` (string): Send a private alert: `s` = all subscribers, `c` = all agents in the ticket's category, or an agent id.
- `assignee`: Agent id to assign the ticket to (from happyfox_list_staff); null to unassign.
- `custom_fields` (object): Custom field values keyed "t-cf-<id>". Ticket fields (ids from happyfox_list_ticket_custom_fields); compulsory-on-completion fields are required when closing. Values: text = string, number = number,…
- `due_date` (string): Due date, yyyy-mm-dd or dd/mm/yyyy.
- `html` (string): Note in HTML.
- `plaintext` (string): Note in plain text.
- `priority` (integer): New priority id (happyfox_list_priorities).
- `staff` (integer, required): The agent adding the note (happyfox_list_staff) id.
- `status` (integer): New status id (happyfox_list_statuses).
- `tags` (string): Tags to set, as a comma-separated string.
- `ticket_number` (integer, required): The ticket NUMBER (the `id` field, e.g. 3 for #DC00000003) — not the prefixed display id.
- `time_spent` (integer): Minutes to add to the ticket's time spent (some categories require it).

### `happyfox_update_ticket_tags` (~134 tokens)

Add or remove ticket tags

Add and/or remove tags on a ticket without touching anything else. HappyFox: POST /api/1.1/json/ticket/<ticket_number>/update_tags/.

Input parameters:

- `add` (string): Tags to add, as a comma-separated string.
- `remove` (string): Tags to remove, as a comma-separated string.
- `staff_id` (integer, required): The agent making the change (shown in the ticket history) id.
- `ticket_number` (integer, required): The ticket NUMBER (the `id` field, e.g. 3 for #DC00000003) — not the prefixed display id.

### `happyfox_update_ticket_custom_fields` (~157 tokens)

Edit a ticket's custom fields

Set ticket custom-field values (t-cf-<id>, ids from happyfox_list_ticket_custom_fields). HappyFox: POST /api/1.1/json/ticket/<ticket_number>/update_custom_fields/.

Input parameters:

- `custom_fields` (object, required): Custom field values keyed "t-cf-<id>". Ticket fields only. Values: text = string, number = number, dropdown = choice id, multiple choice = array of choice ids, date = yyyy-mm-dd.
- `staff` (integer, required): The agent making the change id.
- `ticket_number` (integer, required): The ticket NUMBER (the `id` field, e.g. 3 for #DC00000003) — not the prefixed display id.

### `happyfox_create_contact` (~162 tokens)

Create a contact

Create a contact. HappyFox treats this as create-or-edit keyed on email: if the email already exists that contact is updated, and any contact custom field NOT passed is reset — use happyfox_update_contact to edit an existing contact. HappyFox: POST /api/1.1/json/users/.

Input parameters:

- `custom_fields` (object): Custom field values keyed "c-cf-<id>". Contact fields (happyfox_list_contact_custom_fields); required ones must be present. Values: text = string, number = number, dropdown = choice id, multiple choi…
- `email` (string, required): Contact email address.
- `name` (string, required): Contact name.
- `phones` (array): Phone numbers.

### `happyfox_update_contact` (~141 tokens)

Edit a contact

Edit an existing contact's name, email or contact custom fields (c-cf-<id>). Phone numbers are edited via happyfox_create_contact with the phone id. HappyFox: POST /api/1.1/json/user/<id>/.

Input parameters:

- `contact_id` (integer, required): The contact id.
- `custom_fields` (object): Custom field values keyed "c-cf-<id>". Contact fields. Values: text = string, number = number, dropdown = choice id, multiple choice = array of choice ids, date = yyyy-mm-dd.
- `email` (string): New email address.
- `name` (string): New name.

## Diagnostics

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

## Score history

- 2026-10-04: 77
- 2026-10-03: 33
- 2026-10-02: 76
- 2026-10-01: 33
- 2026-09-30: 28
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/happyfox MCP server?

io.usefulapi/happyfox is an MCP server listed in the public MCP registry as io.usefulapi/happyfox. Triage HappyFox tickets, contacts and KB articles, run reports, and reply or add private notes. This page covers its hosted endpoint (https://happyfox.usefulapi.io/mcp).

### Is the io.usefulapi/happyfox MCP server safe to use?

io.usefulapi/happyfox scores 77 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 io.usefulapi/happyfox MCP server expose?

io.usefulapi/happyfox exposes 23 tools: happyfox_list_tickets, happyfox_get_ticket, happyfox_list_contacts, happyfox_get_contact, happyfox_list_contact_groups, and 18 more. Their descriptions and schemas cost roughly 3,094 tokens of context every time the server is loaded.

### Does the io.usefulapi/happyfox MCP server require authentication?

Yes. io.usefulapi/happyfox 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 io.usefulapi/happyfox MCP server still maintained?

io.usefulapi/happyfox is still listed as active in the MCP registry. We last reached this channel on 4 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://happyfox.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-happyfox/happyfox.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-happyfox/happyfox.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-happyfox/happyfox