MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

Waitwhile MCP by usefulapi

Claim this listing

io.usefulapi/waitwhile

usefulapi.ioVerified

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

Data & AnalyticsIs Waitwhile MCP by usefulapi down?Alternatives

13 of 22 checks passed

  • Handshake
  • Tools listed
  • Updated recently

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Connect to server
Median latency
53 ms
Uptime, 30 days
Not measured
Last checked

Measurement details

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 53 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name waitwhile-mcp.

  • Pass
    Lists tools

    tools/list returned 29 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 53 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 53 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Fail
    Parameters documented

    109 of 142 parameters have a description (77%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-10T23:33:58.259115Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Tools

  • waitwhile_add_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.

    Measured

  • waitwhile_cancel_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.

    Measured

  • waitwhile_create_visit

    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.

    Measured

  • waitwhile_first_available_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.

    Measured

  • waitwhile_get_customer

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

    Measured

  • waitwhile_get_data_field

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

    Measured

  • waitwhile_get_location

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

    Measured

  • waitwhile_get_location_status

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

    Measured

  • waitwhile_get_message

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

    Measured

  • waitwhile_get_resource

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

    Measured

  • waitwhile_get_service

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

    Measured

  • waitwhile_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}.

    Measured

  • waitwhile_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.

    Measured

  • waitwhile_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.

    Measured

  • waitwhile_list_customer_notes

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

    Measured

  • waitwhile_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.

    Measured

  • waitwhile_list_data_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.

    Measured

  • waitwhile_list_location_status

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

    Measured

  • waitwhile_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.

    Measured

  • waitwhile_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.

    Measured

  • waitwhile_list_resources

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

    Measured

  • waitwhile_list_services

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

    Measured

  • waitwhile_list_users

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

    Measured

  • waitwhile_list_visits

    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.

    Measured

  • waitwhile_resources_availability

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

    Measured

  • waitwhile_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.

    Measured

  • waitwhile_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.

    Measured

  • waitwhile_update_visit

    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}.

    Measured

  • waitwhile_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).

    Measured

Probe history

  • ok53 ms29 tools

Status and uptime

Add badge to your README

The image links back to this page. It shows checks passed, or uptime, and the colour follows the latest status. Responses are cached for 5 to 15 minutes.

MCP Heartbeat badge

Markdown

[![MCP Heartbeat](https://mcpheartbeat.com/badge/io.usefulapi/waitwhile.svg)](https://mcpheartbeat.com/s/io.usefulapi/waitwhile)

HTML

<a href="https://mcpheartbeat.com/s/io.usefulapi/waitwhile"><img alt="MCP Heartbeat" src="https://mcpheartbeat.com/badge/io.usefulapi/waitwhile.svg"></a>

Uptime markdown

[![MCP Heartbeat uptime](https://mcpheartbeat.com/badge/io.usefulapi/waitwhile.svg?kind=uptime)](https://mcpheartbeat.com/s/io.usefulapi/waitwhile)

Served from https://mcpheartbeat.com.

Related servers

All alternatives

Same function and industry, ranked by checks passed then median latency.

Connect to this server

Claude Code

claude mcp add --transport http waitwhile-mcp-by-usefulapi https://waitwhile.usefulapi.io/mcp

Cursor .cursor/mcp.json

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

VS Code .vscode/mcp.json

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