# Waitwhile MCP by usefulapi (remote · waitwhile.usefulapi.io)

Read Waitwhile visits, bookings, customers, services and analytics; add, update and cancel visits.

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

## Components

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

## Channel facts

- Endpoint: `https://waitwhile.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-17.

- **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**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 4119 tokens (~142/item across 29 items; 29 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 77% 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 29 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 30 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 Waitwhile MCP by usefulapi server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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

### 2026-10-14 (score 62, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 59, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 58)

First indexed and scored.

## MCP tools (29)

### `waitwhile_list_locations` (~135 tokens)

List locations

List the account's locations (businesses/sites): id, name, short name, address, time zone, opening hours and waitlist/booking settings. Use the ids to filter visits, services and resources. GET /locations.

Input parameters:

- `country_code` (string): Two-letter country code.
- `desc` (boolean): Newest first.
- `external_id` (string): Only the location with this external id.
- `limit` (integer): Results per page, 1-100 (default 20).
- `start_after` (string): Cursor: pass the previous reply's next_start_after to get the next page.

### `waitwhile_get_location` (~48 tokens)

Get location

One location by id or short name (the part of its public Waitwhile URL). GET /locations/{shortNameOrId}.

Input parameters:

- `location` (string, required): Location id or short name.

### `waitwhile_list_location_status` (~85 tokens)

List location status (live waitlist)

Live status of every location: open/closed, number of people waiting and being served, current estimated wait time, and booking counters. GET /location-status.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 20).
- `start_after` (string): Cursor: pass the previous reply's next_start_after to get the next page.

### `waitwhile_get_location_status` (~47 tokens)

Get location status (live waitlist)

Live status of one location: open/closed, waiting and serving counts, estimated wait. GET /location-status/{locationId}.

Input parameters:

- `location_id` (string, required): Location id.

### `waitwhile_list_visits` (~324 tokens)

List visits (waitlist entries and bookings)

List visits: waitlist entries (people in line) and bookings (appointments), with customer, state (PENDING, DRAFT, BOOKED, WAITING, SERVING, COMPLETE), tags (e.g. NO-SHOW, CANCELLED, ARRIVED), services, resources, party size, position and timestamps. Filter by location, state, tag, customer, service, resource, booking date (local time) or created/updated date. Cursor-paged. Contains customer contact details. GET /visits.

Input parameters:

- `customer_id` (string)
- `desc` (boolean): Newest first.
- `external_customer_id` (string)
- `from_booking_date` (string): Bookings starting at or after this local date-time, YYYY-MM-DDThh:mm.
- `from_date` (string): Visits created from this date-time (ISO 8601 or epoch ms).
- `limit` (integer): Results per page, 1-100 (default 20).
- `location_id` (string): Only visits at this location.
- `resource_id` (string)
- `service_id` (string)
- `start_after` (string): Cursor: pass the previous reply's next_start_after to get the next page.
- `state` (string)
- `tag` (string)
- `to_booking_date` (string): Bookings starting at or before this local date-time, YYYY-MM-DDThh:mm.
- `to_date` (string): Visits created up to this date-time (ISO 8601 or epoch ms).

### `waitwhile_search_visits` (~157 tokens)

Search visits

Search visits by a prefix match on customer name, phone, e-mail or customer id, optionally filtered by location, state, tag and excluded tags. Page-numbered. Contains customer contact details. GET /visits/search.

Input parameters:

- `exclude_tags` (array): Leave out visits carrying any of these tags.
- `limit` (integer): Results per page, 1-100 (default 20).
- `location_id` (string)
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `q` (string, required): Prefix match on name, phone, e-mail or customer id.
- `state` (string)
- `tag` (string)

### `waitwhile_get_visit` (~61 tokens)

Get visit

One visit (waitlist entry or booking) by id: customer, state, tags, services, resources, party size, position, estimated wait and all timestamps. GET /visits/{visitId}.

Input parameters:

- `visit_id` (string, required): Visit id.

### `waitwhile_list_booking_slots` (~167 tokens)

List booking slots

Booking slots of a location for a date range with the free spots per resource and service, so you can see when an appointment can be booked. Dates are local to the location, YYYY-MM-DDThh:mm. GET /visits/availability.

Input parameters:

- `from_date` (string): Local start, YYYY-MM-DDThh:mm.
- `location_id` (string, required): Location id.
- `resource_ids` (array): Only slots for these resources.
- `service_duration` (integer): Service duration in seconds, to size the slots.
- `service_ids` (array): Only slots for these services.
- `show_min_spots` (integer): Only slots with at least this many free spots.
- `to_date` (string): Local end, YYYY-MM-DDThh:mm.

### `waitwhile_first_available_slots` (~148 tokens)

First available booking slots

The first available booking slots of a location (optionally for a party size, services and resources) from a date. Use it to propose appointment times. GET /visits/first-available-slots.

Input parameters:

- `from_date` (string): Local start, YYYY-MM-DDThh:mm.
- `location_id` (string, required): Location id.
- `max_num_slots` (integer): Max number of slots to return.
- `party_size` (integer)
- `resource_ids` (array)
- `service_duration` (integer): Service duration in seconds.
- `service_ids` (array)
- `to_date` (string): Local end, YYYY-MM-DDThh:mm.

### `waitwhile_list_customers` (~214 tokens)

List customers

List customers (name, phone, e-mail, tags, last visit per location, created/updated). Cursor-paged, 20 per page by default; filter by location, external id or created/updated date. Contains personal data. GET /customers.

Input parameters:

- `desc` (boolean): Newest first.
- `external_id` (string)
- `from_date` (string): ISO 8601 date or date-time (e.g. 2026-10-01T00:00:00Z), or epoch milliseconds.
- `limit` (integer): Results per page, 1-100 (default 20).
- `location_id` (string): Only customers with visits at this location.
- `start_after` (string): Cursor: pass the previous reply's next_start_after to get the next page.
- `to_date` (string): ISO 8601 date or date-time (e.g. 2026-10-01T00:00:00Z), or epoch milliseconds.

### `waitwhile_search_customers` (~136 tokens)

Search customers

Search customers by a prefix match on name, phone, e-mail or customer id; optionally narrowed by location, visit state or tag. Page-numbered. Contains personal data. GET /customers/search.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 20).
- `location_id` (string)
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `q` (string, required): Prefix match on name, phone, e-mail or customer id.
- `state` (string)
- `tag` (string)

### `waitwhile_get_customer` (~48 tokens)

Get customer

One customer by id: contact details, tags, per-location state and last visit. Contains personal data. GET /customers/{customerId}.

Input parameters:

- `customer_id` (string, required): Customer id.

### `waitwhile_list_customer_notes` (~48 tokens)

List customer notes

The staff notes recorded on a customer (content, author, visit and location, timestamps). GET /customers/{customerId}/notes.

Input parameters:

- `customer_id` (string, required): Customer id.

### `waitwhile_list_services` (~147 tokens)

List services

List services (what customers book or queue for): name, duration, price, locations, resources and category structure. GET /services.

Input parameters:

- `external_id` (string)
- `is_category` (boolean): Only service categories (true) or only services (false).
- `limit` (integer): Results per page, 1-100 (default 20).
- `location_id` (array): Only items offered at these locations.
- `parent_id` (string): Only children of this category.
- `q` (string): Prefix match on name or display name.
- `start_after` (string): Cursor: pass the previous reply's next_start_after to get the next page.

### `waitwhile_get_service` (~32 tokens)

Get service

One service by id. GET /services/{serviceId}.

Input parameters:

- `service_id` (string, required): Service id.

### `waitwhile_list_resources` (~165 tokens)

List resources (staff, rooms, tables)

List resources — the people, rooms, tables or equipment that serve customers: name, locations, services, availability flag and category structure. GET /resources.

Input parameters:

- `email` (string): Only the resource with this e-mail.
- `external_id` (string)
- `is_category` (boolean): Only resource categories (true) or only resources (false).
- `limit` (integer): Results per page, 1-100 (default 20).
- `location_id` (array): Only items offered at these locations.
- `parent_id` (string): Only children of this category.
- `q` (string): Prefix match on name or display name.
- `start_after` (string): Cursor: pass the previous reply's next_start_after to get the next page.

### `waitwhile_get_resource` (~32 tokens)

Get resource

One resource by id. GET /resources/{resourceId}.

Input parameters:

- `resource_id` (string, required): Resource id.

### `waitwhile_resources_availability` (~82 tokens)

Resource availability

Working hours/availability of a location's resources on a date (e.g. who is working today). GET /resources/availability.

Input parameters:

- `date` (string): Date (yyyy-mm-dd) or ISO 8601 date-time; default today.
- `location_id` (string, required): Location id.
- `resource_ids` (array): Only these resources.

### `waitwhile_list_data_fields` (~125 tokens)

List data fields (intake form fields)

List the custom data fields (intake/booking form questions) with type, options and where they apply. Use the ids to read answers on visits. GET /data-fields.

Input parameters:

- `external_id` (string)
- `limit` (integer): Results per page, 1-100 (default 20).
- `location_id` (array): Only items offered at these locations.
- `q` (string): Prefix match on name or display name.
- `start_after` (string): Cursor: pass the previous reply's next_start_after to get the next page.

### `waitwhile_get_data_field` (~38 tokens)

Get data field

One data field by id. GET /data-fields/{dataFieldId}.

Input parameters:

- `data_field_id` (string, required): Data field id.

### `waitwhile_list_users` (~130 tokens)

List users (staff)

List the staff users of the account: name, e-mail, roles, locations. Password data and tokens are never returned. GET /users.

Input parameters:

- `external_id` (string)
- `limit` (integer): Results per page, 1-100 (default 20).
- `location_id` (array): Only users with access to these locations.
- `q` (string): Prefix match on name or e-mail.
- `role` (array): Only users with these roles.
- `start_after` (string): Cursor: pass the previous reply's next_start_after to get the next page.

### `waitwhile_list_messages` (~253 tokens)

List messages

List the SMS/e-mail messages Waitwhile sent to and received from customers: channel, recipient, body, delivery state (PENDING, BLOCKED, FAILED, DELIVERED, UNCONFIRMED, RECEIVED) and error. Filter by location, visit, customer, state or date. Contains personal data. This only reads; it cannot send. GET /messages.

Input parameters:

- `customer_id` (string)
- `desc` (boolean): Newest first.
- `external_customer_id` (string)
- `from_date` (string): ISO 8601 date or date-time (e.g. 2026-10-01T00:00:00Z), or epoch milliseconds.
- `limit` (integer): Results per page, 1-100 (default 20).
- `location_id` (string)
- `start_after` (string): Cursor: pass the previous reply's next_start_after to get the next page.
- `state` (string)
- `to_date` (string): ISO 8601 date or date-time (e.g. 2026-10-01T00:00:00Z), or epoch milliseconds.
- `visit_id` (string)

### `waitwhile_get_message` (~36 tokens)

Get message

One message by id. Contains personal data. GET /messages/{messageId}.

Input parameters:

- `message_id` (string, required): Message id.

### `waitwhile_visit_analytics` (~124 tokens)

Visit analytics

Aggregated visit statistics for a period: visits, waitlisted, bookings, served, no-shows, cancellations, wait and serve duration quantiles, and breakdowns by location, resource, service, party size, user, day of week and hour of day. GET /analytics/visits (JSON).

Input parameters:

- `from_date` (string): Period start (ISO 8601 or epoch ms).
- `location_id` (string): Only this location (default: all).
- `to_date` (string): Period end (ISO 8601 or epoch ms).

### `waitwhile_list_audit_entries` (~231 tokens)

List audit entries

The account's audit log: who changed what and when (visits, customers, locations, services, resources, users, messages). Filter by type, event, entity, location or date. GET /audit-entries.

Input parameters:

- `desc` (boolean): Newest first.
- `entity_id` (string): Id of the changed object.
- `event` (string): Audit event type.
- `from_date` (string): ISO 8601 date or date-time (e.g. 2026-10-01 or 2026-10-01T00:00:00Z).
- `limit` (integer): Results per page, 1-100 (default 20).
- `location_id` (string)
- `start_after` (string): Cursor: pass the previous reply's next_start_after to get the next page.
- `to_date` (string): ISO 8601 date or date-time (e.g. 2026-10-01 or 2026-10-01T00:00:00Z).
- `type` (string)

### `waitwhile_create_visit` (~355 tokens)

Add a customer to the waitlist or create a booking

WRITE: create ONE visit at a location. Without a date it adds the customer to the waitlist; with a local date-time (YYYY-MM-DDThh:mm) it creates a booking. Needs a location and at least a name, phone or e-mail. Not idempotent: calling it twice creates two visits. Visit notes are not supported here (the field is deprecated): use waitwhile_add_customer_note. By default the request asks Waitwhile to suppress the customer message; this may only stop the immediate confirmation, and scheduled reminders/follow-ups can still go out per the location's settings. With send_notifications=true Waitwhile may text/e-mail this ONE customer. POST /visits.

Input parameters:

- `date` (string): Booking start in the location's local time, YYYY-MM-DDThh:mm. Omit to join the waitlist.
- `duration` (integer): Booking duration in seconds.
- `email` (string): Customer e-mail.
- `first_name` (string)
- `last_name` (string)
- `location_id` (string, required): Location id (see waitwhile_list_locations).
- `name` (string): Customer name.
- `party_size` (integer)
- `phone` (string): Customer phone, E.164 (+16005551234).
- `resource_ids` (array): Preferred resources (staff, rooms).
- `send_notifications` (boolean): Default false: the request asks Waitwhile not to send the immediate confirmation/status message. This may not stop everything: scheduled reminders and follow-ups can still go out according to the loc…
- `service_ids` (array): Services the customer wants.

### `waitwhile_update_visit` (~276 tokens)

Update a visit (state, tags, time, party)

WRITE: change ONE visit — its state (e.g. WAITING to SERVING to COMPLETE, or BOOKED), add/remove tags (e.g. ARRIVED, CONFIRMED, NO-SHOW), booking date/duration or party size. Only the fields you pass change. By default the request asks Waitwhile to suppress the customer message; this may only stop the immediate status message, and scheduled reminders/follow-ups can still go out per the location's settings. With send_notifications=true Waitwhile may text/e-mail this ONE customer. Use waitwhile_cancel_visit to cancel. POST /visits/{visitId}.

Input parameters:

- `add_tags` (array): Tags to add.
- `date` (string): New booking start, local time YYYY-MM-DDThh:mm.
- `duration` (integer): New booking duration in seconds.
- `party_size` (integer)
- `remove_tags` (array): Tags to remove.
- `send_notifications` (boolean): Default false: the request asks Waitwhile not to send the immediate confirmation/status message. This may not stop everything: scheduled reminders and follow-ups can still go out according to the loc…
- `state` (string): New state.
- `visit_id` (string, required): Visit id.

### `waitwhile_cancel_visit` (~178 tokens)

Cancel a visit

WRITE: cancel ONE visit (a waitlist entry or booking). Waitwhile sets its state to COMPLETE and adds the CANCELLED tag; the visit is kept, not deleted. By default the request asks Waitwhile to suppress the customer message; this may only stop the immediate cancellation notice, and scheduled reminders/follow-ups can still go out per the location's settings. With send_notifications=true Waitwhile may text/e-mail this ONE customer. POST /visits/{visitId}/cancel.

Input parameters:

- `send_notifications` (boolean): Default false: the request asks Waitwhile not to send the immediate confirmation/status message. This may not stop everything: scheduled reminders and follow-ups can still go out according to the loc…
- `visit_id` (string, required): Visit id.

### `waitwhile_add_customer_note` (~88 tokens)

Add a customer note

WRITE: add one staff note to a customer's record (optionally tied to a visit and location). Adds only; nothing is edited or sent to the customer. POST /customers/{customerId}/notes.

Input parameters:

- `content` (string, required): The note text.
- `customer_id` (string, required): Customer id.
- `location_id` (string)
- `visit_id` (string)

## Diagnostics

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

## Score history

- 2026-10-17: 63
- 2026-10-16: 62
- 2026-10-15: 62
- 2026-10-14: 62
- 2026-10-13: 59
- 2026-10-12: 58

## Common questions

### What is the Waitwhile MCP by usefulapi server?

Waitwhile MCP by usefulapi is listed in the public MCP registry as io.usefulapi/waitwhile. Read Waitwhile visits, bookings, customers, services and analytics; add, update and cancel visits. This page covers its hosted endpoint (https://waitwhile.usefulapi.io/mcp).

### Is the Waitwhile MCP by usefulapi server safe to use?

Waitwhile 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 Waitwhile MCP by usefulapi server expose?

Waitwhile MCP by usefulapi exposes 29 tools: waitwhile_list_locations, waitwhile_get_location, waitwhile_list_location_status, waitwhile_get_location_status, waitwhile_list_visits, and 24 more. Their descriptions and schemas cost roughly 3,910 tokens of context every time the server is loaded.

### Does the Waitwhile MCP by usefulapi server require authentication?

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

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