Bluerails Hotels
REMOTE · 402.BLUERAILS.COM
Live hotel search and booking for AI agents in DACH, the UK and 10 US cities.
Available components
Last scanned (20 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 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 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 (hotel_reserve). 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 Usability25
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 5386 tokens (~1795/item across 3 items; 2 tools + 1 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
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.
- 21 Nov 26 +1
- Resource “Hotel search results” now points somewhere else: ui://bluerails/rooms.4acbaf6c50c0.html → ui://bluerails/rooms.034c11107054.html security
- Tool “list_hotels” rewrote its description, which is the text the model reads security
- 20 Nov 26 0
- Resource “Hotel search results” now points somewhere else: ui://bluerails/rooms.b3fe761b828c.html → ui://bluerails/rooms.4acbaf6c50c0.html security
- 19 Nov 26 +1
- Tool “list_hotels” rewrote its description, which is the text the model reads security
- 17 Nov 26 0
- Tool “hotel_reserve” rewrote its description, which is the text the model reads security
- Tool “list_hotels” rewrote its description, which is the text the model reads security
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
- Resource “Hotel search results” now points somewhere else: ui://bluerails/rooms.691039887dbe.html → ui://bluerails/rooms.b3fe761b828c.html security
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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://402.bluerails.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.bluerails.com | CN=Amazon RSA 2048 S19,O=Amazon,C=US | 13 Nov 2026 | 31 May 2027 | RSA 2048 | SHA256-RSA | 40491aeb41eb6c240ea0711d34173c3d |
| SANs: *.bluerails.com, www.publishers402.com, bluerails402.com, www.hotels402.com, discovery.bluerails402.com, publishers402.com, www.bluerails402.com, hotels402.com | ||||||
| CN=Amazon RSA 2048 S19,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 8 Jul 2026 | 7 Jul 2029 | RSA 2048 | SHA256-RSA | 3e66530c008bab6b9a6d90c1f0d323dac30eeeca |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of 402.bluerails.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| bluerails.com. | 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; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; connect-src 'self' https://api.eu.amplitude.com https://sr-client-cfg.eu.amplitude.com; frame-ancestors 'none'; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://402.bluerails.com/mcp | Verified | 200 | |
| http (plaintext) | http://402.bluerails.com/mcp | HTTPS enforced | 301 | https://402.bluerails.com/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 →
hotel_reserve Book a room ~852
Book a hotel room. Works for ANY offer `list_hotels` gave you an `offerId` for — there is no separate check to make first, so pass the offer the guest chose. Pass that offer’s `offerId` exactly as you were given it — it names the hotel, room, rate, stay and price, which is why none of those are separate arguments. It expires after 30 minutes; if it has expired or the hotel has raised the price since, nothing is booked — get a fresh one by calling `list_hotels` with that same `offerId`, which re-prices just that room rather than showing the guest the whole property again. TWO OUTCOMES, and the reply tells you which. `confirmationNumber` means the room is booked: give the guest the number and tell them they pay the hotel at the desk — nothing has been charged. `paymentUrl` means the room is NOT held yet: give the guest that link to pay, their card is HELD rather than charged, and the booking is placed once they have paid. Set `acceptedTerms` only after the guest has agreed to book this rate. Show them that rate’s cancellation terms where `list_hotels` gave any; where its `cancelTerms` was null we hold none, so say so and that the hotel’s own terms apply, then set it once they agree on that basis — a blank is NOT a reason to refuse the booking. Ask the guest for their own phone number and billing address — the hotel puts them on the reservation and uses them to reach the guest. Never invent them. If a call comes back ambiguous, do NOT call again — a reservation may already exist. If it comes back with `retryable` true, an earlier call for this guest is still running: call again with the same `offerId` after `retryAfterSeconds` to get its result.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptedTerms | boolean | yes | TRUE only when the guest has agreed to book this rate. Where `list_hotels` gave that rate cancellation terms, show them first and get the agreement to those. Where its `cancelTerms` was null WE HOLD… |
| guestCity | string | yes | – |
| guestCountry | string | yes | Two-letter country code, e.g. DE, AT, CH. The country the guest lives in, not the one they are travelling to. |
| guestEmail | string | yes | The hotel sends its confirmation here. It is the guest's own address, never yours. An example or placeholder address such as name@example.com is refused and nothing is reserved: ask the guest for the… |
| guestGivenName | string | yes | – |
| guestLastName | string | yes | – |
| guestPhone | string | yes | The guest's phone number, in any format the guest gives it. |
| guestPostal | string | yes | Postal code. |
| guestSalutation | string | – | How the guest is addressed, in their own words. Only pass what the guest told you; never guess from a name. |
| guestStreet | string | yes | Street and house number. |
| guestStreetNo | string | – | House number, when the guest gives it separately from the street. |
| offerId | string | yes | The `offerId` of the exact room and rate the guest chose, copied from `list_hotels` unchanged. It names the hotel, the room, the rate, the stay, the party and the price the guest was shown, so none o… |
| Name | Type | Req | Description |
|---|---|---|---|
| bookingReference | string | – | OUR reference for this booking — the number the guest quotes to US. Different from `confirmationNumber`, which is the hotel’s and is what they quote at the property. Absent only when the booking coul… |
| checkIn | string | – | – |
| checkOut | string | – | – |
| confirmationNumber | string | – | Present ONLY when a room was actually booked. The hotel’s own reference — give it to the guest and tell them to keep it. |
| error | string | – | Present ONLY when nothing was booked. It carries the reason in words a guest can hear and, on a refusal you can recover from, the call to make next. Give the guest the reason; act on the rest yoursel… |
| hotel | string | – | The property that took the booking. |
| payment | string | – | What the guest owes and to whom. Nothing is ever charged here. |
| paymentUrl | string | – | OUR payment page, and the room is NOT reserved until the guest has paid. Their card is HELD, not charged. Present only when nothing was booked yet and payment is what gets it booked. |
| reason | string | – | Machine-readable cause of a refusal: terms-not-accepted, guest-email-placeholder, offer-malformed, offer-bad-signature, offer-expired, offer-not-enabled, offer-not-bookable, listing-not-found, not-co… |
| retryAfterSeconds | integer | – | With `retryable`: how many seconds to wait before calling again with the same `offerId`. |
| retryable | boolean | – | True only on `in-progress` while an earlier call for this guest and offer is still running: call again with the SAME `offerId` after `retryAfterSeconds` to get its result. |
| tellTheGuest | string | – | Wording meant for the guest rather than for you. On an ambiguous outcome it says NOT to book again — pass that on rather than retrying. |
No examples provided.
list_hotels Find and price hotels ~4,528
A PROPERTY THE GUEST NAMED NEEDS NO BUDGET. This is the one exception to ASK BEFORE YOU SEARCH below. When the guest names the hotel they want ("book Schwitzer's 13-15 Dec for 2"), do NOT ask what they want to spend and do not fill a budget in: send its name as `query` with `checkIn`, `checkOut` and `adults` and leave `maxPricePerNight` out. A name matching at most 3 properties is priced for the stay with no budget applied; a budget below the hotel's price would only hide the hotel they asked for. A broader name is refused with nothing priced — send the fuller name, add its town in `city`, or ask the guest for a budget and search instead. Every other request (a place, a kind of hotel, "somewhere near Munich") is a fresh search: ask for the budget as below. Search hotel properties in Germany, Austria, Switzerland, the United Kingdom and the United States, and price them for a stay in the same call. ASK BEFORE YOU SEARCH. Five things are required and this tool answers nothing without them: `checkIn`, `checkOut`, `adults`, `maxPricePerNight` and the `currency` that budget is in. "Hotels in Berlin for a couple" is not yet a search — it names a place and a party and nothing else, so ask which nights they want, who is coming — adults AND any children, by age — and roughly what they want to spend, in ONE message, and search once they answer. Never fill these in for them: dates you chose are not their dates, and a budget read off "cheap" or off a star rating hides the very hotels they could have afforded. A call missing any of them comes back with no rows and a `hint` naming what is still to be asked. PLACES. Pass `city` with any place name we cover to get properties around it, nearest first, each with `distanceKm` — despite the name it takes a place of any size, so a village, a resort or a borough ("Silvaplana", "Wals", "Zell am See", "Brooklyn") works as well as a city. `radius` is a value with its unit — {"value": 10, "unit": "mi"} — so you never have to convert; it…
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | Adults in the party. REQUIRED — ask how many people are travelling. Properties price by party size, so a number you assumed prices a stay nobody asked for. "A couple" is two; anything vaguer is a que… |
| amenities | array | – | Facilities and house rules the property must ALL have — a hotel missing one is excluded, so every extra value narrows the result. Prefer this to naming an amenity in `query`: these are exact, while `… |
| checkIn | string | – | Arrival date, YYYY-MM-DD. REQUIRED — ask the guest for their dates before you search. Without them nothing can be priced and the answer would be a list of property names with no rooms, no prices and… |
| checkOut | string | – | Departure date, YYYY-MM-DD. REQUIRED, on the same terms as `checkIn` — ask the guest, never choose. |
| childrenAges | array | – | ONE ENTRY PER CHILD — their age, or `null` when you do not know it yet. Not a count: properties price a child by its age, and none may be invented. ASK WHETHER ANYONE UNDER 18 IS TRAVELLING, in the s… |
| city | string | – | Place to search around — any place name we cover, not just a city: a town, a village or a resort works, e.g. "Salzburg", "Munich", "Silvaplana", "Wals". Pass the place name ALONE, not a phrase: "Salz… |
| coordinates | object | – | A point to search around, for anywhere smaller than a town: a street, a landmark, a station, a junction, a named district. ESTIMATE IT YOURSELF for the place the guest named — `city` takes town names… |
| country | string | – | Filter by country: de=Germany, at=Austria, ch=Switzerland, us=United States, gb=United Kingdom |
| currency | string | – | THE CURRENCY OF `maxPricePerNight`, AND THE ONE THE ANSWER IS QUOTED BACK IN. ISO 4217 — `EUR`, `CHF`, `GBP`. REQUIRED on every search: send `EUR` when the guest gave you a euro figure, which is most… |
| language | string | – | The language to render the results card in — pass the language the guest is WRITING in, unless they have asked for another. A bare language code or a full BCP 47 tag both work ("de", "de-AT", "en-GB"… |
| limit | integer | – | How many results to return. Defaults to 10, and may not exceed 20; a larger value is rejected, never quietly reduced. |
| maxPricePerNight | integer | – | Budget per night, in the `currency` you send alongside it — BOTH ARE REQUIRED. TAKEN FROM A FIGURE THE GUEST GAVE YOU AND NOWHERE ELSE. Ask them roughly what they want to spend a night before you sea… |
| offerId | string | – | An `offerId` from an earlier answer, to get a fresh price for THAT room rather than searching again. Pass it when the guest has already chosen and you need a current handle — after `hotel_reserve` sa… |
| query | string | – | Free-text match over a property’s NAME, short description and tags. It is NOT a natural-language request: EVERY word you pass must appear on the same property, so each extra word narrows the result a… |
| radius | object | – | How far around `city` — or around `coordinates`, when you sent a point — to search, as a value and its unit: {"value": 10, "unit": "mi"}. Defaults to 20 km. May not exceed 100 km once converted; larg… |
| starRating | string | – | Filter by star rating: 1-star, 2-star, 3-star, 4-star, 5-star. A property can hold stars AND be a boutique hotel; ask for the two separately. |
| style | string | – | Filter by how the property presents itself: boutique. Independent of starRating — combine them to ask for both. |
| Name | Type | Req | Description |
|---|---|---|---|
| aboveBudget | array | – | Hotels we read real prices for that are OVER your `maxPricePerNight`, in the same shape as `priced`. Returned only when NOT ONE hotel fits the budget — when any does, dearer ones are left out entirel… |
| currency | string | – | The ISO code every price in this answer is in. |
| error | string | – | – |
| hint | string | – | One or more sentences about THIS answer that the rows cannot tell you: why a search came back empty, what a budget left out, how many properties were dropped because they told us they are full, and —… |
| language | string | – | The `language` that was asked for, echoed back verbatim. Absent when the caller passed none, which is how the card knows to follow the guest’s own app language instead. |
| maxPricePerNight | number | – | The budget `aboveBudget` was measured against — the GUEST’S OWN figure, in the `currency` you sent, like every price beside it. Echoed back so the results card can name it. Present only alongside `ab… |
| maxRadiusKm | number | – | – |
| nearestBeyondRadiusKm | number|null | – | Only when the search found nothing: how far the nearest property lies outside the radius. It is measured with your `query` still applied, so when you set one a null here does NOT mean the area is emp… |
| nearestSearchedToKm | number | – | How far the nearestBeyondRadiusKm search itself looked before giving up. |
| place | string | – | The `city` that was resolved, echoed back. |
| placeNotRecognised | string | – | The place name could not be resolved. NOT a statement that the place has no hotels. |
| priced | array | – | Only on a dated call. AT MOST your `limit` of them — 10 by default and never more than 20 — hotels we could get a real price for. Deliberately ordered — SHOW THEM IN THE ORDER YOU ARE GIVEN, and lead… |
| radiusUsedKm | number | – | The radius actually searched, in km, after converting the caller’s unit. |
| requestedRadiusKm | number | – | – |
| stay | object | – | The stay this answer priced, echoed back. Present only on a dated call — a view needs it to label the result and to turn a stay total into a per-night figure. |
| unpriced | array | yes | Matching properties we have NO price for. SHOW THEM IN THE ORDER YOU ARE GIVEN, and do not call any row the nearest. On a dated call that means: the property does not publish rates anywhere we can re… |
No examples provided.
How do I install the Bluerails Hotels MCP server?
Bluerails Hotels is a hosted endpoint at https://402.bluerails.com/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 · 402.bluerails.com
claude mcp add --transport http com-bluerails-hotels 'https://402.bluerails.com/mcp'
What is the Bluerails Hotels MCP server?
Bluerails Hotels is an MCP server listed in the public MCP registry as com.bluerails/hotels. Live hotel search and booking for AI agents in DACH, the UK and 10 US cities. This page covers its hosted endpoint (https://402.bluerails.com/mcp).
Is the Bluerails Hotels MCP server safe to use?
Bluerails Hotels scores 65 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 Bluerails Hotels MCP server expose?
Bluerails Hotels exposes 2 tools: list_hotels, hotel_reserve. Their descriptions and schemas cost roughly 5,380 tokens of context every time the server is loaded.
Does the Bluerails Hotels MCP server require authentication?
No. We connected to Bluerails Hotels without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Bluerails Hotels MCP server still maintained?
Bluerails Hotels 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 Bluerails Hotels MCP server?
VerifyMCP ran 14 checks on Bluerails Hotels, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.