Skip to content

Beds24 MCP by usefulapi

io.usefulapi/beds24usefulapi.iostreamable-httpv1.40.4Scanned

Check bookings, quote stays, read guest messages and reviews, and update calendars in Beds24.

18 tools: 5 can delete or cancel things and 13 only read.

Tools: 5 delete, 0 irreversible, 0 write, 13 read.
  • Reads private data · 3
  • Reads text others write · 4
  • Can send data out · 2
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Beds24 MCP by usefulapi can do

The Beds24 MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 18 tools. It can delete or cancel things (5 tools: beds24_create_booking, beds24_update_booking, beds24_send_booking_message, beds24_mark_messages_read and 1 more). 13 tools only read.

3 tools read private data (beds24_list_bookings, beds24_list_booking_messages and beds24_get_room_calendar); 4 tools bring in text other people can write (beds24_list_bookings, beds24_list_booking_messages, beds24_list_booking_com_reviews and 1 more); 2 tools can send data out of your system (beds24_send_booking_message and beds24_mark_messages_read). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

18 tools

Deletes or cancels 5Claude Code: deny
  • beds24_create_bookingCreate a new booking in a room for given dates and guest details.No findings

    Why it is in this group

    • The name "beds24_create_booking" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a booking
    • destructiveHint: true
  • beds24_mark_messages_readMark one or more booking messages as read (or unread with read=false).Can send data outNo findings

    Why it is in this group

    • The name "beds24_mark_messages_read" says "mark": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "beds24_mark_messages_read" says "mark" and "message": it writes something other people read.
    Description, as the server wrote it
    Mark one or more booking messages as read (or unread with read=false). Beds24: POST /bookings/messages with [{ id, read }].

    Annotations the server declares

    • title: Mark messages read
    • destructiveHint: true
  • beds24_send_booking_messageSend a message on a booking's conversation.Can send data outNo findings

    Why it is in this group

    • The name "beds24_send_booking_message" says "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "beds24_send_booking_message" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Send a booking message
    • destructiveHint: true
  • beds24_update_bookingChange an existing booking: dates, room/unit, guest counts, guest details, notes, flag, price, or status (e.g.No findings

    Why it is in this group

    • The name "beds24_update_booking" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update a booking
    • destructiveHint: true
  • beds24_update_room_calendarSet per-day calendar values for ONE room over a date range: units available (numAvail), minStay, maxStay, multiplier, override (none, blackout, exception, noCheckIn, noCheckOut, no…No findings

    Why it is in this group

    • The name "beds24_update_room_calendar" says "update": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update room calendar
    • destructiveHint: true
Only reads 13Show 13 read-only tools
  • beds24_get_bookingFetch one booking by id with its invoice items, info items and additional guests.No findings

    Why it is in this group

    • The name "beds24_get_booking" says "get": a word for reading.
    Description, as the server wrote it
    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>.

    Annotations the server declares

    • title: Get a booking
    • readOnlyHint: true
  • beds24_get_room_availabilityPer-date availability (true/false) for rooms over a range of nights.No findings

    Why it is in this group

    • The name "beds24_get_room_availability" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get room availability
    • readOnlyHint: true
  • beds24_get_room_calendarPer-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.Reads private dataNo findings

    Why it is in this group

    • The name "beds24_get_room_calendar" says "get": a word for reading.

    What it can reach

    • private-dataThe name "beds24_get_room_calendar" says "get" and "calendar": it reads calendars.
    • private-dataThe description's first sentence says "calendar": it reads calendars.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get room calendar
    • readOnlyHint: true
  • beds24_get_room_offersQuote a stay: bookable offers with total price and units available per room for given dates and guests.No findings

    Why it is in this group

    • The name "beds24_get_room_offers" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get room offers (quote)
    • readOnlyHint: true
  • beds24_get_token_detailsCheck the configured Beds24 token: whether it is valid, its scopes, owner id, expiry, and whether it is restricted to one property.No findings

    Why it is in this group

    • The name "beds24_get_token_details" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get token details
    • readOnlyHint: true
  • beds24_get_unit_bookingsWhich units of each room type are booked on each date — an occupancy grid keyed by date.No findings

    Why it is in this group

    • The name "beds24_get_unit_bookings" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get unit bookings (occupancy grid)
    • readOnlyHint: true
  • beds24_list_airbnb_reviewsGuest reviews from Airbnb for one room: overall and category ratings, public review, private feedback and the host response.Reads text others writeNo findings

    Why it is in this group

    • The name "beds24_list_airbnb_reviews" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe name "beds24_list_airbnb_reviews" says "list" and "review": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List Airbnb reviews
    • readOnlyHint: true
  • beds24_list_booking_com_reviewsGuest reviews from Booking.com for one property, made on or after a date: scores, content, reviewer and any reply.Reads text others writeNo findings

    Why it is in this group

    • The name "beds24_list_booking_com_reviews" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe name "beds24_list_booking_com_reviews" says "list" and "review": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List Booking.com reviews
    • readOnlyHint: true
  • beds24_list_booking_invoicesList invoices and their line items (charges and payments) for bookings.No findings

    Why it is in this group

    • The name "beds24_list_booking_invoices" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List booking invoices
    • readOnlyHint: true
  • beds24_list_booking_messagesRead the guest conversation on bookings — messages from guests, host replies, internal notes and system messages — across channels (Airbnb, Booking.com, Vrbo, direct).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "beds24_list_booking_messages" says "list": a word for reading.

    What it can reach

    • private-dataThe name "beds24_list_booking_messages" says "list" and "message": it reads messages.
    • private-dataThe description's first sentence says "read" and "conversation": it reads messages.
    • untrusted-inputThe name "beds24_list_booking_messages" says "list" and "message": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "read" and "conversation": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List booking messages
    • readOnlyHint: true
  • beds24_list_bookingsSearch 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 referen…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "beds24_list_bookings" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "search" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List bookings
    • readOnlyHint: true
  • beds24_list_fixed_pricesList fixed price rules (seasonal rates): date span, min/max nights, per-room and per-person prices, discounts, allowed arrival days and channel export.No findings

    Why it is in this group

    • The name "beds24_list_fixed_prices" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List fixed prices
    • readOnlyHint: true
  • beds24_list_propertiesList the properties in the account with their address, currency, check-in times and room types (roomTypes).No findings

    Why it is in this group

    • The name "beds24_list_properties" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List properties
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

24 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__beds24__beds24_mark_messages_read",
      "mcp__beds24__beds24_send_booking_message"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:32 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://beds24.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://beds24.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://beds24.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://beds24.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http beds24 https://beds24.usefulapi.io/mcp
claude mcp add --transport http beds24 https://beds24.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__beds24__beds24_get_token_details",
      "mcp__beds24__beds24_list_properties",
      "mcp__beds24__beds24_list_bookings",
      "mcp__beds24__beds24_get_booking",
      "mcp__beds24__beds24_list_booking_messages",
      "mcp__beds24__beds24_list_booking_invoices",
      "mcp__beds24__beds24_get_room_offers",
      "mcp__beds24__beds24_get_room_availability",
      "mcp__beds24__beds24_get_unit_bookings",
      "mcp__beds24__beds24_get_room_calendar",
      "mcp__beds24__beds24_list_fixed_prices",
      "mcp__beds24__beds24_list_booking_com_reviews",
      "mcp__beds24__beds24_list_airbnb_reviews"
    ],
    "ask": [],
    "deny": [
      "mcp__beds24__beds24_create_booking",
      "mcp__beds24__beds24_update_booking",
      "mcp__beds24__beds24_send_booking_message",
      "mcp__beds24__beds24_mark_messages_read",
      "mcp__beds24__beds24_update_room_calendar"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as beds24. Review it before you use it.

Capability tags behind 7 rules
  • mcp__beds24__beds24_list_bookings private-data, untrusted-input
  • mcp__beds24__beds24_list_booking_messages private-data, untrusted-input
  • mcp__beds24__beds24_get_room_calendar private-data
  • mcp__beds24__beds24_list_booking_com_reviews untrusted-input
  • mcp__beds24__beds24_list_airbnb_reviews untrusted-input
  • mcp__beds24__beds24_send_booking_message outbound
  • mcp__beds24__beds24_mark_messages_read outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/beds24/verify?hash=b8d18428a2e77360d40d45130ddae82b4b7fb21d216b7a67f43ad5d10c23a15a" | jq -e '.changed == false'

Pinned hash b8d18428a2e7, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/beds24/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/beds24
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/beds24.svg)](https://radar.anlyon.com/servers/io.usefulapi/beds24)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Beds24 MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Beds24 MCP by usefulapi safe?

No scan can promise that. What its definitions show: 18 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Beds24 MCP by usefulapi delete data?

Yes. 5 tools can delete, cancel or revoke something: beds24_create_booking, beds24_update_booking, beds24_send_booking_message, beds24_mark_messages_read and beds24_update_room_calendar.

Can the Beds24 MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Beds24 MCP by usefulapi have?

18 tools: 5 destructive, 13 read. beds24_create_booking, beds24_update_booking, beds24_send_booking_message, beds24_mark_messages_read, beds24_update_room_calendar, beds24_get_token_details, beds24_list_properties, beds24_list_bookings and 10 more.

Does the Beds24 MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Beds24 MCP by usefulapi send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): beds24_send_booking_message and beds24_mark_messages_read.

Has the Beds24 MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.