io.usefulapi/goteamup
REMOTE · GOTEAMUP.USEFULAPI.IO · SCANNED OCT 4
Check classes, attendance, customers, memberships and invoices in TeamUp and register customers.
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 Usability69
- AI-judged instruction clarity (excellent).Pass
- 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. 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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 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/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.
remote · goteamup.usefulapi.io
claude mcp add --transport http io-usefulapi-goteamup 'https://goteamup.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-goteamup": {
"url": "https://goteamup.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-goteamup": {
"type": "http",
"url": "https://goteamup.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-goteamup] url = "https://goteamup.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-goteamup": {
"type": "remote",
"url": "https://goteamup.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-goteamup --url 'https://goteamup.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-goteamup:
url: "https://goteamup.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-goteamup": {
"Transport": "http",
"Url": "https://goteamup.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-goteamup -t streamable-http -u 'https://goteamup.usefulapi.io/mcp'
{
"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.
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.
- 3 Oct 26 +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.
- 2 Oct 26 0
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +52
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → 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
- 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://goteamup.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 goteamup.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://goteamup.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://goteamup.usefulapi.io/.well-known/oauth-protected-resource/mcp" Protected resource metadata
| Document | https://goteamup.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://goteamup.usefulapi.io/mcp |
| Authorisation server | https://goteamup.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://goteamup.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://goteamup.usefulapi.io/mcp | HTTPS enforced | 301 | https://goteamup.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 →
goteamup_confirm_attendance Check a customer in ~67
Confirm that a customer attended an event (check them in). Returns the updated attendance. TeamUp: POST /events/{id}/confirm_attendance.
| Name | Type | Req | Description |
|---|---|---|---|
| customer | integer | yes | The customer's numeric id. |
| event_id | integer | yes | The event's numeric id. |
No output schema declared.
No examples provided.
goteamup_create_customer Create (invite) a customer ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email address (used for the invitation). | |
| first_name | string | yes | First name. |
| invitation_note | string | – | A personal note included in the invitation email. |
| last_name | string | yes | Last name. |
| send_invitation_email | boolean | – | Send the invitation email (TeamUp default: true). |
No output schema declared.
No examples provided.
goteamup_get_authenticated_application Get the authenticated application ~65
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
goteamup_get_customer Get one customer ~135
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | 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. |
No output schema declared.
No examples provided.
goteamup_get_customer_membership Get one customer membership ~129
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_membership_id | integer | yes | 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. |
No output schema declared.
No examples provided.
goteamup_get_event Get one event ~122
Fetch one class or appointment by id, including capacity, attending/waiting counts, registration open/close and late-cancel deadlines. TeamUp: GET /events/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | integer | yes | 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. |
No output schema declared.
No examples provided.
goteamup_get_invoice Get one invoice ~122
Fetch one invoice by id. Use expand=line_items,charges,discounts,taxes,applied_credits for the breakdown. TeamUp: GET /invoices/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The invoice's numeric id. |
No output schema declared.
No examples provided.
goteamup_list_attendances List attendances (bookings) ~337
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
goteamup_list_crm_interactions List CRM interactions ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
goteamup_list_customer_memberships List customer memberships ~343
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
goteamup_list_customers List customers ~314
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
goteamup_list_events List events (classes and appointments) ~422
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
goteamup_list_instructors List instructors ~149
List the business's instructors (coaches, trainers) with name, bio and linked staff id. TeamUp: GET /instructors.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
goteamup_list_invoices List invoices ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
goteamup_list_memberships List memberships (plans) ~228
List the membership products the business sells — packs, recurring and prepaid plans — with price, duration, allotment, active member count and visibility. TeamUp: GET /memberships.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
goteamup_list_offering_types List offering types (class types) ~203
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
goteamup_list_venues List venues ~160
List the business's venues (physical locations and online venues) with address, timezone and rooms. TeamUp: GET /venues.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
goteamup_log_crm_interaction Log a CRM interaction ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| call_outcome | string | – | Outcome — only for interaction_type=Call. |
| customer | integer | yes | The customer's numeric id. |
| interaction_type | string | yes | Kind of interaction. |
| note | string | – | Free-text notes about the interaction. |
No output schema declared.
No examples provided.
goteamup_register_customer_for_event Book a customer into an event ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| comped | boolean | – | Book as comped (no membership use / charge). Default false. |
| customer | integer | yes | The customer's numeric id. |
| customer_membership | integer | – | The customer membership id to book with (omit to let TeamUp choose). |
| event_id | integer | yes | The event's numeric id. |
No output schema declared.
No examples provided.
goteamup_unregister_customer_from_event Remove a customer from an event ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer | integer | yes | The customer's numeric id. |
| event_id | integer | yes | The event's numeric id. |
| is_late_cancel | boolean | – | Record as a late cancellation (may incur penalties). Omit unless explicitly requested. |
No output schema declared.
No examples provided.
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.