Bookare
REMOTE · BOOKARE.APP
Online booking for gyms, salons, restaurants and stays. No commission, free plan. Set up by your AI.
Available components
Last scanned (21 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
Recent critical change
Authorization (18 Nov 2026). See the changelog before you install this server.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (setup_from_template). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 9381 tokens (~156/item across 60 items; 60 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 Management0
- Stability check failed: schema churn in the 4 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 56 additions. See how to fix → Fail
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% 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 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 61 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 20 Nov 26 0
- “create_pack” added an optional parameter “price_on_public_page” cosmetic
- “create_pack” added an optional parameter “public_page” cosmetic
- “update_pack” added an optional parameter “price_on_public_page” cosmetic
- “update_pack” added an optional parameter “public_page” cosmetic
4 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 18 Nov 26 −5
- Authorization: partial → fail ▼ critical
- Stability: unverified → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “call_venue_tool” was removed ▼ security
- Tool “list_venue_tools” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- New tool “delete_class_type”, which the server declares destructive security
- New tool “delete_pack”, which the server declares destructive security
- New tool “delete_unit”, which the server declares destructive security
- New tool “remove_photo”, which the server declares destructive security
- New tool “remove_season”, which the server declares destructive security
- New tool “remove_weekly_class”, which the server declares destructive security
- New tool “reset_nightly_price”, which the server declares destructive security
- New tool “set_coupon_active”, which the server declares destructive security
- Tool “check_address” rewrote its description, which is the text the model reads security
- Tool “create_venue” rewrote its description, which is the text the model reads security
- Tool “get_plans” rewrote its description, which is the text the model reads security
- Tool “get_claim_link” is now declared destructive security
- Tool “set_booking_rules” is now declared destructive security
- Tool “set_branding” is now declared destructive security
- Tool “set_listing” is now declared destructive security
- Tool “set_nightly_price” is now declared destructive security
- Tool “set_opening_hours” is now declared destructive security
- Tool “set_stay_rules” is now declared destructive security
- Tool “setup_from_template” is now declared destructive security
- Tool “update_class_type” is now declared destructive security
- Tool “update_pack” is now declared destructive security
- Tool “update_unit” is now declared destructive security
- Tool “update_venue” is now declared destructive security
- Tool “update_weekly_class” is now declared destructive security
- Schema quality: 909 → 9235 ▼ functional
- Tool coverage: 63% → 88% ▲ functional
- Schema quality: fair → good functional
- Destructive annotations: pass → 100 functional
- Server version: 1.0.0 → 1.1.1 functional
- New tool “add_instructor” functional
- New tool “add_photo” functional
- New tool “add_season” functional
- New tool “add_service” functional
- New tool “add_staff” functional
- New tool “add_table” functional
- New tool “add_weekly_class” functional
- New tool “close_days” functional
- New tool “create_class_type” functional
- New tool “create_coupon” functional
- New tool “create_pack” functional
- New tool “create_unit” functional
- New tool “get_agenda_setup” functional
- New tool “get_claim_link” functional
- New tool “get_dns_instructions” functional
- New tool “get_embed_code” functional
- New tool “get_listing” functional
- New tool “get_timetable” functional
- New tool “get_venue” functional
- New tool “import_bookings” functional
- New tool “import_member_packs” functional
- New tool “import_members” functional
- New tool “import_status” functional
- New tool “import_visits” functional
- New tool “list_class_types” functional
- New tool “list_closed_days” functional
- New tool “list_coupons” functional
- New tool “list_instructors” functional
- New tool “list_nightly_prices” functional
- New tool “list_packs” functional
- New tool “list_stay_options” functional
- New tool “list_templates” functional
- New tool “list_units” functional
- New tool “open_days” functional
- New tool “set_booking_rules” functional
- New tool “set_branding” functional
- New tool “set_cover_photo” functional
- New tool “set_listing” functional
- New tool “set_nightly_price” functional
- New tool “set_opening_hours” functional
- New tool “set_pack_visibility” functional
- New tool “set_stay_rules” functional
- New tool “setup_from_template” functional
- New tool “update_class_type” functional
- New tool “update_pack” functional
- New tool “update_unit” functional
- New tool “update_venue” functional
- New tool “update_weekly_class” functional
- “create_venue” reworded the description of “business_type” cosmetic
- 17 Nov 26 69
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 21 Nov 2026 · Probed https://bookare.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bookare.app | CN=WE1,O=Google Trust Services,C=US | 17 Nov 2026 | 15 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | ff15a58ad437bdaa13c4c055e9ff3778 |
| SANs: bookare.app, docs.bookare.app, *.docs.bookare.app | ||||||
| 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 bookare.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| bookare.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bookare.app/mcp | Verified | 200 | |
| http (plaintext) | http://bookare.app/mcp | HTTPS enforced | 301 | https://bookare.app/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 →
set_nightly_price Set the price of specific nights ~212
Gives its own price per night to one night or a range (e.g. Christmas), for one unit or (without unit_id) for every unit. It wins over seasons and the base price. weekdays limits it to some days of the week, e.g. ["fri","sat"] for weekends in July. Existing bookings keep their agreed total. For one night, send only from. Acts on one venue, given its address and access key.
| Name | Type | Req | Description |
|---|---|---|---|
| access_key | string | yes | The venue’s access key. |
| address | string | yes | The venue’s address name, the "name" in name.bookare.app. |
| from | string | yes | First night, YYYY-MM-DD. |
| price_per_night_eur | number | yes | – |
| to | string | – | Last night (inclusive), YYYY-MM-DD. Default: same as from. |
| unit_id | string | – | Leave out to set it on every unit. |
| weekdays | array | – | Optional: only these nights of the week. |
No output schema declared.
No examples provided.
set_opening_hours Set opening hours for bookings ~128
Replaces the hours when appointments or tables can be booked. One row per period, several per day allowed (e.g. 10:00-14:00 and 17:00-21:00). Days not listed are closed. For restaurants "to" is the last time a table can be booked. Acts on one venue, given its address and access key.
| Name | Type | Req | Description |
|---|---|---|---|
| access_key | string | yes | The venue’s access key. |
| address | string | yes | The venue’s address name, the "name" in name.bookare.app. |
| hours | array | yes | – |
No output schema declared.
No examples provided.
set_pack_visibility Activate or deactivate a pack ~115
visible = false deactivates a pack: it is hidden and can no longer be bought; members who have it keep it. visible = true activates it again. This is the safe way to stop selling a pack. Acts on one venue, given its address and access key.
| Name | Type | Req | Description |
|---|---|---|---|
| access_key | string | yes | The venue’s access key. |
| address | string | yes | The venue’s address name, the "name" in name.bookare.app. |
| pack_id | string | yes | – |
| visible | boolean | yes | – |
No output schema declared.
No examples provided.
set_stay_rules Change the booking rules ~155
Check-in and check-out times, whether online bookings are confirmed at once or wait for the venue, and until how many days before arrival a guest may cancel. Only the fields sent are changed. Acts on one venue, given its address and access key.
| Name | Type | Req | Description |
|---|---|---|---|
| access_key | string | yes | The venue’s access key. |
| address | string | yes | The venue’s address name, the "name" in name.bookare.app. |
| check_in_from | string | – | HH:MM |
| check_out_by | string | – | HH:MM |
| guest_can_cancel_until_days_before | integer | – | 0-60 |
| instant_confirmation | boolean | – | False = each online booking waits for the venue to confirm. |
No output schema declared.
No examples provided.
setup_from_template Set up from a ready-made template ~156
Fills an empty or new venue with a typical setup in one call: e.g. "pilates" adds class types, a weekly timetable, packs with suggested prices and booking rules. replace_starter = true removes the empty starter class type made at sign-up. Returns what was added. Acts on one venue, given its address and access key.
| Name | Type | Req | Description |
|---|---|---|---|
| access_key | string | yes | The venue’s access key. |
| address | string | yes | The venue’s address name, the "name" in name.bookare.app. |
| replace_starter | boolean | – | Default true. |
| template_id | string | yes | Template id, e.g. pilates, yoga, hair_salon, restaurant, small_hotel, campsite. |
No output schema declared.
No examples provided.
update_class_type Change a class type ~175
Renames a class type or changes its default spots, colour, whether packs are charged or whether it is drop-in. Spots apply to classes created from now on. Acts on one venue, given its address and access key.
| Name | Type | Req | Description |
|---|---|---|---|
| access_key | string | yes | The venue’s access key. |
| address | string | yes | The venue’s address name, the "name" in name.bookare.app. |
| booked_with_packs | boolean | – | – |
| class_type_id | string | yes | – |
| colour | string | – | – |
| drop_in | boolean | – | True = no times on the timetable: people just come in and check in (e.g. the gym floor). Each check-in takes one class from their pack, at most once a day. |
| name | string | – | – |
| spots | integer | – | – |
No output schema declared.
No examples provided.
update_pack Change a pack ~366
Changes a pack on sale. Only the fields you send change. Packs members have already bought keep their own terms and are not affected. Acts on one venue, given its address and access key.
| Name | Type | Req | Description |
|---|---|---|---|
| access_key | string | yes | The venue’s access key. |
| address | string | yes | The venue’s address name, the "name" in name.bookare.app. |
| class_type_ids | array | – | Class types the pack can be used for. Empty list = all. |
| classes | integer | – | How many classes the pack holds (1-200). Leave out when unlimited is true. |
| description | string | – | Longer description shown with the pack. |
| name | string | – | Name shown to members, e.g. "Move 10". |
| off_peak_only | boolean | – | True if it can be used only for classes marked off-peak. |
| on_sale_until | string | – | YYYY-MM-DD: a limited-time pack members can buy until the end of that day. Empty string = always on sale. |
| pack_id | string | yes | – |
| price_eur | number | – | Price in euro, e.g. 59.9. |
| price_on_public_page | boolean | – | True (default): visitors who are not signed in see the price. False: they see "Price for members"; signed-in members see the price. |
| public_page | boolean | – | True (default): visitors who are not signed in see the pack on the venue page. False: only signed-in members see it. |
| tagline | string | – | One short line under the name. |
| unlimited | boolean | – | True for unlimited classes until it expires. |
| valid_days | integer | – | Days the pack is valid from the day it is bought (1-730). |
No output schema declared.
No examples provided.
update_unit Change a unit ~402
Changes a unit. Only the fields you send change. Existing bookings keep their agreed total. Acts on one venue, given its address and access key.
| Name | Type | Req | Description |
|---|---|---|---|
| access_key | string | yes | The venue’s access key. |
| address | string | yes | The venue’s address name, the "name" in name.bookare.app. |
| amenities | array | – | Unit amenity keys (the unit_amenities list of this venue’s stay options), e.g. ["wifi","ac","kitchen"]. |
| bathrooms | integer | – | 0 = not shown. |
| bedrooms | integer | – | 0 = not shown. |
| beds | object | – | How many beds of each kind, e.g. {"double":1,"single":2}. Kinds: double, single, sofa, bunk. |
| description | string | – | Free text for guests (up to 600 characters). |
| guests_up_to | integer | – | Most guests it takes (1-60). |
| identical_units | integer | – | How many identical ones exist, e.g. 20 tent and camper pitches. Default 1. |
| kind | string | – | What it is. |
| min_nights | integer | – | Minimum nights per booking. Default 1. |
| name | string | – | Name guests see, e.g. "Sea-view studio" or "Tent or camper pitch". |
| price_per_night_eur | number | – | Base price per night in euro (seasons can override it). |
| shown_to_guests | boolean | – | False hides the unit from the booking page. Default true. |
| size_sqm | integer | – | Size in square metres. 0 = not shown. |
| takes_bookings | boolean | – | False keeps the unit visible to guests but they cannot book it (e.g. not ready yet); its nights are closed on connected channels too. The venue can still add bookings itself. Default true. |
| unit_id | string | yes | – |
No output schema declared.
No examples provided.
update_venue Change venue details ~350
Changes the venue’s name, legal name, address, phones, contact email, website or opening hours: what customers see at the bottom of every page and in emails. Only the fields you send change; send an empty value to clear one. The venue type, country and booking address cannot be changed here. Acts on one venue, given its address and access key.
| Name | Type | Req | Description |
|---|---|---|---|
| access_key | string | yes | The venue’s access key. |
| address | string | yes | The venue’s address name, the "name" in name.bookare.app. |
| city | string | – | City or area, e.g. "Zografou". |
| string | – | Contact email shown to customers. | |
| legal_name | string | – | The business’s legal name, shown on the privacy page as the data controller. |
| name | string | – | Venue name (2-80 characters). |
| opening_hours | array | – | Opening hours, one line per group of days (up to 7 lines), e.g. ["Mon–Wed 09:00–13:00 & 16:00–21:00", "Sat 09:00–14:00"]. Empty list clears them. |
| phones | array | – | Up to two phone numbers, the main one first. Numbers without a country code are taken as the venue’s country. |
| postal_code | string | – | Postal code, e.g. "157 73". |
| street | string | – | Street and number, e.g. "Agias Lavras 5-7". |
| website | string | – | The venue’s own website, full address like https://example.gr. Used for the “back to site” button. |
No output schema declared.
No examples provided.
update_weekly_class Change a weekly class ~233
Moves a weekly class to another day or time, or changes its type, instructor, spots, duration or off-peak mark. Only the fields you send change. Dates that already have bookings stay at the old time. Acts on one venue, given its address and access key.
| Name | Type | Req | Description |
|---|---|---|---|
| access_key | string | yes | The venue’s access key. |
| address | string | yes | The venue’s address name, the "name" in name.bookare.app. |
| class_type_id | string | – | – |
| duration_minutes | integer | – | Optional, default 60 (15-240). |
| instructor_id | string | – | Optional. Id of an instructor. |
| off_peak | boolean | – | Optional. Marks the class as off-peak. |
| spots | integer | – | Optional. Defaults to the class type’s spots (1-50). |
| time | string | – | Start time in the venue’s local time, HH:MM (24h). |
| weekday | integer | – | 0 = Monday … 6 = Sunday. |
| weekly_class_id | string | yes | Id of the weekly class on the timetable. |
No output schema declared.
No examples provided.
How do I install the Bookare MCP server?
Bookare is a hosted endpoint at https://bookare.app/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 · bookare.app
claude mcp add --transport http app-bookare-bookare 'https://bookare.app/mcp'
What is the Bookare MCP server?
Bookare is an MCP server listed in the public MCP registry as app.bookare/bookare. Online booking for gyms, salons, restaurants and stays. No commission, free plan. Set up by your AI. This page covers its hosted endpoint (https://bookare.app/mcp).
Is the Bookare MCP server safe to use?
Bookare scores 64 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 Bookare MCP server expose?
Bookare exposes 60 tools: list_business_types, check_address, get_plans, create_venue, get_venue, and 55 more. Their descriptions and schemas cost roughly 9,014 tokens of context every time the server is loaded.
Does the Bookare MCP server require authentication?
No. We connected to Bookare without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Bookare MCP server still maintained?
Bookare is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Bookare MCP server?
VerifyMCP ran 13 checks on Bookare, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.