Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Booqable MCP by usefulapi

REMOTE · BOOQABLE.USEFULAPI.IO

Browse rental orders, customers, products and availability, and create bookings in Booqable.

0 this week 18 Trust /100

Last scanned (17 hours ago)

Scores higher than 3% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Nov 26 −61
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 31 Oct 26 +3
    • Authorization: partial → pass ▲ security
    • MCP protocol: fail → pass ▲ functional
    • New prompt “check_if_a_product_is_available_for_a_date” functional
    • New prompt “check_invoices_quotes_and_payments” functional
    • New prompt “create_a_rental_order_or_change_an_existing_one” functional
    • New prompt “look_up_add_or_update_a_customer” functional
    • New prompt “read_or_add_internal_notes_on_a_record” functional
    • New prompt “review_rental_orders_by_status_or_rental_period” functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
    • Server version: 1.31.0 → 1.33.0 functional
    • Server version: 1.30.0 → 1.31.0 functional
    • Server version: 1.29.2 → 1.30.0 functional
  • 30 Oct 26 +1
    • Stability: 0.97 → pass security
    • Server version: 1.29.1 → 1.29.2 functional
    • Server version: 1.29.0 → 1.29.1 functional
  • 29 Oct 26 0
    • Server version: 1.28.0 → 1.29.0 functional
    • Server version: 1.27.0 → 1.28.0 functional
  • 28 Oct 26 +1
    • Server version: 1.25.0 → 1.27.0 functional
  • 27 Oct 26 0
    • Server version: 1.24.0 → 1.25.0 functional
  • 26 Oct 26 +1

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

Diagnostics

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 21 Nov 2026 · Probed https://booqable.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 11 Nov 2026 9 Feb 2027 ECDSA 256 ECDSA-SHA256 93e2fea3bbc31354138c8a47c5e87592
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 booqable.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
usefulapi.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://booqable.usefulapi.io/mcp Redirected 302 https://usefulapi.io/booqable/
http (plaintext) http://booqable.usefulapi.io/mcp Inconclusive 302 http://booqable.usefulapi.io/mcp
MCP tools · 21 exposed · ~3,563 tokens

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 →

Tool Tokens
booqable_book_product ~176

Add a quantity of a product to an order, allocating inventory (creates a planning and a line). By default adds to an existing planning for the same product if there is one. Booqable: POST /api/4/order_fulfillments with a book_product action.

NameTypeReqDescription
confirm_shortageboolean–true to accept a shortage warning when booking on a reserved or started order.
modestring–infer_planning (default): reuse the product's planning if any; create_new: always a new line; update_existing: add to planning_id.
order_idstringyesThe order id (UUID).
planning_idstring–Required when mode is update_existing.
product_idstringyesThe product id (UUID).
quantityintegeryesUnits to book.

No output schema declared.

No examples provided.

booqable_check_inventory_availability ~213

How many units of one or more products can be booked for an exact period at a location. Returns `available` and `plannable` (plannable can exceed available when shortage is allowed). Get location ids from booqable_list_locations. Booqable: GET /api/4/inventory_availabilities.

NameTypeReqDescription
fromstringyesPeriod start, ISO 8601 at the company's local time written as UTC, e.g. 2026-07-01T10:00:00Z means 10:00 at the shop. Do not convert to real UTC.
location_idstringyesThe pickup location id.
product_idsarrayyesProduct ids to check.
tillstringyesPeriod end, ISO 8601 at the company's local time written as UTC, e.g. 2026-07-01T10:00:00Z means 10:00 at the shop. Do not convert to real UTC.

No output schema declared.

No examples provided.

booqable_create_customer ~111

Create a new customer. Booqable: POST /api/4/customers.

NameTypeReqDescription
discount_percentagenumber–Default discount % applied to this customer's new orders.
emailstring–Email address used for communication.
email_marketing_consentedboolean–Whether the customer consented to email marketing.
legal_typestring–person or commercial.
namestringyesPerson or company name.
tag_listarray–Tags (case-insensitive).

No output schema declared.

No examples provided.

booqable_create_note ~77

Attach an internal note to a customer, order, product or other record. Booqable: POST /api/4/notes.

