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

Check classes, attendance, customers, memberships and invoices in TeamUp and register customers.

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

## Components

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

## Channel facts

- Endpoint: `https://goteamup.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3632 tokens (~181/item across 20 items; 20 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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.usefulapi/goteamup MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-goteamup": {
      "type": "http",
      "url": "https://goteamup.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-03 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-02 (score 75, 0)

- [functional] Server version: 1.3.0 → 1.5.1

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

- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.3.0

### 2026-09-30 (score 70, +52)

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

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

First indexed and scored.

## MCP tools (20)

### `goteamup_get_authenticated_application` (~65 tokens)

Get the authenticated application

Show the API application this token belongs to and the businesses (providers) it can reach, with their numeric ids — a cheap way to confirm the token works and to find the value for GOTEAMUP_PROVIDER_ID. TeamUp: GET /auth/application.

### `goteamup_list_customers` (~314 tokens)

List customers

Search and list the business's customers (members and leads). Filter by free text (email and name), CRM status, active memberships, age or family. Deferred fields such as field_values, credit_balance or sms_account can be added with expand. TeamUp: GET /customers.

Input parameters:

- `active_memberships` (array): Only customers holding one of these membership (plan) ids.
- `age_gte` (number): Minimum age in years.
- `age_lte` (number): Maximum age in years.
- `autocomplete` (string): Prefix match from the start of email and name fields.
- `deleted` (boolean): Filter by deleted (true) or not deleted (false).
- `expand` (string): Comma-separated related fields to expand into full objects (dot-nested, max depth 4), e.g. customer,event.instructors.
- `family` (integer): Only customers in this family id.
- `fields` (string): Comma-separated fields to return (dot notation for nested), e.g. id,name,starts_at.
- `ids` (array): Only these customer ids.
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Results per page, 1-100 (default 100).
- `query` (string): Free-text match against email and name.
- `status` (array): CRM status slugs, as shown in a customer's `status` field; pass 'null' for customers without a status.

### `goteamup_get_customer` (~135 tokens)

Get one customer

Fetch one customer by id: name, email, family role, lead flag, CRM status, created date. Use expand for deferred fields, e.g. field_values,credit_balance,staff_assignments. TeamUp: GET /customers/{id}.

Input parameters:

- `customer_id` (integer, required): The customer's numeric id.
- `expand` (string): Comma-separated related fields to expand into full objects (dot-nested, max depth 4), e.g. customer,event.instructors.
- `fields` (string): Comma-separated fields to return (dot notation for nested), e.g. id,name,starts_at.

### `goteamup_list_events` (~422 tokens)

List events (classes and appointments)

List scheduled sessions — classes and appointments — with start/end time, status, capacity, attending and waitlist counts, instructors, venue and offering type. Filter by time window, instructor, venue, offering type, status or occupancy. TeamUp: GET /events.

Input parameters:

- `ends_at_gte` (string): Only events ending at or after (ISO 8601 timestamp, e.g. 2026-10-01T00:00:00Z).
- `ends_at_lte` (string): Only events ending at or before (ISO 8601 timestamp, e.g. 2026-10-01T00:00:00Z).
- `expand` (string): Comma-separated related fields to expand into full objects (dot-nested, max depth 4), e.g. customer,event.instructors.
- `fields` (string): Comma-separated fields to return (dot notation for nested), e.g. id,name,starts_at.
- `ids` (array): Only these event ids.
- `instructors` (array): Only events taught by these instructor ids ('me' for your own).
- `occupancy_status` (array): Only events matching at least one of these occupancy states.
- `offering_types` (array): Only events of these offering type (class type) ids.
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Results per page, 1-100 (default 100).
- `sort` (string): Ordering; '-' for descending.
- `starts_at_gte` (string): Only events starting at or after (ISO 8601 timestamp, e.g. 2026-10-01T00:00:00Z).
- `starts_at_lte` (string): Only events starting at or before (ISO 8601 timestamp, e.g. 2026-10-01T00:00:00Z).
- `status` (array): Event status.
- `venues` (array): Only events at these venue ids.

### `goteamup_get_event` (~122 tokens)

Get one event

Fetch one class or appointment by id, including capacity, attending/waiting counts, registration open/close and late-cancel deadlines. TeamUp: GET /events/{id}.

Input parameters:

- `event_id` (integer, required): The event's numeric id.
- `expand` (string): Comma-separated related fields to expand into full objects (dot-nested, max depth 4), e.g. customer,event.instructors.
- `fields` (string): Comma-separated fields to return (dot notation for nested), e.g. id,name,starts_at.

### `goteamup_list_attendances` (~337 tokens)

List attendances (bookings)

List bookings: who is registered for, attended, no-showed or late-cancelled which event, and with which customer membership. Filter by customer, event, venue, offering type, status or event start window. Use expand=customer,event for names. TeamUp: GET /attendances.

Input parameters:

- `customer` (array): Only these customer ids.
- `event` (array): Only these event ids.
- `event_starts_at_gte` (string): Only attendances for events starting at or after (ISO 8601 timestamp, e.g. 2026-10-01T00:00:00Z).
- `event_starts_at_lte` (string): Only attendances for events starting at or before (ISO 8601 timestamp, e.g. 2026-10-01T00:00:00Z).
- `expand` (string): Comma-separated related fields to expand into full objects (dot-nested, max depth 4), e.g. customer,event.instructors.
- `fields` (string): Comma-separated fields to return (dot notation for nested), e.g. id,name,starts_at.
- `offering_types` (array): Only these offering type ids.
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Results per page, 1-100 (default 100).
- `sort` (string): Ordering; '-' for descending.
- `status` (array): Attendance status; plans_to_attend = registered or waitlisted.
- `venue` (array): Only these venue ids.

### `goteamup_list_customer_memberships` (~343 tokens)

List customer memberships

List memberships held by customers — status (active, hold, complete, cancelled), start/expiration/renewal dates, billed price, active hold. Filter by customer, membership plan, type, status, dates or holds. TeamUp: GET /customer_memberships.

Input parameters:

- `customer` (array): Only these customer ids.
- `expand` (string): Comma-separated related fields to expand into full objects (dot-nested, max depth 4), e.g. customer,event.instructors.
- `expiration_date_gte` (string): Expiration date on or after (date, YYYY-MM-DD).
- `expiration_date_lte` (string): Expiration date on or before (date, YYYY-MM-DD).
- `fields` (string): Comma-separated fields to return (dot notation for nested), e.g. id,name,starts_at.
- `has_active_hold` (boolean): Only memberships with (true) or without (false) a current or upcoming hold.
- `ids` (array): Only these customer membership ids.
- `membership` (array): Only these membership (plan) ids.
- `membership_type` (array): Membership type.
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Results per page, 1-100 (default 100).
- `sort` (string): Ordering; '-' for descending.
- `start_date_gte` (string): Start date on or after (date, YYYY-MM-DD).
- `start_date_lte` (string): Start date on or before (date, YYYY-MM-DD).
- `status` (array): Customer membership status.

### `goteamup_get_customer_membership` (~129 tokens)

Get one customer membership

Fetch one customer membership by id. Use expand=usage_summary,next_billing_date,shared_with for usage, next bill and sharing. TeamUp: GET /customer_memberships/{id}.

Input parameters:

- `customer_membership_id` (integer, required): The customer membership's numeric id.
- `expand` (string): Comma-separated related fields to expand into full objects (dot-nested, max depth 4), e.g. customer,event.instructors.
- `fields` (string): Comma-separated fields to return (dot notation for nested), e.g. id,name,starts_at.

### `goteamup_list_memberships` (~228 tokens)

List memberships (plans)

List the membership products the business sells — packs, recurring and prepaid plans — with price, duration, allotment, active member count and visibility. TeamUp: GET /memberships.

Input parameters:

- `expand` (string): Comma-separated related fields to expand into full objects (dot-nested, max depth 4), e.g. customer,event.instructors.
- `fields` (string): Comma-separated fields to return (dot notation for nested), e.g. id,name,starts_at.
- `for_sale` (boolean): Only memberships currently for sale (true) or not (false).
- `is_dropin` (boolean): Filter drop-in memberships.
- `name_contains` (string): Only memberships whose name contains this text.
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Results per page, 1-100 (default 100).
- `permits_registration_for_event` (integer): Only memberships that can be used to book this event id.
- `visible_to_customers` (boolean): Filter by customer visibility.

### `goteamup_list_offering_types` (~203 tokens)

List offering types (class types)

List offering types — the kinds of classes, appointments and courses the business runs — with schedule type, drop-in price, age limits, visibility and status. TeamUp: GET /offering_types.

Input parameters:

- `expand` (string): Comma-separated related fields to expand into full objects (dot-nested, max depth 4), e.g. customer,event.instructors.
- `fields` (string): Comma-separated fields to return (dot notation for nested), e.g. id,name,starts_at.
- `has_active_sessions` (boolean): Only offering types with upcoming active sessions.
- `name_contains` (string): Only offering types whose name contains this text.
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Results per page, 1-100 (default 100).
- `sort` (string): Ordering; '-' for descending.
- `status` (string): Offering type status.

### `goteamup_list_instructors` (~149 tokens)

List instructors

List the business's instructors (coaches, trainers) with name, bio and linked staff id. TeamUp: GET /instructors.

Input parameters:

- `expand` (string): Comma-separated related fields to expand into full objects (dot-nested, max depth 4), e.g. customer,event.instructors.
- `fields` (string): Comma-separated fields to return (dot notation for nested), e.g. id,name,starts_at.
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Results per page, 1-100 (default 100).
- `query` (string): Free-text match on the instructor.

### `goteamup_list_venues` (~160 tokens)

List venues

List the business's venues (physical locations and online venues) with address, timezone and rooms. TeamUp: GET /venues.

Input parameters:

- `expand` (string): Comma-separated related fields to expand into full objects (dot-nested, max depth 4), e.g. customer,event.instructors.
- `fields` (string): Comma-separated fields to return (dot notation for nested), e.g. id,name,starts_at.
- `has_active_sessions` (boolean): Only venues with non-cancelled sessions.
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Results per page, 1-100 (default 100).
- `status` (string): Venue status.

### `goteamup_list_invoices` (~190 tokens)

List invoices

List invoices with status (open, paid, failed, voided, upcoming, …), due date, amount due, payer and receipt URL. Filter by status or a customer membership. TeamUp: GET /invoices.

Input parameters:

- `customer_membership` (integer): Only invoices for this customer membership id.
- `expand` (string): Comma-separated related fields to expand into full objects (dot-nested, max depth 4), e.g. customer,event.instructors.
- `fields` (string): Comma-separated fields to return (dot notation for nested), e.g. id,name,starts_at.
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Results per page, 1-100 (default 100).
- `sort` (string): Ordering; '-' for descending.
- `status` (array): Invoice status.

### `goteamup_get_invoice` (~122 tokens)

Get one invoice

Fetch one invoice by id. Use expand=line_items,charges,discounts,taxes,applied_credits for the breakdown. TeamUp: GET /invoices/{id}.

Input parameters:

- `expand` (string): Comma-separated related fields to expand into full objects (dot-nested, max depth 4), e.g. customer,event.instructors.
- `fields` (string): Comma-separated fields to return (dot notation for nested), e.g. id,name,starts_at.
- `invoice_id` (integer, required): The invoice's numeric id.

### `goteamup_list_crm_interactions` (~164 tokens)

List CRM interactions

List logged CRM interactions (calls, emails, meetings, contacted) with notes and who logged them, optionally for one customer. Requires a super_admin-level token. TeamUp: GET /crm/interactions.

Input parameters:

- `customer` (integer): Only interactions for this customer id.
- `expand` (string): Comma-separated related fields to expand into full objects (dot-nested, max depth 4), e.g. customer,event.instructors.
- `fields` (string): Comma-separated fields to return (dot notation for nested), e.g. id,name,starts_at.
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Results per page, 1-100 (default 100).

### `goteamup_create_customer` (~123 tokens)

Create (invite) a customer

Add a new customer to the business as staff. By default TeamUp emails them an invitation to claim the profile; set send_invitation_email=false to add them silently. TeamUp: POST /customers.

Input parameters:

- `email` (string): Email address (used for the invitation).
- `first_name` (string, required): First name.
- `invitation_note` (string): A personal note included in the invitation email.
- `last_name` (string, required): Last name.
- `send_invitation_email` (boolean): Send the invitation email (TeamUp default: true).

### `goteamup_register_customer_for_event` (~131 tokens)

Book a customer into an event

Register a customer for a class or appointment, optionally using a specific customer membership, or comped (free). Returns the attendance id. Undo with goteamup_unregister_customer_from_event. TeamUp: POST /events/{id}/register.

Input parameters:

- `comped` (boolean): Book as comped (no membership use / charge). Default false.
- `customer` (integer, required): The customer's numeric id.
- `customer_membership` (integer): The customer membership id to book with (omit to let TeamUp choose).
- `event_id` (integer, required): The event's numeric id.

### `goteamup_unregister_customer_from_event` (~122 tokens)

Remove a customer from an event

Cancel a customer's booking for a class or appointment. is_late_cancel=true records it as a LATE cancel, which can trigger the business's penalty rules — leave it unset unless asked. The response says whether it counted as late. TeamUp: POST /events/{id}/unregister.

Input parameters:

- `customer` (integer, required): The customer's numeric id.
- `event_id` (integer, required): The event's numeric id.
- `is_late_cancel` (boolean): Record as a late cancellation (may incur penalties). Omit unless explicitly requested.

### `goteamup_confirm_attendance` (~67 tokens)

Check a customer in

Confirm that a customer attended an event (check them in). Returns the updated attendance. TeamUp: POST /events/{id}/confirm_attendance.

Input parameters:

- `customer` (integer, required): The customer's numeric id.
- `event_id` (integer, required): The event's numeric id.

### `goteamup_log_crm_interaction` (~106 tokens)

Log a CRM interaction

Record a call, email, meeting or contact with a customer or lead, with an optional note and call outcome. Requires a super_admin-level token. TeamUp: POST /crm/interactions.

Input parameters:

- `call_outcome` (string): Outcome — only for interaction_type=Call.
- `customer` (integer, required): The customer's numeric id.
- `interaction_type` (string, required): Kind of interaction.
- `note` (string): Free-text notes about the interaction.

## Diagnostics

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

## Score history

- 2026-10-04: 76
- 2026-10-03: 76
- 2026-10-02: 75
- 2026-10-01: 75
- 2026-09-30: 70
- 2026-09-29: 18

## Common questions

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

io.usefulapi/goteamup is an MCP server listed in the public MCP registry as io.usefulapi/goteamup. Check classes, attendance, customers, memberships and invoices in TeamUp and register customers. This page covers its hosted endpoint (https://goteamup.usefulapi.io/mcp).

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

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

io.usefulapi/goteamup exposes 20 tools: goteamup_get_authenticated_application, goteamup_list_customers, goteamup_get_customer, goteamup_list_events, goteamup_get_event, and 15 more. Their descriptions and schemas cost roughly 3,632 tokens of context every time the server is loaded.

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

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

io.usefulapi/goteamup is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://goteamup.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-goteamup/goteamup.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-goteamup/goteamup.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-goteamup/goteamup