io.usefulapi/smoobu
REMOTE · SMOOBU.USEFULAPI.IO · SCANNED OCT 4
Check vacation-rental reservations, rates, availability and guest messages, and update bookings.
Available components
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2672 tokens (~133/item across 20 items; 20 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 Management7
- Stability observed for 2 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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 20 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
How do I install the io.usefulapi/smoobu MCP server?
io.usefulapi/smoobu is a hosted endpoint at https://smoobu.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 · smoobu.usefulapi.io
claude mcp add --transport http io-usefulapi-smoobu 'https://smoobu.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-smoobu": {
"url": "https://smoobu.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-smoobu": {
"type": "http",
"url": "https://smoobu.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-smoobu] url = "https://smoobu.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-smoobu": {
"type": "remote",
"url": "https://smoobu.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-smoobu --url 'https://smoobu.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-smoobu:
url: "https://smoobu.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-smoobu": {
"Transport": "http",
"Url": "https://smoobu.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-smoobu -t streamable-http -u 'https://smoobu.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-smoobu": {
"type": "http",
"url": "https://smoobu.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 +41
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.07 ▲ functional
- 3 Oct 26 −43
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 2 Oct 26 +43
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 100 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- 30 Sept 26 +10
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- 29 Sept 26 18
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 4 Oct 2026 · Probed https://smoobu.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 smoobu.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://smoobu.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://smoobu.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://smoobu.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | No |
| Problem | metadata_http_error |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://smoobu.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://smoobu.usefulapi.io/mcp | HTTPS enforced | 301 | https://smoobu.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 →
smoobu_check_availability Check availability and quote a stay ~172
Check which properties can be booked for an arrival/departure pair and get the total price for each; unavailable ones come back with the reason (minimum stay, too many guests, arrival day, lead time...). Read-only, books nothing. Smoobu: POST /booking/checkApartmentAvailability.
| Name | Type | Req | Description |
|---|---|---|---|
| apartment_ids | array | – | Properties to check. Omit or pass [] to check all. |
| arrival_date | string | yes | Arrival date (yyyy-mm-dd). |
| customer_id | integer | – | Your Smoobu user id. Omit to look it up automatically (one extra GET /api/me). |
| departure_date | string | yes | Departure date (yyyy-mm-dd). |
| discount_code | string | – | Discount code from the booking-tool settings. |
| guests | integer | – | Number of guests. |
No output schema declared.
No examples provided.
smoobu_create_reservation Create a reservation ~449
Create a reservation (or a blocked period) on a property. Smoobu treats it like a booking from a channel and SYNCS the blocked dates to every connected channel (Airbnb, Booking.com, ...). Fails if the dates overlap an existing booking. This server offers no cancel — cancel it in Smoobu if needed. Which guest fields are mandatory depends on your booking-tool 'Form Content' settings. Smoobu: POST /api/reservations.
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | – | Guest address. |
| adults | integer | – | Number of adults. |
| apartment_id | integer | yes | The property id. |
| arrival_date | string | yes | Arrival date (yyyy-mm-dd). |
| arrival_time | string | – | Arrival time (HH:mm, 24h). |
| channel_id | integer | – | Channel id (defaults to 70). Must be a channel the account has, e.g. 13 = Direct booking, 11 = Blocked channel. |
| children | integer | – | Number of children. |
| country | string | – | Guest country. |
| departure_date | string | yes | Departure date (yyyy-mm-dd). |
| departure_time | string | – | Departure time (HH:mm, 24h). |
| deposit | number | – | Deposit amount. |
| deposit_status | – | – | Deposit status: 0 = open / not paid, 1 = paid in full. |
| string | – | Guest email. | |
| first_name | string | – | Guest first name. |
| language | string | – | Guest language, e.g. en, de, es. |
| last_name | string | – | Guest last name. |
| notice | string | – | Free-text notes on the booking. |
| phone | string | – | Guest phone. |
| prepayment | number | – | Prepayment amount. |
| prepayment_status | – | – | Prepayment status: 0 = open / not paid, 1 = paid in full. |
| price | number | – | Total price of the booking. |
| price_elements | array | – | Optional price breakdown (base price, cleaning fee, ...). |
| price_status | – | – | Price status: 0 = open / not paid, 1 = paid in full. |
No output schema declared.
No examples provided.
smoobu_get_apartment Get one property ~68
Fetch one property's details: location, time zone, rooms and beds, max occupancy, amenities, currency, min/max nightly price and type. Smoobu: GET /api/apartments/{apartmentId}.
| Name | Type | Req | Description |
|---|---|---|---|
| apartment_id | integer | yes | The apartment (property) id. |
No output schema declared.
No examples provided.
smoobu_get_guest Get one guest ~60
Fetch one guest by id (the guestId on a reservation) with contact details, notes and every booking they have made. Smoobu: GET /api/guests/{guestId}.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_id | integer | yes | The guest id. |
No output schema declared.
No examples provided.
smoobu_get_rates Get rates and availability ~88
Get the nightly price, minimum length of stay and availability (0 = not available) for each date in a range, for one or more properties. Smoobu: GET /api/rates.
| Name | Type | Req | Description |
|---|---|---|---|
| apartment_ids | array | yes | Property ids. |
| end_date | string | yes | Last date (yyyy-mm-dd). |
| start_date | string | yes | First date (yyyy-mm-dd). |
No output schema declared.
No examples provided.
smoobu_get_reservation Get one reservation ~74
Fetch one reservation by id: guest, dates, check-in/out times, channel and its reference id, price, prepayment and deposit status, and the guest-app URL. Smoobu: GET /api/reservations/{reservationId}.
| Name | Type | Req | Description |
|---|---|---|---|
| reservation_id | integer | yes | The reservation (booking) id. |
No output schema declared.
No examples provided.
smoobu_get_reservation_placeholders Get a reservation's message placeholders ~95
Get every placeholder value Smoobu would substitute into a message for this reservation: guest name, dates and times, nights, price and balance, online check-in link, guest-app link, door PIN codes and more. Useful for drafting a guest message. Smoobu: GET /api/reservations/{reservationId}/placeholders.
| Name | Type | Req | Description |
|---|---|---|---|
| reservation_id | integer | yes | The reservation (booking) id. |
No output schema declared.
No examples provided.
smoobu_get_user Get the current user ~56
Fetch the Smoobu user these credentials belong to (id, name, email). A cheap way to confirm the setup works; the id is the customerId used by availability checks. Smoobu: GET /api/me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
smoobu_list_addons List add-ons ~98
List the bookable add-ons (towels, breakfast, late check-out...) with amount, tax, calculation type (0 per booking, 1 per person, 2 per night, 3 per person and night) and the properties they apply to; optionally for one property. Smoobu: GET /api/addons[/{apartmentId}].
| Name | Type | Req | Description |
|---|---|---|---|
| apartment_id | integer | – | Only add-ons for this property. |
No output schema declared.
No examples provided.
smoobu_list_apartments List properties ~50
List every property (Smoobu calls them apartments) in the account, with id and name. Start here to get apartment ids. Smoobu: GET /api/apartments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
smoobu_list_custom_placeholders List custom placeholders ~48
List the account's custom message placeholders (key, default value, and whether they are global, per booking or per property). Smoobu: GET /api/custom-placeholders.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
smoobu_list_guests List guests ~93
List guests from the Smoobu CRM with their emails, phone numbers, address, notes and bookings; optionally search. Smoobu: GET /api/guests.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Guests per page, 1-100. |
| query | string | – | Search term, e.g. a name or email. |
No output schema declared.
No examples provided.
smoobu_list_message_threads List inbox threads ~85
List the unified guest inbox: one thread per booking with guest name, property and the latest message, plus the unread count. Smoobu: GET /api/threads.
| Name | Type | Req | Description |
|---|---|---|---|
| apartment_ids | array | – | Only threads for these properties. |
| page_number | integer | – | Page number, starting at 1. |
| page_size | integer | – | Threads per page. |
No output schema declared.
No examples provided.
smoobu_list_price_elements List a reservation's price elements ~73
List the financial breakdown of one reservation: base price, cleaning fee, add-ons, long-stay discounts and coupons, with amounts, tax and currency. Smoobu: GET /api/reservations/{reservationId}/price-elements.
| Name | Type | Req | Description |
|---|---|---|---|
| reservation_id | integer | yes | The reservation (booking) id. |
No output schema declared.
No examples provided.
smoobu_list_reservation_messages List a reservation's messages ~121
Get the full conversation for one reservation, paginated. Each message has a subject, plain-text and HTML body, and type (1 = inbox / from guest, 2 = outbox / sent). Smoobu: GET /api/reservations/{reservationId}/messages.
| Name | Type | Req | Description |
|---|---|---|---|
| only_related_to_guest | boolean | – | true = only guest-facing messages; false = every message on the booking. |
| page | integer | – | Page number, starting at 1. |
| reservation_id | integer | yes | The reservation (booking) id. |
No output schema declared.
No examples provided.
smoobu_list_reservations List reservations ~349
List reservations across all channels (Airbnb, Booking.com, direct, ...), paginated, with guest, dates, channel, price and payment status. Filter by stay range, arrival, departure, creation or modification date, and property. Smoobu: GET /api/reservations.
| Name | Type | Req | Description |
|---|---|---|---|
| apartment_id | integer | – | Only this property. |
| arrival_from | string | – | Only arrivals on or after (yyyy-mm-dd). |
| arrival_to | string | – | Only arrivals on or before (yyyy-mm-dd). |
| created_from | string | – | Only bookings created on or after (yyyy-mm-dd). |
| created_to | string | – | Only bookings created on or before (yyyy-mm-dd). |
| departure_from | string | – | Only departures on or after (yyyy-mm-dd). |
| departure_to | string | – | Only departures on or before (yyyy-mm-dd). |
| exclude_blocked | boolean | – | Hide blocked-period bookings. |
| from | string | – | Only bookings overlapping a stay range starting on this date (yyyy-mm-dd). |
| include_price_elements | boolean | – | Include each booking's price breakdown. |
| include_related | boolean | – | With apartment_id: also return bookings from grouped properties. |
| modified_from | string | – | Only bookings modified on or after (yyyy-mm-dd). |
| modified_to | string | – | Only bookings modified on or before (yyyy-mm-dd). |
| page | integer | – | Page number, starting at 1. |
| page_size | integer | – | Bookings per page, 1-100. |
| show_cancellations | boolean | – | Include cancelled bookings. |
| to | string | – | End of that stay range (yyyy-mm-dd). |
No output schema declared.
No examples provided.
smoobu_send_message_to_guest Send a message to a guest ~127
Send a message to the guest of a reservation through Smoobu (it goes out on the booking's channel, e.g. the Airbnb or Booking.com inbox, or email). Delivered IMMEDIATELY and cannot be unsent — confirm the text with the user first. Smoobu: POST /api/reservations/{reservationId}/messages/send-message-to-guest.
| Name | Type | Req | Description |
|---|---|---|---|
| message_body | string | yes | Message content, HTML or plain text. |
| reservation_id | integer | yes | The reservation (booking) id. |
| subject | string | – | Subject line. |
No output schema declared.
No examples provided.
smoobu_send_message_to_host Post a message to the host ~130
Post a message on a reservation's thread addressed to the Smoobu user (the host). With internal=true it is an internal note hidden from the guest — handy for logging. Cannot be unsent. Smoobu: POST /api/reservations/{reservationId}/messages/send-message-to-host.
| Name | Type | Req | Description |
|---|---|---|---|
| internal | boolean | – | true = visible only to the host, hidden from the guest. |
| message_body | string | yes | Message content, HTML or plain text. |
| reservation_id | integer | yes | The reservation (booking) id. |
| subject | string | – | Subject line. |
No output schema declared.
No examples provided.
smoobu_set_rates Set rates and minimum stays ~123
Set the nightly price and/or minimum length of stay for dates on one or more properties. Smoobu PUSHES these to every channel with price sync enabled, so this changes live prices guests see. Reversible by setting the old values again — read them first with smoobu_get_rates. Each operation needs daily_price, min_length_of_stay, or both (a minimum stay alone needs an existing price). Smoobu: POST /api/rates.
| Name | Type | Req | Description |
|---|---|---|---|
| apartment_ids | array | yes | Property ids. |
| operations | array | yes | Rate changes to apply. |
No output schema declared.
No examples provided.
smoobu_update_reservation Update a reservation ~313
Update an existing reservation's times, guest contact, notes, guest counts, language, or price / prepayment / deposit amounts and paid status. Only the fields you pass are sent. Dates and property cannot be changed here. Smoobu: PUT /api/reservations/{reservationId}.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | Number of adults. |
| arrival_time | string | – | Arrival time (HH:mm, 24h). |
| assistant_notice | string | – | Instructions for your assistant / cleaner. |
| children | integer | – | Number of children. |
| departure_time | string | – | Departure time (HH:mm, 24h). |
| deposit | number | – | Deposit amount. |
| deposit_status | – | – | Deposit status: 0 = open / not paid, 1 = paid in full. |
| guest_email | string | – | Guest email. |
| guest_name | string | – | Guest name. |
| guest_phone | string | – | Guest phone. |
| language | string | – | Guest language, e.g. en, de, es. |
| notice | string | – | Free-text notes on the booking. |
| prepayment | number | – | Prepayment amount. |
| prepayment_status | – | – | Prepayment status: 0 = open / not paid, 1 = paid in full. |
| price | number | – | Total price. |
| price_status | – | – | Price status: 0 = open / not paid, 1 = paid in full. |
| reservation_id | integer | yes | The reservation (booking) id. |
No output schema declared.
No examples provided.
What is the io.usefulapi/smoobu MCP server?
io.usefulapi/smoobu is an MCP server listed in the public MCP registry as io.usefulapi/smoobu. Check vacation-rental reservations, rates, availability and guest messages, and update bookings. This page covers its hosted endpoint (https://smoobu.usefulapi.io/mcp).
Is the io.usefulapi/smoobu MCP server safe to use?
io.usefulapi/smoobu scores 74 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 io.usefulapi/smoobu MCP server expose?
io.usefulapi/smoobu exposes 20 tools: smoobu_get_user, smoobu_list_apartments, smoobu_get_apartment, smoobu_list_reservations, smoobu_get_reservation, and 15 more. Their descriptions and schemas cost roughly 2,672 tokens of context every time the server is loaded.
Does the io.usefulapi/smoobu MCP server require authentication?
Yes. io.usefulapi/smoobu 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 io.usefulapi/smoobu MCP server still maintained?
io.usefulapi/smoobu is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.