NameTypeReqDescription
bodystringyesThe note text.
owner_idstringyesThe id of the record the note is about.
owner_typestringyesThe owner's resource type.

No output schema declared.

No examples provided.

booqable_create_order ~252

Create an EMPTY order for a rental period (status new or draft). Then add products with booqable_book_product and reserve it with booqable_transition_order_status. Locations default to the first active location. Booqable: POST /api/4/orders.

NameTypeReqDescription
customer_idstring–The customer this order is for.
start_location_idstring–Pickup location id.
starts_atstringyesRental start, ISO 8601 at the company's local time written as UTC, e.g. 2026-07-01T10:00:00Z means 10:00 at the shop. Do not convert to real UTC.
statusstring–Initial status. Default new (visible only to its creator); draft is visible but reserves nothing.
stop_location_idstring–Return location id.
stops_atstringyesRental end, ISO 8601 at the company's local time written as UTC, e.g. 2026-07-01T10:00:00Z means 10:00 at the shop. Do not convert to real UTC.
tag_listarray–Tags (case-insensitive).

No output schema declared.

No examples provided.

booqable_get_availability_calendar ~129

Day-by-day availability for one product over a month: status (available/partial/unavailable) and bookable quantity per day. Booqable: GET /api/4/availabilities with subject_type=item.

NameTypeReqDescription
location_idstring–Location id to check at.
monthintegeryesCalendar month, 1-12.
product_idstringyesThe product id (UUID).
quantityinteger–Units needed; sets the threshold for available vs partial.
yearintegeryesCalendar year, e.g. 2026.

No output schema declared.

No examples provided.

booqable_get_company ~55

Fetch the Booqable account this token belongs to — name, currency, default timezone, address. A cheap way to confirm the slug and token work. Booqable: GET /api/4/companies/current.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

booqable_get_customer ~88

Fetch one customer with order count, revenue and balance due, sideloading their properties (addresses, phone, custom fields) by default. Booqable: GET /api/4/customers/{id}.

NameTypeReqDescription
customer_idstringyesThe customer id (UUID).
includestring–Comma-separated relationships to sideload, e.g. properties,tax_region.

No output schema declared.

No examples provided.

booqable_get_order ~108

Fetch one order with its totals, deposit and payment state, sideloading the customer and order lines by default (override with include, e.g. customer,lines,payments,documents,notes). Booqable: GET /api/4/orders/{id}.

NameTypeReqDescription
includestring–Comma-separated relationships to sideload, e.g. customer,lines,payments,documents,notes,start_location.
order_idstringyesThe order id (UUID).

No output schema declared.

No examples provided.

booqable_list_customers ~179

List customers, optionally searched by name/email or filtered by email, tag or archived state. Booqable: GET /api/4/customers.

NameTypeReqDescription
archivedboolean–true = only archived, false = only active.
emailstring–Only the customer with exactly this email.
includestring–Comma-separated relationships to sideload, e.g. properties.
pageinteger–Page number (1-based). Default 1.
page_sizeinteger–Results per page, 1-100 (Booqable default 25).
qstring–Free-text search over customers.
sortstring–Sort, comma-separated attributes; prefix with - for descending, e.g. -created_at.
tagstring–Only customers carrying this tag.

No output schema declared.

No examples provided.

booqable_list_documents ~197

List invoices, quotes and contracts, with totals and payment status. Filter by type, order, customer or status. Booqable: GET /api/4/documents.

NameTypeReqDescription
customer_idstring–Only documents for this customer.
document_typestring–Only this document type.
includestring–Comma-separated relationships to sideload, e.g. customer,order.
order_idstring–Only documents for this order.
pageinteger–Page number (1-based). Default 1.
page_sizeinteger–Results per page, 1-100 (Booqable default 25).
qstring–Free-text search.
sortstring–Sort, comma-separated attributes; prefix with - for descending, e.g. -created_at.
statusstring–Only documents in this status (values depend on document type).

No output schema declared.

No examples provided.

booqable_list_locations ~107

List pickup/return locations (warehouses, stores) with address and pickup/delivery capability. Location ids are needed for availability checks and orders. Booqable: GET /api/4/locations.

