WuBook MCP by usefulapi
REMOTE · WUBOOK.USEFULAPI.IO
Read WuBook ZaK rooms, availability and reservations; manage inventory and guest check-in.
Available components
Last scanned (18 minutes ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 Nov 2026.
Category E-commerce
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 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.
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 →
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
- 1 Nov 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.10 → 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 “change_prices_or_close_dates_for_sale” functional
- New prompt “check_availability_before_taking_a_booking” functional
- New prompt “check_guests_in_or_out” functional
- New prompt “review_arrivals_and_reservation_details” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.6.0 → 1.8.0 functional
- Server version: 1.5.0 → 1.6.0 functional
- Server version: 1.4.2 → 1.5.0 functional
- 30 Oct 26 0
- Server version: 1.4.1 → 1.4.2 functional
- Server version: 1.4.0 → 1.4.1 functional
- 29 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.3.0 → 1.4.0 functional
- Server version: 1.2.0 → 1.3.0 functional
- 28 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 6 Nov 2026 · Probed https://wubook.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 wubook.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://wubook.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/wubook/ |
| http (plaintext) | http://wubook.usefulapi.io/mcp | Inconclusive | 302 | http://wubook.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 →
wubook_check_in Check in ~97
WRITE: check in the guests of a reservation in ZaK. Applies to every guest of the reservation unless room_customer_ids is given. POST /kp/reservations/do_checkin.
| Name | Type | Req | Description |
|---|---|---|---|
| reservation_code | string | – | Reservation (human) code such as XY-0001. |
| reservation_id | integer | – | Reservation id. |
| room_customer_ids | array | – | Only these reservation-room guest ids (default: all guests). |
No output schema declared.
No examples provided.
wubook_check_out Check out ~96
WRITE: check out the guests of a reservation in ZaK. Applies to every guest of the reservation unless room_customer_ids is given. POST /kp/reservations/do_checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| reservation_code | string | – | Reservation (human) code such as XY-0001. |
| reservation_id | integer | – | Reservation id. |
| room_customer_ids | array | – | Only these reservation-room guest ids (default: all guests). |
No output schema declared.
No examples provided.
wubook_create_reservation Create reservation ~185
WRITE: create a reservation in ZaK for one guest. Give rooms (room type and optionally the physical room id, with price and currency) and/or products (product id with price and currency). Set assign_rooms to let ZaK pick the physical rooms. This books inventory and is NOT idempotent: calling it twice creates two reservations, so check wubook_get_room_availability first and do not retry on an error without looking the reservation up. POST /kp/reservations/new.
| Name | Type | Req | Description |
|---|---|---|---|
| arrival | string | yes | Arrival date, yyyy-mm-dd. |
| assign_rooms | boolean | – | Let ZaK choose physical rooms for entries without a room id. |
| departure | string | yes | Departure date, yyyy-mm-dd (after arrival). |
| guest | object | yes | The booker. |
| products | array | – | – |
| rooms | array | – | – |
No output schema declared.
No examples provided.
wubook_get_customer Get customer (guest) ~100
One guest record by customer id (from a reservation's booker or room customers): name, country, address, contact, birth data, billing info. Personal data. Identity documents (type, number, expiry) are left out unless include_documents is true. POST /kp/customers/fetch_one.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | Customer id. |
| include_documents | boolean | – | Also return the guest's identity documents (default false). |
No output schema declared.
No examples provided.
wubook_get_inventory_symbols Get inventory symbols ~51
The meaning of the short keys in prices and restrictions (p price, a availability, m MinStay, M MaxStay, c closure, ...). POST /kp/inventory/fetch_symbols.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wubook_get_rate_values Get rate values ~121
Daily prices, availability and restrictions of one rate, starting at a date: for each product id a list with one object per day (p price, a availability, m/M min/max stay, c closed, ...; see wubook_get_inventory_symbols). POST /kp/inventory/fetch_rate_values.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | yes | Number of days from `from`, 1-366. |
| from | string | yes | First day, yyyy-mm-dd. |
| rate_id | integer | yes | Rate id (wubook_list_rates). |
No output schema declared.
No examples provided.
wubook_get_reservation Get reservation ~101
One reservation by id or by reservation code (XY-0001): status, booker customer id, origin channel, board, dates, price split (rooms, extras, meals), payment, taxes and rooms with occupancy and customer ids. POST /kp/reservations/fetch_one_reservation.
| Name | Type | Req | Description |
|---|---|---|---|
| reservation_code | string | – | Reservation (human) code such as XY-0001. |
| reservation_id | integer | – | Reservation id. |
No output schema declared.
No examples provided.
wubook_get_room_availability Get room availability ~108
Availability for a stay: for each room type id, the number of rooms available and the ids of the available physical rooms. The availability count can be lower than the number of listed physical rooms when a reservation has no physical room assigned yet; use the availability count when assessing bookable capacity. POST /kp/inventory/fetch_rooms_availability.
| Name | Type | Req | Description |
|---|---|---|---|
| arrival | string | yes | Arrival date, yyyy-mm-dd. |
| departure | string | yes | Departure date, yyyy-mm-dd. |
No output schema declared.
No examples provided.
wubook_list_extras List extras ~41
List the extras the property sells (id, name, price, VAT percentage, cost, tags). POST /kp/property/fetch_extras.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wubook_list_meal_boards List meal boards ~52
List the meal rules and meal prices per board type (fb, hb, bb, ai) for adults, teens, children and babies. POST /kp/property/fetch_meals_board.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wubook_list_products List products ~55
List the products (a room type sold on a board basis: id, room type id, name, default price, occupancy). Product ids are the keys of prices and availability. POST /kp/property/fetch_products.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wubook_list_rates List rates ~46
List the rates of the property (id, name, board, currency, standard flag). Use a rate id for prices and restrictions. POST /kp/property/fetch_rates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wubook_list_reservations List reservations ~204
List reservations, optionally filtered by creation, arrival or departure date ranges (inclusive). Newest first is not guaranteed; page with offset. Returns the page plus next_offset (null when the last page was reached). POST /kp/reservations/fetch_reservations.
| Name | Type | Req | Description |
|---|---|---|---|
| arrival_from | string | – | Arriving on or after. Needs arrival_to. |
| arrival_to | string | – | Arriving on or before. |
| created_from | string | – | Created on or after (yyyy-mm-dd). Needs created_to. |
| created_to | string | – | Created on or before. |
| departure_from | string | – | Departing on or after. Needs departure_to. |
| departure_to | string | – | Departing on or before. |
| limit | – | – | Page size: 8, 16, 32 or 64 (default 32). |
| offset | integer | – | Reservations to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
wubook_list_room_types List room types ~39
List the room types (id, name, short name, default price, default occupancy). POST /kp/property/fetch_room_types.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wubook_list_rooms List rooms ~37
List the physical rooms of the property (id, room type id, name, tags). POST /kp/property/fetch_rooms.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wubook_list_todays_reservations List today's reservations ~45
Reservations of the property for today (arrivals, departures and stays in house). POST /kp/reservations/fetch_today_reservations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wubook_undo_check_in Undo check-in ~66
WRITE: revert the check-in of a reservation in ZaK. POST /kp/reservations/undo_checkin.
| Name | Type | Req | Description |
|---|---|---|---|
| reservation_code | string | – | Reservation (human) code such as XY-0001. |
| reservation_id | integer | – | Reservation id. |
No output schema declared.
No examples provided.
wubook_undo_check_out Undo check-out ~65
WRITE: revert the check-out of a reservation in ZaK. POST /kp/reservations/undo_checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| reservation_code | string | – | Reservation (human) code such as XY-0001. |
| reservation_id | integer | – | Reservation id. |
No output schema declared.
No examples provided.
wubook_update_inventory Update prices, availability and restrictions ~221
WRITE: overwrite daily prices, availability and stay restrictions of one rate. `products` maps a product id to a list of day objects; the first object is the day `from`, the next the following day, and so on. Only the fields you send per day change. Changes can be pushed to connected channels (OTAs) and affect live bookings, so confirm the values with the user first. POST /kp/inventory/write.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | First day the lists start at, yyyy-mm-dd. |
| products | object | yes | Product id → one object per day, e.g. {"12": [{"p": 90, "a": 3}, {"p": 95}]}. Keys: p price, a availability, m/M min/max stay, ma/Ma by arrival, ni no check-in, no no check-out, c closed, nt no OTA,… |
| rate_id | integer | yes | Rate id (wubook_list_rates). |
No output schema declared.
No examples provided.
How do I install the WuBook MCP by usefulapi server?
WuBook MCP by usefulapi is a hosted endpoint at https://wubook.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 · wubook.usefulapi.io
claude mcp add --transport http io-usefulapi-wubook 'https://wubook.usefulapi.io/mcp'
What is the WuBook MCP by usefulapi server?
WuBook MCP by usefulapi is listed in the public MCP registry as io.usefulapi/wubook. Read WuBook ZaK rooms, availability and reservations; manage inventory and guest check-in. This page covers its hosted endpoint (https://wubook.usefulapi.io/mcp).
Is the WuBook MCP by usefulapi server safe to use?
WuBook 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 WuBook MCP by usefulapi server expose?
WuBook MCP by usefulapi exposes 19 tools: wubook_list_rooms, wubook_list_room_types, wubook_list_rates, wubook_list_products, wubook_list_meal_boards, and 14 more. Their descriptions and schemas cost roughly 1,730 tokens of context every time the server is loaded.
Does the WuBook MCP by usefulapi server require authentication?
Its publisher declares no required credentials for WuBook 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 WuBook MCP by usefulapi server still maintained?
WuBook MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 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 WuBook MCP by usefulapi server?
VerifyMCP ran 4 checks on WuBook 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 WuBook 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.