# Zenbooker MCP by usefulapi (remote · zenbooker.usefulapi.io)

Read Zenbooker jobs, customers, invoices and timeslots; add customers and job notes.

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

## Components

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

## Channel facts

- Endpoint: `https://zenbooker.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.5.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-25.

- **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**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3378 tokens (~160/item across 21 items; 21 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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 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 Zenbooker MCP by usefulapi server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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

### 2026-10-24 (score 63, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] 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

### 2026-10-23 (score 63, +1)

- [functional] Server version: 1.0.1 → 1.1.0

### 2026-10-22 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.0.1

### 2026-10-21 (score 62)

First indexed and scored.

## MCP tools (21)

### `zenbooker_list_jobs` (~335 tokens)

List jobs

List jobs (booked appointments), by start time by default, with filters: customer id, assigned team member id, territory id, recurring booking id, status, canceled flag, creation time and scheduled start window. Returns { results, count, has_more, next_cursor }; pass next_cursor as cursor for the next page. GET /v1/jobs.

Input parameters:

- `assigned` (string): Only jobs assigned to this team member (service provider) id.
- `canceled` (boolean): true = only canceled jobs, false = only jobs that are not canceled.
- `created_after` (string): Only items created after this ISO 8601 date-time.
- `created_before` (string): Only items created before this ISO 8601 date-time.
- `cursor` (integer): Where to start in the list (default 0). Pass the previous reply's next_cursor.
- `customer` (string): Only jobs of this customer id.
- `limit` (integer): Results per page, 1-100 (default 20).
- `recurring_booking` (string): Only jobs that belong to this recurring booking id.
- `sort_by` (string): Sort field (default start_time).
- `sort_order` (string): Sort order (default ascending).
- `start_date_max` (string): Only jobs scheduled to start on or before this ISO 8601 date-time.
- `start_date_min` (string): Only jobs scheduled to start on or after this ISO 8601 date-time.
- `status` (string): Only jobs with this status.
- `territory` (string): Only jobs in this service territory id.

### `zenbooker_get_job` (~67 tokens)

Get job

One job by id: appointment time, status, customer, service address, services and fields, assigned providers, notes and invoice summary. GET /v1/jobs/{id}.

Input parameters:

- `job_id` (string, required): The Zenbooker id (the id field of a list result).

### `zenbooker_add_job_note` (~87 tokens)

Add a note to a job

WRITE: add an internal note (text) to a job. Notes are appended, never replaced, and cannot be deleted through this server, so check the job first. POST /v1/jobs/{id}/notes.

Input parameters:

- `job_id` (string, required): The Zenbooker id (the id field of a list result).
- `text` (string, required): The note text.

### `zenbooker_list_recurring_bookings` (~223 tokens)

List recurring bookings

List recurring bookings (repeating job series), by status (active or canceled), customer id, assigned team member id, territory id or creation time. Max 40 per page. Returns { results, count, has_more, next_cursor }. GET /v1/recurring.

Input parameters:

- `assigned` (string): Only recurring bookings assigned to this team member id.
- `created_after` (string): Only items created after this ISO 8601 date-time.
- `created_before` (string): Only items created before this ISO 8601 date-time.
- `cursor` (integer): Where to start in the list (default 0). Pass the previous reply's next_cursor.
- `customer` (string): Only recurring bookings of this customer id.
- `limit` (integer): Results per page, 1-40 (default 20).
- `sort_order` (string): Sort order (default ascending).
- `status` (string): Only recurring bookings with this status.
- `territory` (string): Only recurring bookings in this service territory id.

### `zenbooker_get_recurring_booking` (~73 tokens)

Get recurring booking

One recurring booking by id: first job date, job count, time slot, status, territory, service, pricing and its job ids. GET /v1/recurring/{id}.

Input parameters:

- `recurring_booking_id` (string, required): The Zenbooker id (the id field of a list result).

### `zenbooker_list_customers` (~231 tokens)

List customers

List or search customers by name, email or phone, by creation time, or by default address near a place (location + radius in miles). Returns { results, count, has_more, next_cursor }. GET /v1/customers.

Input parameters:

- `created_after` (string): Only items created after this ISO 8601 date-time.
- `created_before` (string): Only items created before this ISO 8601 date-time.
- `cursor` (integer): Where to start in the list (default 0). Pass the previous reply's next_cursor.
- `email` (string): Search by customer email.
- `limit` (integer): Results per page, 1-100 (default 20).
- `location` (string): A place or address; finds customers whose default address is near it (geocoded by Zenbooker).
- `name` (string): Search by customer name.
- `phone` (string): Search by phone number.
- `radius` (integer): Search radius in miles, used with location.
- `sort_order` (string): Sort order (default ascending).

### `zenbooker_get_customer` (~63 tokens)

Get customer

One customer by id: contact details, notes, addresses, job and recurring booking ids and linked Stripe customer. GET /v1/customers/{id}.

Input parameters:

- `customer_id` (string, required): The Zenbooker id (the id field of a list result).

### `zenbooker_create_customer` (~94 tokens)

Create customer

WRITE: create a new customer record in Zenbooker (name required; phone and email optional). It does not look for an existing customer, so search with zenbooker_list_customers first to avoid duplicates. POST /v1/customers.

Input parameters:

- `email` (string): The customer's email address.
- `name` (string, required): The customer's name.
- `phone` (string): The customer's default phone number.

### `zenbooker_list_invoices` (~227 tokens)

List invoices

List invoices, optionally by status (draft, unpaid, partial_paid, paid, void), customer id, territory id or creation time. Each invoice has line items, totals, amount paid and due and its transactions. Returns { results, count, has_more, next_cursor }. GET /v1/invoices.

Input parameters:

- `created_after` (string): Only items created after this ISO 8601 date-time.
- `created_before` (string): Only items created before this ISO 8601 date-time.
- `cursor` (integer): Where to start in the list (default 0). Pass the previous reply's next_cursor.
- `customer` (string): Only invoices of this customer id.
- `limit` (integer): Results per page, 1-100 (default 20).
- `sort_by` (string): Sort field (default creation_date).
- `sort_order` (string): Sort order (default ascending).
- `status` (string): Only invoices in this status (default: any status).
- `territory` (string): Only invoices in this service territory id.

### `zenbooker_get_invoice` (~66 tokens)

Get invoice

One invoice by id: recipient, line items, discounts, tax, totals, amount paid and due, status and transactions. GET /v1/invoices/{id}.

Input parameters:

- `invoice_id` (string, required): The Zenbooker id (the id field of a list result).

### `zenbooker_list_transactions` (~283 tokens)

List transactions

List payment transactions, optionally by type (stripe_payment, external_transaction), payment method, status (succeeded, failed, voided), customer id, territory id, creation time or payment date. Returns { results, count, has_more, next_cursor }. GET /v1/transactions.

Input parameters:

- `created_after` (string): Only items created after this ISO 8601 date-time.
- `created_before` (string): Only items created before this ISO 8601 date-time.
- `cursor` (integer): Where to start in the list (default 0). Pass the previous reply's next_cursor.
- `customer` (string): Only transactions of this customer id.
- `limit` (integer): Results per page, 1-100 (default 20).
- `payment_method` (string): Only transactions paid by this method.
- `sort_by` (string): Sort field (default creation_date).
- `sort_order` (string): Sort order (default ascending).
- `status` (string): Only transactions in this status.
- `territory` (string): Only transactions in this service territory id.
- `transaction_date_after` (string): Only transactions dated after this ISO 8601 date-time.
- `transaction_date_before` (string): Only transactions dated before this ISO 8601 date-time.
- `type` (string): Only transactions of this type.

### `zenbooker_get_transaction` (~63 tokens)

Get transaction

One payment transaction by id: status, type, method, amount, invoice and customer ids, Stripe references. GET /v1/transactions/{id}.

Input parameters:

- `transaction_id` (string, required): The Zenbooker id (the id field of a list result).

### `zenbooker_list_services` (~164 tokens)

List services

List the services a business offers, with pricing method, base price and duration, option sections and recurring frequencies. GET /v1/services.

Input parameters:

- `category_id` (string): Only services in this category id.
- `created_after` (string): Only items created after this ISO 8601 date-time.
- `created_before` (string): Only items created before this ISO 8601 date-time.
- `cursor` (integer): Where to start in the list (default 0). Pass the previous reply's next_cursor.
- `is_visible` (boolean): true = only services visible in online booking.
- `limit` (integer): Results per page, 1-100 (default 20).
- `sort_order` (string): Sort order (default ascending).

### `zenbooker_get_service` (~55 tokens)

Get service

One service by id: pricing, duration, option sections and their options. GET /v1/services/{id}.

Input parameters:

- `service_id` (string, required): The Zenbooker id (the id field of a list result).

### `zenbooker_list_territories` (~185 tokens)

List service territories

List the service territories (areas a business serves) with timezone, service area, providers and operating hours. Use the ids to filter jobs and invoices or to look up time slots. GET /v1/territories.

Input parameters:

- `created_after` (string): Only items created after this ISO 8601 date-time.
- `created_before` (string): Only items created before this ISO 8601 date-time.
- `cursor` (integer): Where to start in the list (default 0). Pass the previous reply's next_cursor.
- `enabled` (boolean): true = only active territories, false = only deactivated ones (default both).
- `limit` (integer): Results per page, 1-100 (default 20).
- `name` (string): Search by territory name.
- `sort_order` (string): Sort order (default ascending).

### `zenbooker_get_territory` (~50 tokens)

Get service territory

One service territory by id. GET /v1/territories/{id}.

Input parameters:

- `territory_id` (string, required): The Zenbooker id (the id field of a list result).

### `zenbooker_list_team_members` (~215 tokens)

List team members

List team members (staff and service providers) with role, status, assigned territories, skill tags and work hours. Use the ids to filter jobs by assigned provider. GET /v1/team_members.

Input parameters:

- `created_after` (string): Only items created after this ISO 8601 date-time.
- `created_before` (string): Only items created before this ISO 8601 date-time.
- `cursor` (integer): Where to start in the list (default 0). Pass the previous reply's next_cursor.
- `deactivated` (boolean): true = only deactivated team members, false = only active ones.
- `email` (string): Find a team member by email address.
- `limit` (integer): Results per page, 1-100 (default 20).
- `service_provider` (boolean): true = only team members who can be assigned jobs.
- `sort_order` (string): Sort order (default ascending).
- `territory` (string): Only providers assigned to this service territory id.

### `zenbooker_get_team_member` (~64 tokens)

Get team member

One team member by id: contact details, role, status, territories, skill tags and work hours. GET /v1/team_members/{id}.

Input parameters:

- `team_member_id` (string, required): The Zenbooker id (the id field of a list result).

### `zenbooker_list_service_requests` (~193 tokens)

List service requests

List incoming service requests (booking requests and quote requests) with status, customer, territory, duration, requested dates, services and pricing. Returns { results, count, has_more, next_cursor }. GET /v1/service_requests.

Input parameters:

- `created_after` (string): Only items created after this ISO 8601 date-time.
- `created_before` (string): Only items created before this ISO 8601 date-time.
- `cursor` (integer): Where to start in the list (default 0). Pass the previous reply's next_cursor.
- `customer` (string): Only requests of this customer id.
- `limit` (integer): Results per page, 1-100 (default 20).
- `request_type` (string): Only this kind of request.
- `sort_order` (string): Sort order (default ascending).
- `territory` (string): Only requests in this service territory id.

### `zenbooker_check_service_area` (~133 tokens)

Check service area

Check whether a location is inside the business's service area: returns in_service_area, the matching territory and other territories that serve it (or the closest territory when it is outside every area). Give a postal code, an address, or lat + lng. GET /v1/scheduling/service_area_check.

Input parameters:

- `address` (string): Street address (needed only when there is no postal code or lat/lng).
- `lat` (number): Latitude; send together with lng.
- `lng` (number): Longitude; send together with lat.
- `postal_code` (string): ZIP or postal code.

### `zenbooker_get_timeslots` (~243 tokens)

Get available time slots

Available booking time slots for a service territory, grouped by day (days[].timeslots[] with start, end and id). Needs the territory id (zenbooker_list_territories or zenbooker_check_service_area) and the service duration in minutes. GET /v1/scheduling/timeslots.

Input parameters:

- `date` (string): First day to check, yyyy-mm-dd (default today).
- `days` (integer): How many days to return (default 7, max 60).
- `duration` (integer, required): Service length in minutes (required).
- `lat` (number): Customer latitude (for drive-time aware availability); send with lng.
- `lng` (number): Customer longitude; send with lat.
- `min_providers_needed` (integer): Minimum number of providers a slot needs (default 1).
- `required_skills` (string): Comma-separated skill tag ids a provider must have.
- `service_providers` (string): Comma-separated team member ids to restrict slots to.
- `territory` (string, required): The service territory id (required).
- `timeslot_template` (string): A timeslot template id.

## Diagnostics

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

## Score history

- 2026-10-25: 64
- 2026-10-24: 63
- 2026-10-23: 63
- 2026-10-22: 62
- 2026-10-21: 62

## Common questions

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

Zenbooker MCP by usefulapi is listed in the public MCP registry as io.usefulapi/zenbooker. Read Zenbooker jobs, customers, invoices and timeslots; add customers and job notes. This page covers its hosted endpoint (https://zenbooker.usefulapi.io/mcp).

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

Zenbooker MCP by usefulapi scores 64 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 Zenbooker MCP by usefulapi server expose?

Zenbooker MCP by usefulapi exposes 21 tools: zenbooker_list_jobs, zenbooker_get_job, zenbooker_add_job_note, zenbooker_list_recurring_bookings, zenbooker_get_recurring_booking, and 16 more. Their descriptions and schemas cost roughly 3,114 tokens of context every time the server is loaded.

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

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

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

## Links

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