Upsalt Booking
REMOTE · AI.UPSALT.IO
Search Upsalt venues, check availability, and book, view, or cancel a reservation.
Available components
Last scanned (7 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 23 Oct 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel-booking). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 841 tokens (~168/item across 5 items; 5 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Aug 26 0
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 23 Oct 2026 · Probed https://ai.upsalt.io/mcp/booking
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ai.upsalt.io | CN=YE2,O=Let's Encrypt,C=US | 16 Aug 2026 | 14 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 647c3ba97f3b43ed718f12af4d3c2e93b0f |
| SANs: ai.upsalt.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ai.upsalt.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| upsalt.io. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai.upsalt.io/mcp/booking | Verified | 200 | |
| http (plaintext) | http://ai.upsalt.io/mcp/booking | Inconclusive | 405 |
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 →
cancel-booking Cancel Booking ~52
Cancel an existing booking using the management token returned by create-booking. This action is irreversible; confirm with the guest before calling it.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The booking management token returned by create-booking. |
No output schema declared.
No examples provided.
create-booking Create Booking ~431
Create a booking for a company as a guest. Requires a date (YYYY/MM/DD), an hour and shift_id obtained from list-available-slots, and the guest contact details. On success, returns the reservation details including a token that can be used with get-booking-info and cancel-booking.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | yes | Number of adults. |
| babies | integer | – | Number of babies. |
| children | integer | – | Number of children. |
| city | string | – | Guest city. |
| company_id | integer | yes | The company id, as returned by the find-company tool. |
| country | string | – | Guest country. |
| date | string | yes | Booking date in YYYY/MM/DD format (e.g. 2026/07/20). Note the slashes. |
| string | yes | Guest email address. The booking confirmation and management token are sent here. | |
| gluten_free | boolean | – | Whether the party needs gluten-free options. |
| guest_token | string | – | Existing guest token, if the guest has booked before. |
| highchair | integer | – | Number of highchairs. |
| hour | string | yes | Booking hour in HH:MM format, taken from list-available-slots. |
| latitude | number | – | Guest latitude, if known. |
| longitude | number | – | Guest longitude, if known. |
| message | string | – | Optional message for the business. |
| name | string | yes | Guest first name. |
| nuts_allergy | boolean | – | Whether the party has a nut allergy. |
| optin | integer | – | Marketing opt-in flag (1 or 0). |
| pets | integer | – | Number of pets. |
| phone | string | yes | Guest phone number. |
| pushchair | integer | – | Number of pushchairs. |
| shift_id | integer | yes | The shift id, taken from list-available-slots. |
| surname | string | yes | Guest last name. |
| vegan | boolean | – | Whether the party includes vegan guests. |
| vegetarian | boolean | – | Whether the party includes vegetarian guests. |
| wheelchair | integer | – | Number of wheelchairs. |
No output schema declared.
No examples provided.
find-company Find Company ~73
Find a company by its slug and return its public profile: services, opening hours, and booking configuration. Use this first to obtain the company_id needed by the other tools.
| Name | Type | Req | Description |
|---|---|---|---|
| business_type | string | – | Optional business type filter. |
| slug | string | yes | The company slug, as found in its booking page URL. |
No output schema declared.
No examples provided.
get-booking-info Get Booking Info ~58
Retrieve the details of an existing booking using the management token returned by create-booking.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | yes | The company id the booking belongs to. |
| token | string | yes | The booking management token returned by create-booking. |
No output schema declared.
No examples provided.
list-available-slots List Available Slots ~89
List the available booking slots for a company on a given date. Returns shifts and bookable hours; use the shift_id and hour when creating a booking.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | yes | The company id, as returned by the find-company tool. |
| date | string | yes | The date to check, in YYYY-MM-DD format (e.g. 2026-07-20). |
No output schema declared.
No examples provided.
How do I install the Upsalt Booking MCP server?
Upsalt Booking is a hosted endpoint at https://ai.upsalt.io/mcp/booking, 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 · ai.upsalt.io
claude mcp add --transport http everyways-upsalt-booking 'https://ai.upsalt.io/mcp/booking'
What is the Upsalt Booking MCP server?
Upsalt Booking is an MCP server listed in the public MCP registry as io.github.Everyways/upsalt-booking. Search Upsalt venues, check availability, and book, view, or cancel a reservation. This page covers its hosted endpoint (https://ai.upsalt.io/mcp/booking).
Is the Upsalt Booking MCP server safe to use?
Upsalt Booking 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 Upsalt Booking MCP server expose?
Upsalt Booking exposes 5 tools: find-company, list-available-slots, create-booking, get-booking-info, cancel-booking. Their descriptions and schemas cost roughly 703 tokens of context every time the server is loaded.
Does the Upsalt Booking MCP server require authentication?
No. We connected to Upsalt Booking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Upsalt Booking MCP server still maintained?
Upsalt Booking is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.