Zenbooker MCP by usefulapi
REMOTE · ZENBOOKER.USEFULAPI.IO
Read Zenbooker jobs, customers, invoices and timeslots; add customers and job notes.
Available components
Last scanned (4 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 25 Oct 2026.
Category CRM and Sales
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 Security78
- 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 enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. 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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 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
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.
- 25 Oct 26 +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.
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 23 Oct 26 +1
- Server version: 1.0.1 → 1.1.0 functional
- 22 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.0.1 functional
- 21 Oct 26 62
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 25 Oct 2026 · Probed https://zenbooker.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 zenbooker.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 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 | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://zenbooker.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://zenbooker.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://zenbooker.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://zenbooker.usefulapi.io/mcp |
| Authorisation server | https://zenbooker.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://zenbooker.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/zenbooker/ |
| http (plaintext) | http://zenbooker.usefulapi.io/mcp | Inconclusive | 302 | http://zenbooker.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 →
zenbooker_add_job_note Add a note to a job ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The Zenbooker id (the id field of a list result). |
| text | string | yes | The note text. |
No output schema declared.
No examples provided.
zenbooker_check_service_area Check service area ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
zenbooker_create_customer Create customer ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The customer's email address. | |
| name | string | yes | The customer's name. |
| phone | string | – | The customer's default phone number. |
No output schema declared.
No examples provided.
zenbooker_get_customer Get customer ~63
One customer by id: contact details, notes, addresses, job and recurring booking ids and linked Stripe customer. GET /v1/customers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The Zenbooker id (the id field of a list result). |
No output schema declared.
No examples provided.
zenbooker_get_invoice Get invoice ~66
One invoice by id: recipient, line items, discounts, tax, totals, amount paid and due, status and transactions. GET /v1/invoices/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | The Zenbooker id (the id field of a list result). |
No output schema declared.
No examples provided.
zenbooker_get_job Get job ~67
One job by id: appointment time, status, customer, service address, services and fields, assigned providers, notes and invoice summary. GET /v1/jobs/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The Zenbooker id (the id field of a list result). |
No output schema declared.
No examples provided.
zenbooker_get_recurring_booking Get recurring booking ~73
One recurring booking by id: first job date, job count, time slot, status, territory, service, pricing and its job ids. GET /v1/recurring/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| recurring_booking_id | string | yes | The Zenbooker id (the id field of a list result). |
No output schema declared.
No examples provided.
zenbooker_get_service Get service ~55
One service by id: pricing, duration, option sections and their options. GET /v1/services/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| service_id | string | yes | The Zenbooker id (the id field of a list result). |
No output schema declared.
No examples provided.
zenbooker_get_team_member Get team member ~64
One team member by id: contact details, role, status, territories, skill tags and work hours. GET /v1/team_members/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| team_member_id | string | yes | The Zenbooker id (the id field of a list result). |
No output schema declared.
No examples provided.
zenbooker_get_territory Get service territory ~50
One service territory by id. GET /v1/territories/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| territory_id | string | yes | The Zenbooker id (the id field of a list result). |
No output schema declared.
No examples provided.
zenbooker_get_timeslots Get available time slots ~243
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | First day to check, yyyy-mm-dd (default today). |
| days | integer | – | How many days to return (default 7, max 60). |
| duration | integer | yes | 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 | yes | The service territory id (required). |
| timeslot_template | string | – | A timeslot template id. |
No output schema declared.
No examples provided.
zenbooker_get_transaction Get transaction ~63
One payment transaction by id: status, type, method, amount, invoice and customer ids, Stripe references. GET /v1/transactions/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| transaction_id | string | yes | The Zenbooker id (the id field of a list result). |
No output schema declared.
No examples provided.
zenbooker_list_customers List customers ~231
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| 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). |
No output schema declared.
No examples provided.
zenbooker_list_invoices List invoices ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
zenbooker_list_jobs List jobs ~335
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
zenbooker_list_recurring_bookings List recurring bookings ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
zenbooker_list_service_requests List service requests ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
zenbooker_list_services List services ~164
List the services a business offers, with pricing method, base price and duration, option sections and recurring frequencies. GET /v1/services.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
zenbooker_list_team_members List team members ~215
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| 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. |
No output schema declared.
No examples provided.
zenbooker_list_territories List service territories ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
zenbooker_list_transactions List transactions ~283
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · zenbooker.usefulapi.io
claude mcp add --transport http io-usefulapi-zenbooker 'https://zenbooker.usefulapi.io/mcp'
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.