NameTypeReqDescription
archivedboolean–true = only archived, false = only active.
pageinteger–Page number (1-based). Default 1.
page_sizeinteger–Results per page, 1-100 (Booqable default 25).

No output schema declared.

No examples provided.

booqable_list_notes ~106

List internal notes attached to a customer, order, product or other record. Booqable: GET /api/4/notes.

NameTypeReqDescription
owner_idstringyesThe id of the record the notes are about.
owner_typestring–The owner's resource type.
pageinteger–Page number (1-based). Default 1.
page_sizeinteger–Results per page, 1-100 (Booqable default 25).

No output schema declared.

No examples provided.

booqable_list_orders ~313

List rental orders. Filter by free-text search (order number, customer name/email/address, tags, custom fields), status, payment status, customer, or rental-period range. Booqable: GET /api/4/orders.

NameTypeReqDescription
customer_idstring–Only orders for this customer id.
includestring–Comma-separated relationships to sideload, e.g. customer,start_location,stop_location.
pageinteger–Page number (1-based). Default 1.
page_sizeinteger–Results per page, 1-100 (Booqable default 25).
payment_statusstring–Only orders with this payment status.
qstring–Search: order number (exact), customer name, e-mail, address, tags, custom field values.
sortstring–Sort, comma-separated attributes; prefix with - for descending, e.g. -created_at.
starts_at_gtestring–Rental starts at or after this datetime (ISO 8601).
starts_at_ltestring–Rental starts at or before this datetime (ISO 8601).
statusstring–Only orders with this simplified status.
stops_at_gtestring–Rental ends at or after this datetime (ISO 8601).
stops_at_ltestring–Rental ends at or before this datetime (ISO 8601).
tagstring–Only orders carrying this tag.

No output schema declared.

No examples provided.

booqable_list_payments ~186

List payments (charges, authorizations and refunds) with amount, deposit, currency, provider and status. Filter by order, customer or payment type. Read only — this server never moves money. Booqable: GET /api/4/payments.

NameTypeReqDescription
customer_idstring–Only payments for this customer.
includestring–Comma-separated relationships to sideload, e.g. order,payment_method.
order_idstring–Only payments for this order.
pageinteger–Page number (1-based). Default 1.
page_sizeinteger–Results per page, 1-100 (Booqable default 25).
sortstring–Sort, comma-separated attributes; prefix with - for descending, e.g. -created_at.
typestring–Only this payment type.

No output schema declared.

No examples provided.

booqable_list_plannings ~278

List plannings — which product is booked on which order, how many, when, and how many are started (out) or stopped (returned). Filter by order, product, or reservation window. Booqable: GET /api/4/plannings.

NameTypeReqDescription
includestring–Comma-separated relationships to sideload, e.g. item,order,order.customer.
order_idstring–Only plannings on this order.
pageinteger–Page number (1-based). Default 1.
page_sizeinteger–Results per page, 1-100 (Booqable default 25).
product_idstring–Only plannings for this product or bundle (item_id).
sortstring–Sort, comma-separated attributes; prefix with - for descending, e.g. -created_at.
starts_at_gtestring–Planned start at or after this datetime (ISO 8601).
starts_at_ltestring–Planned start at or before this datetime (ISO 8601).
stops_at_gtestring–Planned end at or after this datetime (ISO 8601).
stops_at_ltestring–Planned end at or before this datetime (ISO 8601).

No output schema declared.

No examples provided.

booqable_list_product_groups ~196

List product groups — the catalogue entries (name, SKU, product type, tracking type, pricing). A group holds one or more bookable products (variations). Booqable: GET /api/4/product_groups.

NameTypeReqDescription
archivedboolean–true = only archived, false = only active.
includestring–Comma-separated relationships to sideload, e.g. products,photo.
pageinteger–Page number (1-based). Default 1.
page_sizeinteger–Results per page, 1-100 (Booqable default 25).
product_typestring–Only this product type.
qstring–Free-text search over name/SKU.
sortstring–Sort, comma-separated attributes; prefix with - for descending, e.g. -created_at.
tagstring–Only groups carrying this tag.

