Hello Club MCP by usefulapi
REMOTE · HELLO-CLUB.USEFULAPI.IO
Read Hello Club members, events, bookings and transactions; add members and charges.
Available components
Last scanned (6 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 25 Oct 2026.
Category CRM and Sales
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 Security78
- 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 enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
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.
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 23 Oct 26 +1
- Server version: 1.0.1 → 1.1.0 functional
- 22 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.0.1 functional
- 21 Oct 26 62
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 25 Oct 2026 · Probed https://hello-club.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 hello-club.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 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 | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://hello-club.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://hello-club.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://hello-club.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://hello-club.usefulapi.io/mcp |
| Authorisation server | https://hello-club.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hello-club.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/hello-club/ |
| http (plaintext) | http://hello-club.usefulapi.io/mcp | Inconclusive | 302 | http://hello-club.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 →
hello_club_create_member Create member ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email address. | |
| first_name | string | yes | First name. |
| gender | string | – | Gender. |
| last_name | string | yes | Last name. |
| mobile | string | – | Mobile phone number. |
| phone | string | – | Other phone number. |
No output schema declared.
No examples provided.
hello_club_create_transaction Create transaction ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount in the club's currency, a positive number (tax inclusive). |
| date | string | – | Transaction date (default: now). |
| details | string | yes | 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 | yes | Member the transaction is for. |
| notify_by_email | boolean | – | Email the member about this transaction (default false). |
| type | string | yes | Transaction type (use 'other' for a manual charge). |
No output schema declared.
No examples provided.
hello_club_get_event Get event ~58
One event by id: dates, recurrence, activity, area, organiser, capacity, attendance rules, questions. GET /event/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | Event id - find it with hello_club_list_events. |
No output schema declared.
No examples provided.
hello_club_get_member Get member ~76
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| member_id | string | yes | Hello Club member id (24 hex characters) - find it with hello_club_list_members. |
No output schema declared.
No examples provided.
hello_club_get_membership_type Get membership type ~36
One membership type by id. GET /membership/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| membership_id | string | yes | Membership type id. |
No output schema declared.
No examples provided.
hello_club_get_transaction Get transaction ~56
One transaction by id: member, type, amount, tax, details, dates, paid state. GET /transaction/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| transaction_id | string | yes | Transaction id - find it with hello_club_list_transactions. |
No output schema declared.
No examples provided.
hello_club_list_access_logs List door access logs ~213
List door / access-control logs in a date range: member, door, event, whether it was an override or an unknown person. GET /accessLog.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | End of the range (required). |
No output schema declared.
No examples provided.
hello_club_list_bookings List bookings ~298
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
hello_club_list_check_ins List check-ins ~180
List check-in logs (members arriving at the club): who, when, how (type). Filter by member or type, or only unknown people. GET /checkInLog.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
hello_club_list_event_attendees List event attendees ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
hello_club_list_events List events ~376
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
hello_club_list_members List members ~380
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
hello_club_list_membership_types List membership types ~41
The membership types (plans) the club sells: name, fee, term, age limits, renewal rules and access. GET /membership.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hello_club_list_transactions List transactions ~259
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · hello-club.usefulapi.io
claude mcp add --transport http io-usefulapi-hello-club 'https://hello-club.usefulapi.io/mcp'
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.