Vayancy TravelOS
REMOTE · VAYANCY-AGENTIC-BRAIN-PRODUCTION.UP.RAILWAY.APP
Mediterranean luxury villa booking rail with real-time PMS inventory & direct Stripe holds.
Available components
Last scanned (23 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
Recent critical change
Authorization (13 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 (cancel_booking). 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
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3103 tokens (~344/item across 9 items; 9 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 Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +3
- Tool “cancel_booking” rewrote its description, which is the text the model reads security
- Tool “cancel_hold” rewrote its description, which is the text the model reads security
- Tool “check_availability” rewrote its description, which is the text the model reads security
- Tool “create_booking” rewrote its description, which is the text the model reads security
- Tool “create_hold” rewrote its description, which is the text the model reads security
- Tool “get_booking_details” rewrote its description, which is the text the model reads security
- Tool “get_guest_profile” rewrote its description, which is the text the model reads security
- Tool “get_rate_details” rewrote its description, which is the text the model reads security
- Tool “search_properties” rewrote its description, which is the text the model reads security
- Schema quality: 149 → 344 ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Schema quality: good → excellent functional
- “cancel_booking” reworded the description of “booking_id” cosmetic
- “cancel_booking” reworded the description of “guest_email” cosmetic
- “cancel_booking” reworded the description of “reason” cosmetic
- “cancel_hold” reworded the description of “hold_id” cosmetic
- “check_availability” reworded the description of “check_in” cosmetic
- “check_availability” reworded the description of “check_out” cosmetic
- “check_availability” reworded the description of “guests” cosmetic
- “check_availability” reworded the description of “unit_id” cosmetic
- “create_booking” reworded the description of “guest_email” cosmetic
- “create_booking” reworded the description of “guest_name” cosmetic
- “create_booking” reworded the description of “guest_phone” cosmetic
- “create_booking” reworded the description of “hold_id” cosmetic
- “create_booking” reworded the description of “idempotency_key” cosmetic
- “create_booking” reworded the description of “notes” cosmetic
- “create_hold” reworded the description of “check_in” cosmetic
- “create_hold” reworded the description of “check_out” cosmetic
- “create_hold” reworded the description of “guest_email” cosmetic
- “create_hold” reworded the description of “guests” cosmetic
- “create_hold” reworded the description of “unit_id” cosmetic
- “get_booking_details” reworded the description of “booking_id” cosmetic
- “get_booking_details” reworded the description of “guest_email” cosmetic
- “get_guest_profile” reworded the description of “guest_email” cosmetic
- “get_rate_details” reworded the description of “check_in” cosmetic
- “get_rate_details” reworded the description of “check_out” cosmetic
- “get_rate_details” reworded the description of “guests” cosmetic
- “get_rate_details” reworded the description of “unit_id” cosmetic
- “search_properties” reworded the description of “amenities” cosmetic
- “search_properties” reworded the description of “check_in” cosmetic
- “search_properties” reworded the description of “check_out” cosmetic
- “search_properties” reworded the description of “guests” cosmetic
- “search_properties” reworded the description of “location” cosmetic
- “search_properties” reworded the description of “max_price” cosmetic
- 15 Nov 26 0
- Tool “cancel_booking” rewrote its description, which is the text the model reads security
- Tool “get_booking_details” rewrote its description, which is the text the model reads security
- “cancel_booking” added an optional parameter “guest_email” cosmetic
- “get_booking_details” added an optional parameter “guest_email” cosmetic
- 14 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_availability” rewrote its description, which is the text the model reads security
- Tool “search_properties” rewrote its description, which is the text the model reads security
- Tool “search_properties” changed its title: Search Mediterranean Villas & Hotels → Search Luxury Villas, Hotels & Beachfront Rentals (Greece & Cyprus) cosmetic
- 13 Nov 26 +3
- Authorization: unverified → fail ▼ critical
- The server changed its declared name: vayancy-travelos → Vayancy TravelOS security
- Tool “cancel_booking” is now declared destructive security
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: 100 functional
- New prompt “compare_ota_savings” functional
- New prompt “find_luxury_villa” functional
- New prompt “hold_reservation” functional
- New prompt “mediterranean_charter” functional
- Tool “cancel_booking” changed its title: Cancel Confirmed Booking cosmetic
- Tool “cancel_hold” changed its title: Release Active Inventory Hold cosmetic
- Tool “check_availability” changed its title: Check Live PMS Availability cosmetic
- Tool “create_booking” changed its title: Confirm Booking via Active Hold cosmetic
- Tool “create_hold” changed its title: Create 15-Minute Inventory Hold & Stripe Checkout cosmetic
- Tool “get_booking_details” changed its title: Get Booking Details cosmetic
- Tool “get_guest_profile” changed its title: Get Guest Booking History cosmetic
- Tool “get_rate_details” changed its title: Get Transparent Direct Rates cosmetic
- Tool “search_properties” changed its title: Search Mediterranean Villas & Hotels cosmetic
- 12 Nov 26 56
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://vayancy-agentic-brain-production.up.railway.app/mcp/hospitality/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| 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 vayancy-agentic-brain-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| railway.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; includeSubDomains |
| 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 |
|---|---|---|---|---|
| sse | https://vayancy-agentic-brain-production.up.railway.app/mcp/hospitality/sse | Verified | 200 | |
| http (plaintext) | http://vayancy-agentic-brain-production.up.railway.app/mcp/hospitality/sse | HTTPS enforced | 301 | https://vayancy-agentic-brain-production.up.railway.app/mcp/hospitality/sse |
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 Confirmed Booking ~310
Cancel a confirmed reservation (`booking_id`) in both Vayancy and the property owner's PMS. When to use: - Use ONLY when a reservation has already been confirmed via `create_booking` (you have a `booking_id`) and the guest or property manager requests cancellation. - To modify dates or switch villas on an existing confirmed booking, cancel the existing reservation with `cancel_booking` and place a new hold with `create_hold`. When NOT to use: - Do NOT use `cancel_booking` to release an unconfirmed 15-minute inventory hold before booking—use `cancel_hold` with `hold_id` instead. - Do NOT use `cancel_booking` just to check whether a booking is active—use `get_booking_details` instead. Args: booking_id: Vayancy booking ID from create_booking reason: Cancellation reason guest_email: Guest email used when booking (required for public ownership verification) Returns: JSON object with `booking_id`, `pms_booking_id`, `success` (boolean), and updated `status` (`"cancelled"` or `"cancel_failed"`).
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | string | yes | Confirmed Vayancy booking ID returned by `create_booking`. |
| guest_email | string | – | Lead guest email address used when booking (required on public sessions to verify ownership before cancellation). |
| reason | string | – | Optional reason for cancelling the reservation (recorded in PMS notes). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cancel_hold Release Active Inventory Hold ~159
Release an active, unconfirmed 15-minute inventory hold (`hold_id`) without creating a booking. When to use: - Use when a traveler decides not to proceed with a held villa or wants to release a `hold_id` before completing checkout or calling `create_booking`. When NOT to use: - Do NOT use `cancel_hold` to cancel an already confirmed reservation—use `cancel_booking` with the confirmed `booking_id` instead. Args: hold_id: Hold ID from create_hold Returns: JSON object with `success` (boolean), `hold_id`, and status `message`.
| Name | Type | Req | Description |
|---|---|---|---|
| hold_id | string | yes | Active 15-minute inventory hold ID returned by `create_hold`. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
check_availability Check Live PMS Availability ~348
Check real-time PMS calendar availability for one specific villa or suite (`unit_id`). Directly queries the property management system adapter (WebHotelier, Avantio, HostHub, Lodgify, Hostify) to verify whether a known unit is open for a specific date range and guest count. When to use: - Use when you already have a specific `unit_id` (for example, when a traveler shifts dates or guest count on a shortlisted villa) and want a fast boolean availability check. When NOT to use: - Do NOT use for initial discovery across a destination or island—use `search_properties` instead. - Do NOT use when you need itemized nightly pricing, cleaning fees, taxes, and cancellation policy—use `get_rate_details` instead. Args: unit_id: The unit_id from search_properties results (e.g. "n19trsyt73" or PMS unit identifier) check_in: Arrival date YYYY-MM-DD check_out: Departure date YYYY-MM-DD guests: Number of guests Returns: JSON object confirming `available` (boolean), `unit_id`, `check_in`, `check_out`, `guests`, and optional `error`.
| Name | Type | Req | Description |
|---|---|---|---|
| check_in | string | yes | Arrival date in ISO 8601 format (YYYY-MM-DD). |
| check_out | string | yes | Departure date in ISO 8601 format (YYYY-MM-DD). |
| guests | integer | yes | Total number of guests staying at the property. |
| unit_id | string | yes | Unique property unit identifier (`unit_id` from `search_properties` or PMS unit ID). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_booking Confirm Booking via Active Hold ~407
Finalize and confirm a reservation in the property's PMS using an active 15-minute hold (`hold_id`). The property owner is the merchant of record with zero OTA intermediaries. When to use: - Use after creating an active hold via `create_hold` to commit the reservation into the PMS (when `payment_required=False` or when authenticated with a tenant API key). When NOT to use: - Do NOT call `create_booking` without first locking inventory via `create_hold`. - When `create_hold` returns `payment_required=True` on a public session, direct the guest to the `checkout_url` instead of calling `create_booking` before payment. Args: hold_id: Hold ID from create_hold (must be active, not expired) guest_name: Full name of primary guest guest_email: Guest email guest_phone: Guest phone (international format, e.g. +306912345678) idempotency_key: Unique key from caller — prevents double-booking on retry notes: Optional special requests Returns: JSON object with `success`, `booking_id`, `pms_booking_id`, `unit_id`, `check_in`, `check_out`, `status`, and confirmation dispatch flags.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_email | string | yes | Primary guest email address for confirmation and pre-arrival check-in. |
| guest_name | string | yes | Full legal name of the lead guest. |
| guest_phone | string | yes | Guest phone/WhatsApp number in international E.164 format (e.g. '+306912345678'). |
| hold_id | string | yes | Active 15-minute inventory hold ID returned by `create_hold`. |
| idempotency_key | string | yes | Caller-generated unique key (UUID or string) to guarantee idempotency and prevent duplicate bookings on retry. |
| notes | string | – | Optional special requests, arrival notes, or flight details. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_hold Create 15-Minute Inventory Hold & Stripe Checkout ~359
Place an exclusive 15-minute inventory hold on a villa (`unit_id`) and generate a direct Stripe Checkout URL. Locks the property's calendar for 15 minutes so no conflicting booking can occur while the guest completes payment. When to use: - Use when the guest is ready to lock a specific `unit_id` and dates after reviewing `search_properties` or `get_rate_details`. - Always call `create_hold` before calling `create_booking`. When NOT to use: - Do NOT use while browsing or comparing properties—use `search_properties` or `get_rate_details` instead. - If the guest decides not to proceed after a hold is created, call `cancel_hold` (not `cancel_booking`) to release the hold. Args: unit_id: The unit_id returned by search_properties check_in: Arrival date YYYY-MM-DD check_out: Departure date YYYY-MM-DD guests: Number of guests guest_email: Primary guest email address to bind the reservation hold Returns: JSON object with `hold_id`, `expires_at` timestamp, `payment_required` flag, `next_step`, and direct Stripe `checkout_url`.
| Name | Type | Req | Description |
|---|---|---|---|
| check_in | string | yes | Arrival date in ISO 8601 format (YYYY-MM-DD). |
| check_out | string | yes | Departure date in ISO 8601 format (YYYY-MM-DD). |
| guest_email | string | yes | Primary guest email address to bind the 15-minute inventory hold and payment receipt. |
| guests | integer | yes | Total number of guests staying at the property. |
| unit_id | string | yes | Unique property unit identifier (`unit_id` returned by `search_properties`). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_booking_details Get Booking Details ~279
Retrieve live reservation status, stay dates, unit details, and total amount for one specific confirmed booking (`booking_id`). When to use: - Use when a guest or agent has a specific `booking_id` and wants to check its confirmation status, PMS reference, dates, or total amount. When NOT to use: - Do NOT use `get_booking_details` to look up a guest's multi-stay booking history across a property portfolio by email alone—authenticated tenants should use `get_guest_profile` instead. - Do NOT use before a booking is confirmed—to check pricing on an unbooked unit, use `get_rate_details`. Args: booking_id: Vayancy booking ID returned by create_booking guest_email: Guest email used when booking (required for public ownership verification) Returns: JSON object with `booking_id`, `pms_booking_id`, `status`, `unit_id`, `unit_name`, `check_in`, `check_out`, `guests`, `guest_name`, `guest_email`, `total_amount`, and `currency`.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | string | yes | Confirmed Vayancy booking ID returned by `create_booking`. |
| guest_email | string | – | Lead guest email address used when booking (required on public sessions to verify booking ownership). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_guest_profile Get Guest Booking History ~267
Retrieve a guest's multi-stay booking history (up to 10 most recent reservations) within an authenticated tenant's property portfolio. Requires tenant authentication via the `X-Tenant-Key` header. When to use: - Use ONLY when an authenticated property manager or tenant agent (`X-Tenant-Key` header present) needs to list all past and upcoming stays for a returning guest by `guest_email`. When NOT to use: - Do NOT use `get_guest_profile` on public unauthenticated guest sessions (it will reject requests without `X-Tenant-Key`). - Do NOT use `get_guest_profile` to look up a single reservation's live PMS details by booking ID—use `get_booking_details` with `booking_id` and `guest_email` instead. Args: guest_email: Guest email address Returns: JSON object with `guest_email`, `total_bookings` count, and `bookings` array (`booking_id`, `pms_booking_id`, `unit_id`, `check_in`, `check_out`, `guests`, `status`, `booked_at`).
| Name | Type | Req | Description |
|---|---|---|---|
| guest_email | string | yes | Guest email address to look up past and upcoming reservations within the authenticated tenant's portfolio. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_rate_details Get Transparent Direct Rates ~341
Get the itemized direct-rate quote and cancellation policy for one specific villa (`unit_id`) and date range. Fetches exact live pricing from the property owner's PMS including nightly base rate, subtotal, cleaning fees, local tourist taxes, gross total in EUR, minimum-stay rule, and cancellation policy. When to use: - Use after the traveler selects a specific `unit_id` from `search_properties` to present the full itemized price quote and cancellation terms before calling `create_hold`. When NOT to use: - Do NOT use for broad destination search—use `search_properties` instead. - Do NOT use just to check whether dates are open without needing price itemization—use `check_availability` instead. Args: unit_id: The unit_id from search_properties results check_in: Arrival date YYYY-MM-DD check_out: Departure date YYYY-MM-DD guests: Number of guests Returns: JSON object with `nights`, `currency`, itemized `breakdown` (`base_rate_per_night`, `subtotal`, `cleaning_fee`, `tax`), `gross_total`, `cancellation_policy`, and `min_stay_nights`.
| Name | Type | Req | Description |
|---|---|---|---|
| check_in | string | yes | Arrival date in ISO 8601 format (YYYY-MM-DD). |
| check_out | string | yes | Departure date in ISO 8601 format (YYYY-MM-DD). |
| guests | integer | yes | Total number of guests staying at the property. |
| unit_id | string | yes | Unique property unit identifier (`unit_id` returned by `search_properties`). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_properties Search Luxury Villas, Hotels & Beachfront Rentals (Greece & Cyprus) ~563
Search verified luxury beachfront villas, boutique hotels, and retreats across Greece and Cyprus (including Protaras, Ayia Napa, Mykonos, Santorini, Lefkada, Meganisi, Crete). Performs a real-time two-phase search: first filters verified Mediterranean properties from the Vayancy direct catalog, then executes live parallel PMS availability and base-rate checks directly against property management systems (WebHotelier, Avantio, HostHub, Lodgify, Hostify). When to use: - Use as the initial discovery step when a traveler asks for available villas or hotels in a destination/region and does not yet have a specific `unit_id`. When NOT to use: - Do NOT use `search_properties` to re-check availability for a single known property when the guest changes dates—use `check_availability` with that property's `unit_id` instead. - Do NOT use `search_properties` to get an itemized quote with cleaning fees, tourist taxes, and cancellation policy—use `get_rate_details` with the chosen `unit_id` instead. Args: location: Island, destination, or region (e.g. "Mykonos", "Santorini", "Lefkada", "Crete", "Athens Riviera", "Paros", "Corfu", "Cyprus", "Protaras") check_in: Arrival date YYYY-MM-DD check_out: Departure date YYYY-MM-DD guests: Number of guests max_price: Optional maximum nightly base rate in EUR amenities: Optional comma-separated filters: pool, sea_view, ac, bbq, beachfront, wifi, jacuzzi, gym, chef Returns: JSON object with `properties_found` count and `properties` list containing each available villa's `unit_id`, `name`, `location`, `base_rate` in EUR, `amenities`, `photos`, and `min_stay`.
| Name | Type | Req | Description |
|---|---|---|---|
| amenities | – | – | Optional comma-separated amenity filters (e.g. 'pool,sea_view,beachfront,wifi,ac,bbq,jacuzzi'). |
| check_in | string | yes | Arrival date in ISO 8601 format (YYYY-MM-DD). |
| check_out | string | yes | Departure date in ISO 8601 format (YYYY-MM-DD). |
| guests | integer | yes | Total number of guests staying at the property. |
| location | string | yes | Destination island, town, or region (e.g. 'Lefkada', 'Meganisi', 'Mykonos', 'Santorini', 'Crete', 'Cyprus', 'Protaras'). |
| max_price | – | – | Optional maximum nightly base rate in EUR. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Vayancy TravelOS MCP server?
Vayancy TravelOS is a hosted endpoint at https://vayancy-agentic-brain-production.up.railway.app/mcp/hospitality/sse, 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 · vayancy-agentic-brain-production.up.railway.app
claude mcp add --transport http nikoskalyvas-vayancy-travelos 'https://vayancy-agentic-brain-production.up.railway.app/mcp/hospitality/sse'
What is the Vayancy TravelOS MCP server?
Vayancy TravelOS is an MCP server listed in the public MCP registry as io.github.nikoskalyvas/vayancy-travelos. Mediterranean luxury villa booking rail with real-time PMS inventory & direct Stripe holds. This page covers its hosted endpoint (https://vayancy-agentic-brain-production.up.railway.app/mcp/hospitality/sse).
Is the Vayancy TravelOS MCP server safe to use?
Vayancy TravelOS 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 Vayancy TravelOS MCP server expose?
Vayancy TravelOS exposes 9 tools: search_properties, check_availability, get_rate_details, create_hold, create_booking, and 4 more. Their descriptions and schemas cost roughly 3,033 tokens of context every time the server is loaded.
Does the Vayancy TravelOS MCP server require authentication?
No. We connected to Vayancy TravelOS without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vayancy TravelOS MCP server still maintained?
Vayancy TravelOS 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 Vayancy TravelOS MCP server?
VerifyMCP ran 13 checks on Vayancy TravelOS, 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.