io.usefulapi/happyfox
REMOTE · HAPPYFOX.USEFULAPI.IO · SCANNED OCT 4
Triage HappyFox tickets, contacts and KB articles, run reports, and reply or add private notes.
Available components
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 Security89
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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
- We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 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
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.
remote · happyfox.usefulapi.io
claude mcp add --transport http io-usefulapi-happyfox 'https://happyfox.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-happyfox": {
"url": "https://happyfox.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-happyfox": {
"type": "http",
"url": "https://happyfox.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-happyfox] url = "https://happyfox.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-happyfox": {
"type": "remote",
"url": "https://happyfox.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-happyfox --url 'https://happyfox.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-happyfox:
url: "https://happyfox.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-happyfox": {
"Transport": "http",
"Url": "https://happyfox.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-happyfox -t streamable-http -u 'https://happyfox.usefulapi.io/mcp'
{
"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.
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.
- 4 Oct 26 +44
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Stability: unverified → 0.07 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 3 Oct 26 −43
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- 2 Oct 26 +43
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
- 1 Oct 26 +5
- 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. security
- 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. functional
- 30 Sept 26 +10
- 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. security
- 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. functional
- 29 Sept 26 18
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 4 Oct 2026 · Probed https://happyfox.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 happyfox.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 | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://happyfox.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://happyfox.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://happyfox.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://happyfox.usefulapi.io/mcp |
| Authorisation server | https://happyfox.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://happyfox.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://happyfox.usefulapi.io/mcp | HTTPS enforced | 301 | https://happyfox.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 →
happyfox_add_private_note Add a private note to a ticket ~358
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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). |
No output schema declared.
No examples provided.
happyfox_add_staff_reply Reply to a ticket as an agent ~440
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
happyfox_create_contact Create a contact ~162
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
| string | yes | Contact email address. | |
| name | string | yes | Contact name. |
| phones | array | – | Phone numbers. |
No output schema declared.
No examples provided.
happyfox_create_ticket Create a ticket ~361
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| string | yes | Contact email address. | |
| html | string | – | Message in HTML (text or html is required). |
| name | string | yes | Contact name. |
| phone | string | – | Contact phone number. |
| priority | integer | – | Priority id (happyfox_list_priorities); defaults to the default priority. |
| subject | string | yes | 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. |
No output schema declared.
No examples provided.
happyfox_get_contact Get one contact ~71
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>/.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | yes | The contact's numeric id (e.g. "33") or email address. |
No output schema declared.
No examples provided.
happyfox_get_contact_group Get one contact group ~50
Fetch a contact group and its member contacts. HappyFox: GET /api/1.1/json/contact_group/<id>/.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_group_id | integer | yes | The contact group id. |
No output schema declared.
No examples provided.
happyfox_get_report_summary Get a report summary ~64
Summary counts for a saved report: ticket, completed, assigned, pending and unassigned counts. HappyFox: GET /api/1.1/json/report/<id>/.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | integer | yes | The report (from happyfox_list_reports) id. |
No output schema declared.
No examples provided.
happyfox_get_report_tabular_data Get a report's ticket rows ~116
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 1. |
| report_id | integer | yes | The report (from happyfox_list_reports) id. |
| size | integer | – | Results per page, 1-50 (HappyFox default 10). |
No output schema declared.
No examples provided.
happyfox_get_ticket Get one ticket ~129
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>/.
| Name | Type | Req | Description |
|---|---|---|---|
| show_cf_changes | boolean | – | Include the history of custom-field changes in the updates. |
| ticket_number | integer | yes | The ticket NUMBER (the `id` field, e.g. 3 for #DC00000003) — not the prefixed display id. |
No output schema declared.
No examples provided.
happyfox_list_categories List categories ~42
List ticket categories (queues) with their ids — needed to create a ticket or filter tickets. HappyFox: GET /api/1.1/json/categories/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
happyfox_list_contact_custom_fields List contact custom fields ~52
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/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
happyfox_list_contact_groups List contact groups ~39
List contact groups (typically customer companies) with their tagged email domains. HappyFox: GET /api/1.1/json/contact_groups/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
happyfox_list_contacts List or search contacts ~133
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
happyfox_list_kb_articles Export knowledge-base articles ~75
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| internal | boolean | – | true = internal articles; false/omitted = external articles. |
No output schema declared.
No examples provided.
happyfox_list_priorities List priorities ~41
List ticket priorities with ids — ids used to set a ticket's priority. HappyFox: GET /api/1.1/json/priorities/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
happyfox_list_reports List reports ~40
List the saved reports (id, name, description) from the Reports module. HappyFox: GET /api/1.1/json/reports/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
happyfox_list_staff List agents ~56
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/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
happyfox_list_statuses List statuses ~47
List ticket statuses with ids and behaviour (pending / completed) — ids used to change a ticket's status. HappyFox: GET /api/1.1/json/statuses/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
happyfox_list_ticket_custom_fields List ticket custom fields ~59
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/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
happyfox_list_tickets List or search tickets ~327
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
happyfox_update_contact Edit a contact ~141
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>/.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | 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. |
| string | – | New email address. | |
| name | string | – | New name. |
No output schema declared.
No examples provided.
happyfox_update_ticket_custom_fields Edit a ticket's custom fields ~157
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_fields | object | yes | 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 | yes | The agent making the change id. |
| ticket_number | integer | yes | The ticket NUMBER (the `id` field, e.g. 3 for #DC00000003) — not the prefixed display id. |
No output schema declared.
No examples provided.
happyfox_update_ticket_tags Add or remove ticket tags ~134
Add and/or remove tags on a ticket without touching anything else. HappyFox: POST /api/1.1/json/ticket/<ticket_number>/update_tags/.
| Name | Type | Req | Description |
|---|---|---|---|
| add | string | – | Tags to add, as a comma-separated string. |
| remove | string | – | Tags to remove, as a comma-separated string. |
| staff_id | integer | yes | The agent making the change (shown in the ticket history) id. |
| ticket_number | integer | yes | The ticket NUMBER (the `id` field, e.g. 3 for #DC00000003) — not the prefixed display id. |
No output schema declared.
No examples provided.
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.