io.usefulapi/beds24
REMOTE · BEDS24.USEFULAPI.IO · SCANNED OCT 4
Check bookings, quote stays, read guest messages and reviews, and update calendars in Beds24.
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 Security89
- 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 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
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3732 tokens (~207/item across 18 items; 18 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 Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 18 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/beds24 MCP server?
io.usefulapi/beds24 is a hosted endpoint at https://beds24.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 · beds24.usefulapi.io
claude mcp add --transport http io-usefulapi-beds24 'https://beds24.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-beds24": {
"url": "https://beds24.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-beds24": {
"type": "http",
"url": "https://beds24.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-beds24] url = "https://beds24.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-beds24": {
"type": "remote",
"url": "https://beds24.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-beds24 --url 'https://beds24.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-beds24:
url: "https://beds24.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-beds24": {
"Transport": "http",
"Url": "https://beds24.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-beds24 -t streamable-http -u 'https://beds24.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-beds24": {
"type": "http",
"url": "https://beds24.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 +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.
- 2 Oct 26 +41
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Stability: unverified → 0.07 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Server version: 1.0.0 → 1.5.1 functional
- 1 Oct 26 −35
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: unverified → pass ▲ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 30 Sept 26 +40
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial 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 Tool coverage: 74 functional
- First check of Destructive annotations: 100 functional
- 29 Sept 26 28
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://beds24.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 beds24.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 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 | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://beds24.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://beds24.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://beds24.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://beds24.usefulapi.io/mcp |
| Authorisation server | https://beds24.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://beds24.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://beds24.usefulapi.io/mcp | HTTPS enforced | 301 | https://beds24.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 →
beds24_create_booking Create a booking ~486
Create a new booking in a room for given dates and guest details. It immediately blocks inventory and is synced to connected channels. Set checkAvailability=true to refuse the booking if the room is not free, and notifyGuest / notifyHost to send confirmation emails. Undo by setting status cancelled with beds24_update_booking. Requires a token with bookings write access. Beds24: POST /bookings.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| arrival | string | yes | Arrival date, YYYY-MM-DD. |
| arrivalTime | string | – | Expected arrival time (free text). |
| assignBooking | boolean | – | Let Beds24 assign the first free unit / room using room dependency settings. |
| checkAvailability | boolean | – | Do not save the booking if the room has no availability. Recommended. |
| city | string | – | – |
| comments | string | – | Guest comments. |
| company | string | – | – |
| country | string | – | Free text country. |
| country2 | string | – | 2-letter country code, e.g. DE. |
| departure | string | yes | Departure (check-out) date, YYYY-MM-DD. |
| deposit | number | – | – |
| string | – | – | |
| firstName | string | – | – |
| flagColor | string | – | Flag colour, 6-character hex (e.g. ff0000) or empty string to clear. |
| flagText | string | – | – |
| lang | string | – | Guest language, 2-letter code, e.g. en. |
| lastName | string | – | – |
| mobile | string | – | – |
| notes | string | – | Internal host notes. |
| notifyGuest | boolean | – | Email the guest a booking confirmation. |
| notifyHost | boolean | – | Email the host a booking confirmation. |
| numAdult | integer | – | Number of adults. |
| numChild | integer | – | Number of children. |
| phone | string | – | – |
| postcode | string | – | – |
| price | number | – | Total booking price. |
| reference | string | – | Your own reference. |
| roomId | integer | yes | Room (room type) id. |
| state | string | – | – |
| status | string | – | Booking status. |
| tax | number | – | – |
| title | string | – | Guest title, e.g. Mr, Ms. |
| unitId | integer | – | Specific unit within the room type. |
No output schema declared.
No examples provided.
beds24_get_booking Get a booking ~56
Fetch one booking by id with its invoice items, info items and additional guests. Works for any status, including cancelled. Beds24: GET /bookings?id=<id>.
| Name | Type | Req | Description |
|---|---|---|---|
| bookingId | integer | yes | The booking id. |
No output schema declared.
No examples provided.
beds24_get_room_availability Get room availability ~140
Per-date availability (true/false) for rooms over a range of nights. endDate is the LAST NIGHT (the day before check-out). Beds24: GET /inventory/rooms/availability.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | – | Last night (day before check-out), YYYY-MM-DD. |
| page | integer | – | Page number beyond the first (2, 3, ...). Check pages.nextPageExists in the previous response. |
| propertyIds | array | – | One or more property ids. |
| roomIds | array | – | One or more room ids. |
| startDate | string | – | First night, YYYY-MM-DD. |
No output schema declared.
No examples provided.
beds24_get_room_calendar Get room calendar ~245
Per-day calendar values for rooms: units available, min/max stay, multiplier, override (blackout, no check-in, ...) and the price slots price1..price16, as date ranges. Choose fields with the include flags; if none are set this tool asks for numAvail, minStay, maxStay, override and prices. Beds24: GET /inventory/rooms/calendar.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | Last date, YYYY-MM-DD. |
| includeChannels | boolean | – | Include per-channel booking limits. |
| includeLinkedPrices | boolean | – | – |
| includeMaxStay | boolean | – | – |
| includeMinStay | boolean | – | – |
| includeMultiplier | boolean | – | – |
| includeNumAvail | boolean | – | – |
| includeOverride | boolean | – | – |
| includePrices | boolean | – | – |
| page | integer | – | Page number beyond the first (2, 3, ...). Check pages.nextPageExists in the previous response. |
| propertyIds | array | – | One or more property ids. |
| roomIds | array | – | One or more room ids. |
| startDate | string | yes | First date, YYYY-MM-DD. |
No output schema declared.
No examples provided.
beds24_get_room_offers Get room offers (quote) ~195
Quote a stay: bookable offers with total price and units available per room for given dates and guests. Use before creating a booking. Beds24: GET /inventory/rooms/offers.
| Name | Type | Req | Description |
|---|---|---|---|
| agentCode | string | – | – |
| arrival | string | yes | Arrival date, YYYY-MM-DD. |
| departure | string | yes | Departure date, YYYY-MM-DD. |
| includeTexts | array | – | Include descriptive texts in these 2-letter languages, e.g. ["en"]. |
| numAdults | integer | yes | Number of adults. |
| numChildren | integer | – | – |
| offerIds | array | – | One or more offer ids. |
| page | integer | – | Page number beyond the first (2, 3, ...). Check pages.nextPageExists in the previous response. |
| propertyIds | array | – | One or more property ids. |
| roomIds | array | – | One or more room ids. |
No output schema declared.
No examples provided.
beds24_get_token_details Get token details ~77
Check the configured Beds24 token: whether it is valid, its scopes, owner id, expiry, and whether it is restricted to one property. A cheap way to confirm setup and see which scopes are granted. Note Beds24 answers HTTP 200 with validToken=false for a bad token. Beds24: GET /authentication/details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
beds24_get_unit_bookings Get unit bookings (occupancy grid) ~139
Which units of each room type are booked on each date — an occupancy grid keyed by date. endDate is the last night. Beds24 marks this endpoint Beta. Beds24: GET /inventory/rooms/unitBookings.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | – | Last night, YYYY-MM-DD. |
| page | integer | – | Page number beyond the first (2, 3, ...). Check pages.nextPageExists in the previous response. |
| propertyIds | array | – | One or more property ids. |
| roomIds | array | – | One or more room ids. |
| startDate | string | – | First night, YYYY-MM-DD. |
No output schema declared.
No examples provided.
beds24_list_airbnb_reviews List Airbnb reviews ~79
Guest reviews from Airbnb for one room: overall and category ratings, public review, private feedback and the host response. At most 100 per call. Beds24 marks this endpoint Beta. Beds24: GET /channels/airbnb/reviews.
| Name | Type | Req | Description |
|---|---|---|---|
| roomId | integer | yes | The Beds24 room id linked to the Airbnb listing. |
No output schema declared.
No examples provided.
beds24_list_booking_com_reviews List Booking.com reviews ~91
Guest reviews from Booking.com for one property, made on or after a date: scores, content, reviewer and any reply. At most 100 per call. Beds24 marks this endpoint Alpha. Beds24: GET /channels/booking/reviews.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Reviews made on or after this date, YYYY-MM-DD. |
| propertyId | integer | yes | The property id. |
No output schema declared.
No examples provided.
beds24_list_booking_invoices List booking invoices ~92
List invoices and their line items (charges and payments) for bookings. Requires the bookings-financial scope. Beds24 marks this endpoint Alpha. Beds24: GET /bookings/invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| bookingIds | array | – | One or more booking ids. |
| page | integer | – | Page number beyond the first (2, 3, ...). Check pages.nextPageExists in the previous response. |
No output schema declared.
No examples provided.
beds24_list_booking_messages List booking messages ~200
Read the guest conversation on bookings — messages from guests, host replies, internal notes and system messages — across channels (Airbnb, Booking.com, Vrbo, direct). Filter by booking, property, room, read/unread, source and age. Beds24: GET /bookings/messages.
| Name | Type | Req | Description |
|---|---|---|---|
| bookingIds | array | – | One or more booking ids. |
| filter | string | – | – |
| masterIds | array | – | One or more group master booking ids. |
| maxAge | integer | – | Only messages from the last N days. |
| messageIds | array | – | One or more message ids. |
| page | integer | – | Page number beyond the first (2, 3, ...). Check pages.nextPageExists in the previous response. |
| propertyIds | array | – | One or more property ids. |
| roomIds | array | – | One or more room ids. |
| source | string | – | Only messages from one side. |
No output schema declared.
No examples provided.
beds24_list_bookings List bookings ~438
Search bookings by arrival/departure date range, booking or modified time, property, room, channel, status, or a free-text search over guest name, email, booking id and API reference. With NO filters Beds24 returns only upcoming bookings. `filter` shortcuts: arrivals (arriving today), departures (departing today), new (created in the last 24h), current (in-house). Guest data needs the bookings-personal scope, invoice items bookings-financial. Beds24: GET /bookings.
| Name | Type | Req | Description |
|---|---|---|---|
| apiReferences | array | – | Channel / API references. |
| arrival | string | – | Exact arrival date. |
| arrivalFrom | string | – | Date, YYYY-MM-DD. |
| arrivalTo | string | – | Date, YYYY-MM-DD. |
| bookingIds | array | – | One or more booking ids. |
| bookingTimeFrom | string | – | Booked after this time (UTC). |
| bookingTimeTo | string | – | Booked before this time (UTC). |
| channel | string | – | Only bookings from this channel. |
| departure | string | – | Exact departure date. |
| departureFrom | string | – | Date, YYYY-MM-DD. |
| departureTo | string | – | Date, YYYY-MM-DD. |
| filter | string | – | – |
| includeBookingGroup | boolean | – | – |
| includeGuests | boolean | – | Include additional guests (bookings-personal scope). |
| includeInfoItems | boolean | – | – |
| includeInvoiceItems | boolean | – | – |
| masterIds | array | – | One or more group master booking ids. |
| modifiedFrom | string | – | Modified after this time. |
| modifiedTo | string | – | Modified before this time. |
| page | integer | – | Page number beyond the first (2, 3, ...). Check pages.nextPageExists in the previous response. |
| propertyIds | array | – | One or more property ids. |
| roomIds | array | – | One or more room ids. |
| searchString | string | – | Matches guest name, email, apiReference or booking id. |
| status | array | – | Statuses to include. Defaults to all except cancelled. |
No output schema declared.
No examples provided.
beds24_list_fixed_prices List fixed prices ~132
List fixed price rules (seasonal rates): date span, min/max nights, per-room and per-person prices, discounts, allowed arrival days and channel export. Beds24: GET /inventory/fixedPrices.
| Name | Type | Req | Description |
|---|---|---|---|
| fixedPriceIds | array | – | One or more fixed price ids. |
| includeRateCodes | boolean | – | – |
| page | integer | – | Page number beyond the first (2, 3, ...). Check pages.nextPageExists in the previous response. |
| propertyIds | array | – | One or more property ids. |
| roomIds | array | – | One or more room ids. |
No output schema declared.
No examples provided.
beds24_list_properties List properties ~223
List the properties in the account with their address, currency, check-in times and room types (roomTypes). Optional flags include texts, pictures, offers, unit details and all rooms. Requires the properties scope. Beds24: GET /properties.
| Name | Type | Req | Description |
|---|---|---|---|
| includeAllRooms | boolean | – | Include every room type of each property. |
| includeLanguages | array | – | Languages for texts, e.g. ["en"] or ["all"]. |
| includeOffers | boolean | – | Include offers per room. |
| includePictures | boolean | – | – |
| includePriceRules | boolean | – | – |
| includeTexts | array | – | Which descriptive texts to include. |
| includeUnitDetails | boolean | – | Include full unit details (by default only unit names). |
| includeUpsellItems | boolean | – | – |
| page | integer | – | Page number beyond the first (2, 3, ...). Check pages.nextPageExists in the previous response. |
| propertyIds | array | – | One or more property ids. |
| roomIds | array | – | One or more room ids. |
No output schema declared.
No examples provided.
beds24_mark_messages_read Mark messages read ~68
Mark one or more booking messages as read (or unread with read=false). Beds24: POST /bookings/messages with [{ id, read }].
| Name | Type | Req | Description |
|---|---|---|---|
| messageIds | array | yes | Message ids. |
| read | boolean | – | true (default) = read, false = unread. |
No output schema declared.
No examples provided.
beds24_send_booking_message Send a booking message ~114
Send a message on a booking's conversation. With source host (default) it is delivered to the GUEST through their channel (Airbnb, Booking.com, Vrbo, email) and cannot be unsent; with source internalNote it is a private host note. Beds24: POST /bookings/messages.
| Name | Type | Req | Description |
|---|---|---|---|
| bookingId | integer | yes | The booking id. |
| message | string | yes | Message text. |
| source | string | – | host (to the guest, default) or internalNote (private). |
No output schema declared.
No examples provided.
beds24_update_booking Update a booking ~462
Change an existing booking: dates, room/unit, guest counts, guest details, notes, flag, price, or status (e.g. confirmed, or cancelled to cancel — reversible by setting it back). Only the fields you pass change. Optionally add info items (code/text pairs). Changes sync to channels where allowed. Beds24: POST /bookings with the booking id.
| Name | Type | Req | Description |
|---|---|---|---|
| addInfoItems | array | – | Info items to ADD to the booking (existing ones are untouched). |
| address | string | – | – |
| arrival | string | – | Arrival date, YYYY-MM-DD. |
| arrivalTime | string | – | Expected arrival time (free text). |
| bookingId | integer | yes | The booking id to change. |
| city | string | – | – |
| comments | string | – | Guest comments. |
| company | string | – | – |
| country | string | – | Free text country. |
| country2 | string | – | 2-letter country code, e.g. DE. |
| departure | string | – | Departure (check-out) date, YYYY-MM-DD. |
| deposit | number | – | – |
| string | – | – | |
| firstName | string | – | – |
| flagColor | string | – | Flag colour, 6-character hex (e.g. ff0000) or empty string to clear. |
| flagText | string | – | – |
| lang | string | – | Guest language, 2-letter code, e.g. en. |
| lastName | string | – | – |
| mobile | string | – | – |
| notes | string | – | Internal host notes. |
| notifyGuest | boolean | – | Email the guest an updated confirmation. |
| numAdult | integer | – | Number of adults. |
| numChild | integer | – | Number of children. |
| phone | string | – | – |
| postcode | string | – | – |
| price | number | – | Total booking price. |
| reference | string | – | Your own reference. |
| roomId | integer | – | Room (room type) id. |
| state | string | – | – |
| status | string | – | Booking status. |
| tax | number | – | – |
| title | string | – | Guest title, e.g. Mr, Ms. |
| unitId | integer | – | Specific unit within the room type. |
No output schema declared.
No examples provided.
beds24_update_room_calendar Update room calendar ~495
Set per-day calendar values for ONE room over a date range: units available (numAvail), minStay, maxStay, multiplier, override (none, blackout, exception, noCheckIn, noCheckOut, noCheckInOrCheckOut) and price slots price1..price16. Set a price to null to remove it. These values sync to channels. Read the current values first with beds24_get_room_calendar so you can restore them. Beds24: POST /inventory/rooms/calendar.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | First date, YYYY-MM-DD. |
| maxStay | integer | – | – |
| minStay | integer | – | – |
| multiplier | number | – | – |
| numAvail | integer | – | Units available per day. |
| override | string | – | – |
| price1 | number|null | – | Calendar price1 for these dates. null removes it. |
| price10 | number|null | – | Calendar price10 for these dates. null removes it. |
| price11 | number|null | – | Calendar price11 for these dates. null removes it. |
| price12 | number|null | – | Calendar price12 for these dates. null removes it. |
| price13 | number|null | – | Calendar price13 for these dates. null removes it. |
| price14 | number|null | – | Calendar price14 for these dates. null removes it. |
| price15 | number|null | – | Calendar price15 for these dates. null removes it. |
| price16 | number|null | – | Calendar price16 for these dates. null removes it. |
| price2 | number|null | – | Calendar price2 for these dates. null removes it. |
| price3 | number|null | – | Calendar price3 for these dates. null removes it. |
| price4 | number|null | – | Calendar price4 for these dates. null removes it. |
| price5 | number|null | – | Calendar price5 for these dates. null removes it. |
| price6 | number|null | – | Calendar price6 for these dates. null removes it. |
| price7 | number|null | – | Calendar price7 for these dates. null removes it. |
| price8 | number|null | – | Calendar price8 for these dates. null removes it. |
| price9 | number|null | – | Calendar price9 for these dates. null removes it. |
| roomId | integer | yes | The room id. |
| to | string | yes | Last date, YYYY-MM-DD. |
No output schema declared.
No examples provided.
What is the io.usefulapi/beds24 MCP server?
io.usefulapi/beds24 is an MCP server listed in the public MCP registry as io.usefulapi/beds24. Check bookings, quote stays, read guest messages and reviews, and update calendars in Beds24. This page covers its hosted endpoint (https://beds24.usefulapi.io/mcp).
Is the io.usefulapi/beds24 MCP server safe to use?
io.usefulapi/beds24 scores 75 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/beds24 MCP server expose?
io.usefulapi/beds24 exposes 18 tools: beds24_get_token_details, beds24_list_properties, beds24_list_bookings, beds24_get_booking, beds24_list_booking_messages, and 13 more. Their descriptions and schemas cost roughly 3,732 tokens of context every time the server is loaded.
Does the io.usefulapi/beds24 MCP server require authentication?
Yes. io.usefulapi/beds24 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/beds24 MCP server still maintained?
io.usefulapi/beds24 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.