HappyFox MCP by usefulapi
io.usefulapi/happyfoxusefulapi.iostreamable-httpv1.40.4Scanned
Triage HappyFox tickets, contacts and KB articles, run reports, and reply or add private notes.
23 tools: 7 can delete or cancel things and 16 only read.
- Reads private data · 7
- Reads text others write · 11
- Can send data out · 1
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
7 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the HappyFox MCP by usefulapi can do
The HappyFox MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 23 tools. It can delete or cancel things (7 tools: happyfox_create_ticket, happyfox_add_staff_reply, happyfox_add_private_note, happyfox_update_ticket_tags and 3 more). 16 tools only read.
7 tools read private data (happyfox_get_ticket, happyfox_list_contacts, happyfox_get_contact and 4 more); 11 tools bring in text other people can write (happyfox_list_tickets, happyfox_get_ticket, happyfox_get_contact and 8 more); 1 tool can send data out of your system (happyfox_add_staff_reply). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
23 tools
Deletes or cancels 7Claude Code: deny
happyfox_add_private_noteAdd an internal note (never sent to the contact), optionally alerting agents and changing status, priority, assignee, due date or tags.No findings
Why it is in this group
- The name "happyfox_add_private_note" says "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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/.
Annotations the server declares
- title: Add a private note to a ticket
- destructiveHint: true
happyfox_add_staff_replyAdd an agent reply to a ticket and/or change its status, priority, assignee, due date or tags.Can send data outNo findings
Why it is in this group
- The name "happyfox_add_staff_reply" says "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "happyfox_add_staff_reply" says "add" and "reply": it writes something other people read.
Description, as the server wrote it 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/.
Annotations the server declares
- title: Reply to a ticket as an agent
- destructiveHint: true
happyfox_create_contactCreate a contact.No findings
Why it is in this group
- The name "happyfox_create_contact" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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/.
Annotations the server declares
- title: Create a contact
- destructiveHint: true
happyfox_create_ticketOpen a new ticket on behalf of a contact (created if the email is new).No findings
Why it is in this group
- The name "happyfox_create_ticket" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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/.
Annotations the server declares
- title: Create a ticket
- destructiveHint: true
happyfox_update_contactEdit an existing contact's name, email or contact custom fields (c-cf-<id>).No findings
Why it is in this group
- The name "happyfox_update_contact" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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>/.
Annotations the server declares
- title: Edit a contact
- destructiveHint: true
happyfox_update_ticket_custom_fieldsSet ticket custom-field values (t-cf-<id>, ids from happyfox_list_ticket_custom_fields).No findings
Why it is in this group
- The name "happyfox_update_ticket_custom_fields" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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/.
Annotations the server declares
- title: Edit a ticket's custom fields
- destructiveHint: true
happyfox_update_ticket_tagsAdd and/or remove tags on a ticket without touching anything else.No findings
Why it is in this group
- The name "happyfox_update_ticket_tags" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Add and/or remove tags on a ticket without touching anything else. HappyFox: POST /api/1.1/json/ticket/<ticket_number>/update_tags/.
Annotations the server declares
- title: Add or remove ticket tags
- destructiveHint: true
Only reads 16Show 16 read-only tools
happyfox_get_contactFetch a contact by id or by email address — phones, contact groups, ticket counts and custom fields.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "happyfox_get_contact" says "get": a word for reading.
What it can reach
- private-dataThe name "happyfox_get_contact" says "get" and "contact": it reads contacts.
- private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
- untrusted-inputThe description's first sentence says "fetch" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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>/.
Annotations the server declares
- title: Get one contact
- readOnlyHint: true
happyfox_get_contact_groupFetch a contact group and its member contacts.Reads private dataNo findings
Why it is in this group
- The name "happyfox_get_contact_group" says "get": a word for reading.
What it can reach
- private-dataThe name "happyfox_get_contact_group" says "get" and "contact": it reads contacts.
- private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
Description, as the server wrote it Fetch a contact group and its member contacts. HappyFox: GET /api/1.1/json/contact_group/<id>/.
Annotations the server declares
- title: Get one contact group
- readOnlyHint: true
happyfox_get_report_summarySummary counts for a saved report: ticket, completed, assigned, pending and unassigned counts.Reads text others writeNo findings
Why it is in this group
- The name "happyfox_get_report_summary" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
Description, as the server wrote it Summary counts for a saved report: ticket, completed, assigned, pending and unassigned counts. HappyFox: GET /api/1.1/json/report/<id>/.
Annotations the server declares
- title: Get a report summary
- readOnlyHint: true
happyfox_get_report_tabular_dataThe tabular view of a saved report — one row per ticket (display_id, subject, status, assignee, due date), paginated.Reads text others writeNo findings
Why it is in this group
- The name "happyfox_get_report_tabular_data" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
Description, as the server wrote it 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/.
Annotations the server declares
- title: Get a report's ticket rows
- readOnlyHint: true
happyfox_get_ticketFetch a ticket with its full conversation: status, priority, category, contact, assignee, custom fields, SLA breaches and every update (messages, private notes, property changes, a…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "happyfox_get_ticket" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "conversation": it reads messages.
- untrusted-inputThe name "happyfox_get_ticket" says "get" and "ticket": it reads issues, which other people can write.
- untrusted-inputThe description's first sentence says "fetch" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it 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>/.
Annotations the server declares
- title: Get one ticket
- readOnlyHint: true
happyfox_list_categoriesList ticket categories (queues) with their ids — needed to create a ticket or filter tickets.Reads text others writeNo findings
Why it is in this group
- The name "happyfox_list_categories" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it List ticket categories (queues) with their ids — needed to create a ticket or filter tickets. HappyFox: GET /api/1.1/json/categories/.
Annotations the server declares
- title: List categories
- readOnlyHint: true
happyfox_list_contact_custom_fieldsList contact custom fields: id, type, choices and required flag.Reads private dataNo findings
Why it is in this group
- The name "happyfox_list_contact_custom_fields" says "list": a word for reading.
What it can reach
- private-dataThe name "happyfox_list_contact_custom_fields" says "list" and "contact": it reads contacts.
- private-dataThe description's first sentence says "list" and "contact": it reads contacts.
Description, as the server wrote it 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/.
Annotations the server declares
- title: List contact custom fields
- readOnlyHint: true
happyfox_list_contact_groupsList contact groups (typically customer companies) with their tagged email domains.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "happyfox_list_contact_groups" says "list": a word for reading.
What it can reach
- private-dataThe name "happyfox_list_contact_groups" says "list" and "contact": it reads contacts.
- private-dataThe description's first sentence says "list" and "contact": it reads contacts.
- untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it List contact groups (typically customer companies) with their tagged email domains. HappyFox: GET /api/1.1/json/contact_groups/.
Annotations the server declares
- title: List contact groups
- readOnlyHint: true
happyfox_list_contactsList contacts (customers), paginated, or search them.Reads private dataNo findings
Why it is in this group
- The name "happyfox_list_contacts" says "list": a word for reading.
What it can reach
- private-dataThe name "happyfox_list_contacts" says "list" and "contact": it reads contacts.
- private-dataThe description's first sentence says "list" and "contact": it reads contacts.
Description, as the server wrote it 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/.
Annotations the server declares
- title: List or search contacts
- readOnlyHint: true
happyfox_list_kb_articlesExport the knowledge base: external (customer-facing) articles by default, or internal (agent-only) articles.No findings
Why it is in this group
- The name "happyfox_list_kb_articles" says "list": a word for reading.
Description, as the server wrote it 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/.
Annotations the server declares
- title: Export knowledge-base articles
- readOnlyHint: true
happyfox_list_prioritiesList ticket priorities with ids — ids used to set a ticket's priority.Reads text others writeNo findings
Why it is in this group
- The name "happyfox_list_priorities" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it List ticket priorities with ids — ids used to set a ticket's priority. HappyFox: GET /api/1.1/json/priorities/.
Annotations the server declares
- title: List priorities
- readOnlyHint: true
happyfox_list_reportsList the saved reports (id, name, description) from the Reports module.No findings
Why it is in this group
- The name "happyfox_list_reports" says "list": a word for reading.
Description, as the server wrote it List the saved reports (id, name, description) from the Reports module. HappyFox: GET /api/1.1/json/reports/.
Annotations the server declares
- title: List reports
- readOnlyHint: true
happyfox_list_staffList agents (staff) with their ids, roles, categories and active flag — the `staff` id every reply/note needs, and assignee ids.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "happyfox_list_staff" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "note": it reads notes.
- untrusted-inputThe description's first sentence says "list" and "reply": it reads comments, which other people can write.
Description, as the server wrote it 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/.
Annotations the server declares
- title: List agents
- readOnlyHint: true
happyfox_list_statusesList ticket statuses with ids and behaviour (pending / completed) — ids used to change a ticket's status.Reads text others writeNo findings
Why it is in this group
- The name "happyfox_list_statuses" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it List ticket statuses with ids and behaviour (pending / completed) — ids used to change a ticket's status. HappyFox: GET /api/1.1/json/statuses/.
Annotations the server declares
- title: List statuses
- readOnlyHint: true
happyfox_list_ticket_custom_fieldsList ticket custom fields: id, type, choices (with choice ids), required flags and categories.Reads text others writeNo findings
Why it is in this group
- The name "happyfox_list_ticket_custom_fields" says "list": a word for reading.
What it can reach
- untrusted-inputThe name "happyfox_list_ticket_custom_fields" says "list" and "ticket": it reads issues, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it 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/.
Annotations the server declares
- title: List ticket custom fields
- readOnlyHint: true
happyfox_list_ticketsList tickets, newest activity first, with optional filters and HappyFox's search syntax.Reads text others writeNo findings
Why it is in this group
- The name "happyfox_list_tickets" says "list": a word for reading.
What it can reach
- untrusted-inputThe name "happyfox_list_tickets" says "list" and "ticket": it reads issues, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it 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/.
Annotations the server declares
- title: List or search tickets
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
77 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data7
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write11
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__happyfox__happyfox_add_staff_reply"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 7 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://happyfox.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://happyfox.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 7 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://happyfox.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://happyfox.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http happyfox https://happyfox.usefulapi.io/mcpclaude mcp add --transport http happyfox https://happyfox.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__happyfox__happyfox_list_tickets",
"mcp__happyfox__happyfox_get_ticket",
"mcp__happyfox__happyfox_list_contacts",
"mcp__happyfox__happyfox_get_contact",
"mcp__happyfox__happyfox_list_contact_groups",
"mcp__happyfox__happyfox_get_contact_group",
"mcp__happyfox__happyfox_list_categories",
"mcp__happyfox__happyfox_list_staff",
"mcp__happyfox__happyfox_list_statuses",
"mcp__happyfox__happyfox_list_priorities",
"mcp__happyfox__happyfox_list_ticket_custom_fields",
"mcp__happyfox__happyfox_list_contact_custom_fields",
"mcp__happyfox__happyfox_list_reports",
"mcp__happyfox__happyfox_get_report_summary",
"mcp__happyfox__happyfox_get_report_tabular_data",
"mcp__happyfox__happyfox_list_kb_articles"
],
"ask": [],
"deny": [
"mcp__happyfox__happyfox_create_ticket",
"mcp__happyfox__happyfox_add_staff_reply",
"mcp__happyfox__happyfox_add_private_note",
"mcp__happyfox__happyfox_update_ticket_tags",
"mcp__happyfox__happyfox_update_ticket_custom_fields",
"mcp__happyfox__happyfox_create_contact",
"mcp__happyfox__happyfox_update_contact"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as happyfox. Review it before you use it.
Capability tags behind 15 rules
- mcp__happyfox__happyfox_list_tickets untrusted-input
- mcp__happyfox__happyfox_get_ticket private-data, untrusted-input
- mcp__happyfox__happyfox_list_contacts private-data
- mcp__happyfox__happyfox_get_contact private-data, untrusted-input
- mcp__happyfox__happyfox_list_contact_groups private-data, untrusted-input
- mcp__happyfox__happyfox_get_contact_group private-data
- mcp__happyfox__happyfox_list_categories untrusted-input
- mcp__happyfox__happyfox_list_staff private-data, untrusted-input
- mcp__happyfox__happyfox_list_statuses untrusted-input
- mcp__happyfox__happyfox_list_priorities untrusted-input
- mcp__happyfox__happyfox_list_ticket_custom_fields untrusted-input
- mcp__happyfox__happyfox_list_contact_custom_fields private-data
- mcp__happyfox__happyfox_get_report_summary untrusted-input
- mcp__happyfox__happyfox_get_report_tabular_data untrusted-input
- mcp__happyfox__happyfox_add_staff_reply outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/happyfox/verify?hash=1b62a2aab106d763f1afebc3c2ab0ed7e96bd90b6771ebc60d4cc39e6f445d5f" | jq -e '.changed == false'Pinned hash 1b62a2aab106, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/happyfox/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/happyfox)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
HappyFox MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the HappyFox MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 23 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the HappyFox MCP by usefulapi delete data?
- Yes. 7 tools can delete, cancel or revoke something: happyfox_create_ticket, happyfox_add_staff_reply, happyfox_add_private_note, happyfox_update_ticket_tags, happyfox_update_ticket_custom_fields, happyfox_create_contact and 1 more.
Can the HappyFox MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the HappyFox MCP by usefulapi have?
- 23 tools: 7 destructive, 16 read. happyfox_create_ticket, happyfox_add_staff_reply, happyfox_add_private_note, happyfox_update_ticket_tags, happyfox_update_ticket_custom_fields, happyfox_create_contact, happyfox_update_contact, happyfox_list_tickets and 15 more.
Does the HappyFox MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the HappyFox MCP by usefulapi send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): happyfox_add_staff_reply.
Has the HappyFox MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.