No output schema declared.

No examples provided.

booqable_list_products ~186

List bookable products (the variations inside product groups). Use a product id for availability checks and booking. Booqable: GET /api/4/products.

NameTypeReqDescription
archivedboolean–true = only archived, false = only active.
includestring–Comma-separated relationships to sideload, e.g. product_group,photo.
pageinteger–Page number (1-based). Default 1.
page_sizeinteger–Results per page, 1-100 (Booqable default 25).
product_group_idstring–Only products in this product group.
product_typestring–Only this product type.
qstring–Free-text search over name/SKU.
sortstring–Sort, comma-separated attributes; prefix with - for descending, e.g. -created_at.

No output schema declared.

No examples provided.

booqable_transition_order_status ~187

Move an order between statuses: new→draft, draft→reserved (reserves the items and assigns an order number), stopped→archived, or back to an earlier status with revert: true. Canceling is deliberately NOT offered (Booqable cannot un-cancel). started/stopped are reached by picking up/returning items, so they are only valid here with revert: true. Booqable: POST /api/4/order_status_transitions.

NameTypeReqDescription
confirm_shortageboolean–true to accept a shortage warning when reserving.
order_idstringyesThe order id (UUID).
revertboolean–true when going back to an earlier status (required for started/stopped).
transition_fromstringyesThe order's CURRENT status (Booqable checks it).
transition_tostringyesThe new status.

No output schema declared.

No examples provided.

booqable_update_customer ~146

Update a customer's name, email, legal type, tags, default discount or marketing consent. Only the fields you pass change. Booqable: PUT /api/4/customers/{id}.

NameTypeReqDescription
customer_idstringyesThe customer id (UUID).
discount_percentagenumber–Default discount % applied to this customer's new orders.
emailstring–Email address used for communication.
email_marketing_consentedboolean–Whether the customer consented to email marketing.
legal_typestring–person or commercial.
namestring–Person or company name.
tag_listarray–Tags (case-insensitive).

No output schema declared.

No examples provided.

booqable_update_order ~273

Change an order's rental period, customer, locations or tags. Moving dates can cause a shortage: the call then fails with the shortage details, and a shortage *warning* can be accepted by retrying with confirm_shortage: true. Booqable: PUT /api/4/orders/{id}.

NameTypeReqDescription
confirm_shortageboolean–true to proceed despite a shortage warning.
customer_idstring–Assign this customer (re-applies their discount, deposit and tax region).
order_idstringyesThe order id (UUID).
start_location_idstring–Pickup location id.
starts_atstring–New rental start, ISO 8601 at the company's local time written as UTC, e.g. 2026-07-01T10:00:00Z means 10:00 at the shop. Do not convert to real UTC.
stop_location_idstring–Return location id.
stops_atstring–New rental end, ISO 8601 at the company's local time written as UTC, e.g. 2026-07-01T10:00:00Z means 10:00 at the shop. Do not convert to real UTC.
tag_listarray–Replace the tag list.

No output schema declared.

No examples provided.

Install

How do I install the Booqable MCP by usefulapi server?

Booqable MCP by usefulapi is a hosted endpoint at https://booqable.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 · booqable.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-booqable 'https://booqable.usefulapi.io/mcp'
Common questions

What is the Booqable MCP by usefulapi server?

Booqable MCP by usefulapi is listed in the public MCP registry as io.usefulapi/booqable. Browse rental orders, customers, products and availability, and create bookings in Booqable. This page covers its hosted endpoint (https://booqable.usefulapi.io/mcp).

Is the Booqable MCP by usefulapi server safe to use?

Booqable MCP by usefulapi scores 18 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 Booqable MCP by usefulapi server expose?

Booqable MCP by usefulapi exposes 21 tools: booqable_get_company, booqable_list_orders, booqable_get_order, booqable_list_customers, booqable_get_customer, and 16 more. Their descriptions and schemas cost roughly 3,563 tokens of context every time the server is loaded.

Does the Booqable MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Booqable MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Booqable MCP by usefulapi server still maintained?

Booqable MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Booqable MCP by usefulapi server?

VerifyMCP ran 4 checks on Booqable MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Booqable MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.