# Hello Club MCP by usefulapi (remote · hello-club.usefulapi.io)

Read Hello Club members, events, bookings and transactions; add members and charges.

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

## Components

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

## Channel facts

- Endpoint: `https://hello-club.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.5.3`

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

- **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**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2766 tokens (~197/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 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 Hello Club MCP by usefulapi server?

Hello Club MCP by usefulapi is a hosted endpoint at https://hello-club.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-hello-club 'https://hello-club.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-hello-club": {
      "type": "http",
      "url": "https://hello-club.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-25 (score 63, 0)

- [functional] Server version: 1.5.0 → 1.5.3

### 2026-10-24 (score 63, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 1.4.0 → 1.5.0
- [functional] Server version: 1.3.0 → 1.4.0
- [functional] Server version: 1.1.0 → 1.3.0

### 2026-10-23 (score 63, +1)

- [functional] Server version: 1.0.1 → 1.1.0

### 2026-10-22 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.0.1

### 2026-10-21 (score 62)

First indexed and scored.

## MCP tools (14)

### `hello_club_list_members` (~380 tokens)

List members

List or search the club's members (people and staff) with contact details, roles, memberships (subscriptions), account credit and amount owing. Filter by free text, gender, role, staff, money owing, account credit, current subscription state, ending subscriptions or a membership type. GET /member.

Input parameters:

- `fields` (array): Only return these fields of each item (e.g. ["id","firstName","lastName","email"]). Smaller replies are faster.
- `gender` (string): Filter on gender.
- `has_account_credit` (boolean): Only members with account credit (true) or without (false).
- `has_money_owing` (boolean): Only members with unpaid transactions (true) or without (false).
- `is_staff` (boolean): Only staff members (true) or only non-staff (false).
- `limit` (integer): Results per page, 1-100 (default 25).
- `membership_id` (string): Membership type id (hello_club_list_membership_types), used together with one of the subscription filters.
- `offset` (integer): Number of results to skip (default 0). Pass the previous reply's next_offset.
- `role` (string): Filter on role.
- `search` (string): Free-text search (name, email, member number...).
- `signed_up_since` (string): Sign-up date threshold.
- `subscription_ended` (string): Members whose subscription ended within the past hour/day/week/month/year.
- `subscription_ending` (string): Members whose subscription ends within the next hour/day/week/month/year.
- `updated_since` (string): Only members updated on or after this timestamp.
- `with_current_subscription` (boolean): Only members with a current membership subscription.
- `without_current_subscription` (boolean): Only members without a current membership subscription.

### `hello_club_get_member` (~76 tokens)

Get member

One member by id: profile, contact details, roles, subscriptions, account credit, amount owing, custom fields. Password hashes and payment-provider data are not returned. GET /member/{id}.

Input parameters:

- `member_id` (string, required): Hello Club member id (24 hex characters) - find it with hello_club_list_members.

### `hello_club_list_membership_types` (~41 tokens)

List membership types

The membership types (plans) the club sells: name, fee, term, age limits, renewal rules and access. GET /membership.

### `hello_club_get_membership_type` (~36 tokens)

Get membership type

One membership type by id. GET /membership/{id}.

Input parameters:

- `membership_id` (string, required): Membership type id.

### `hello_club_list_events` (~376 tokens)

List events

List or search events and classes (sessions, courses, tournaments) with dates, activity, area, organiser, capacity and attendance rules. Filter by date range, recurring, hidden, public, has attendees, has spaces left, rule type, activity, area or organiser. GET /event.

Input parameters:

- `activity_id` (string): Only events of this activity id.
- `area_id` (string): Only events in this area id.
- `category_id` (string): Only events in this category id.
- `fields` (array): Only return these fields of each item (e.g. ["id","firstName","lastName","email"]). Smaller replies are faster.
- `from_date` (string): Events from this date on (use together with to_date).
- `has_attendees` (boolean): Only events with at least one attendee.
- `has_spaces_left` (boolean): Only events that still have places left.
- `is_hidden` (boolean): Only hidden events (true) or visible ones (false).
- `is_public` (boolean): Only public events (true) or member-only ones (false).
- `is_recurring` (boolean): Only recurring events (true) or one-off events (false).
- `limit` (integer): Results per page, 1-100 (default 25).
- `membership_id` (string): Only events that can be attended with this membership type id.
- `offset` (integer): Number of results to skip (default 0). Pass the previous reply's next_offset.
- `organiser_id` (string): Only events organised by this member id.
- `rule_type` (string): Only events with this attendance rule type.
- `search` (string): Free-text search.
- `to_date` (string): Events up to this date (use together with from_date).

### `hello_club_get_event` (~58 tokens)

Get event

One event by id: dates, recurrence, activity, area, organiser, capacity, attendance rules, questions. GET /event/{id}.

Input parameters:

- `event_id` (string, required): Event id - find it with hello_club_list_events.

### `hello_club_list_event_attendees` (~169 tokens)

List event attendees

List who is signed up to events: member or guest, event, sign-up date, paid state, whether they attended. Filter by event, member or guest. GET /eventAttendee.

Input parameters:

- `event_id` (string): Only attendees of this event.
- `fields` (array): Only return these fields of each item (e.g. ["id","firstName","lastName","email"]). Smaller replies are faster.
- `guest_id` (string): Only attendances of this guest.
- `limit` (integer): Results per page, 1-100 (default 25).
- `member_id` (string): Only attendances of this member.
- `offset` (integer): Number of results to skip (default 0). Pass the previous reply's next_offset.

### `hello_club_list_bookings` (~298 tokens)

List bookings

List resource bookings (courts, rooms, lanes): owner, activity, area, start/end, paid state, recurrence. Filter by date range, member, activity, mode, area, recurring, paid or removed. GET /booking.

Input parameters:

- `activity_id` (string): Only bookings of this activity.
- `area_id` (string): Only bookings of this area.
- `fields` (array): Only return these fields of each item (e.g. ["id","firstName","lastName","email"]). Smaller replies are faster.
- `from_date` (string): Bookings from this date on (use together with to_date).
- `is_paid` (boolean): Only paid (true) or unpaid (false) bookings.
- `is_recurring` (boolean): Only recurring bookings (true) or one-off bookings (false).
- `is_removed` (boolean): Only removed (true) or active (false) bookings.
- `limit` (integer): Results per page, 1-100 (default 25).
- `member_id` (string): Only bookings that include this member.
- `mode_id` (string): Only bookings of this mode.
- `offset` (integer): Number of results to skip (default 0). Pass the previous reply's next_offset.
- `search` (string): Free-text search.
- `to_date` (string): Bookings up to this date (use together with from_date).

### `hello_club_list_transactions` (~259 tokens)

List transactions

List the club's financial transactions (invoices, charges, credits): member, type, amount, tax, due and payment dates, paid state. Filter by member, type, paid, credit or a date range on date / dueDate / paymentDate. GET /transaction.

Input parameters:

- `date_field` (string): Which date from_date / to_date apply to (default date).
- `fields` (array): Only return these fields of each item (e.g. ["id","firstName","lastName","email"]). Smaller replies are faster.
- `from_date` (string): From this date on (use together with to_date).
- `is_credit` (boolean): Only credit (true) or charge (false) transactions.
- `is_paid` (boolean): Only paid (true) or unpaid (false) transactions.
- `limit` (integer): Results per page, 1-100 (default 25).
- `member_id` (string): Only transactions of this member.
- `offset` (integer): Number of results to skip (default 0). Pass the previous reply's next_offset.
- `to_date` (string): Up to this date (use together with from_date).
- `type` (string): Transaction type.

### `hello_club_get_transaction` (~56 tokens)

Get transaction

One transaction by id: member, type, amount, tax, details, dates, paid state. GET /transaction/{id}.

Input parameters:

- `transaction_id` (string, required): Transaction id - find it with hello_club_list_transactions.

### `hello_club_list_check_ins` (~180 tokens)

List check-ins

List check-in logs (members arriving at the club): who, when, how (type). Filter by member or type, or only unknown people. GET /checkInLog.

Input parameters:

- `fields` (array): Only return these fields of each item (e.g. ["id","firstName","lastName","email"]). Smaller replies are faster.
- `is_unknown` (boolean): Only check-ins of unknown people (true).
- `limit` (integer): Results per page, 1-100 (default 25).
- `member_id` (string): Only check-ins of this member.
- `offset` (integer): Number of results to skip (default 0). Pass the previous reply's next_offset.
- `search` (string): Free-text search.
- `type` (string): Check-in type (as recorded by the club).

### `hello_club_list_access_logs` (~213 tokens)

List door access logs

List door / access-control logs in a date range: member, door, event, whether it was an override or an unknown person. GET /accessLog.

Input parameters:

- `door` (string): Only entries for this door id.
- `event_id` (string): Only entries for this event.
- `fields` (array): Only return these fields of each item (e.g. ["id","firstName","lastName","email"]). Smaller replies are faster.
- `from_date` (string, required): Start of the range (required).
- `is_override` (boolean): Only manual overrides (true).
- `is_unknown` (boolean): Only unknown people (true).
- `limit` (integer): Results per page, 1-100 (default 25).
- `member_id` (string): Only entries of this member.
- `offset` (integer): Number of results to skip (default 0). Pass the previous reply's next_offset.
- `to_date` (string, required): End of the range (required).

### `hello_club_create_member` (~140 tokens)

Create member

WRITE: create a new member in the club (first and last name required; email, mobile, phone and gender optional). Creates a real member record in the club's database; it does not assign a membership or send an invoice. Not idempotent: calling twice creates two members, so search with hello_club_list_members first. POST /member.

Input parameters:

- `email` (string): Email address.
- `first_name` (string, required): First name.
- `gender` (string): Gender.
- `last_name` (string, required): Last name.
- `mobile` (string): Mobile phone number.
- `phone` (string): Other phone number.

### `hello_club_create_transaction` (~223 tokens)

Create transaction

WRITE: create a financial transaction for a member (a charge, or a credit when is_credit is true), e.g. an invoice line or a manual adjustment. This changes the member's amount owing / account credit in the club's books and, with notify_by_email, emails the member. Not idempotent: calling twice creates two transactions. Confirm member, amount and type with the user first. POST /transaction.

Input parameters:

- `amount` (number, required): Amount in the club's currency, a positive number (tax inclusive).
- `date` (string): Transaction date (default: now).
- `details` (string, required): Description shown on the invoice.
- `due_date` (string): Payment due date.
- `is_credit` (boolean): True = a credit to the member instead of a charge (default false).
- `member_id` (string, required): Member the transaction is for.
- `notify_by_email` (boolean): Email the member about this transaction (default false).
- `type` (string, required): Transaction type (use 'other' for a manual charge).

## Diagnostics

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

## Score history

- 2026-10-25: 63
- 2026-10-24: 63
- 2026-10-23: 63
- 2026-10-22: 62
- 2026-10-21: 62

## Common questions

### What is the Hello Club MCP by usefulapi server?

Hello Club MCP by usefulapi is listed in the public MCP registry as io.usefulapi/hello-club. Read Hello Club members, events, bookings and transactions; add members and charges. This page covers its hosted endpoint (https://hello-club.usefulapi.io/mcp).

### Is the Hello Club MCP by usefulapi server safe to use?

Hello Club MCP by usefulapi scores 63 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 Hello Club MCP by usefulapi server expose?

Hello Club MCP by usefulapi exposes 14 tools: hello_club_list_members, hello_club_get_member, hello_club_list_membership_types, hello_club_get_membership_type, hello_club_list_events, and 9 more. Their descriptions and schemas cost roughly 2,505 tokens of context every time the server is loaded.

### Does the Hello Club MCP by usefulapi server require authentication?

Yes. Hello Club 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 Hello Club MCP by usefulapi server still maintained?

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