com.stayker/1stay
REMOTE · MCP.STAYKER.COM · SCANNED AUG 3
Hotel booking MCP server. Search, book, and manage reservations across 250K+ properties worldwide.
Available components
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 →
Endpoint Security57
- 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
- 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 Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1673 tokens (~209/item across 8 items; 8 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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.stayker.com
claude mcp add --transport http com-stayker-1stay https://mcp.stayker.com/mcp
[mcp_servers.com-stayker-1stay] url = "https://mcp.stayker.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-stayker-1stay": {
"type": "remote",
"url": "https://mcp.stayker.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-stayker-1stay --url https://mcp.stayker.com/mcp --transport streamable-http
mcp_servers:
com-stayker-1stay:
url: "https://mcp.stayker.com/mcp" {
"mcpServers": {
"com-stayker-1stay": {
"type": "http",
"url": "https://mcp.stayker.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
- Tool “get_booking” rewrote its description, which is the text the model reads security
- Tool “resend_confirmation” rewrote its description, which is the text the model reads security
- Tool “cancel_booking” rewrote its description, which is the text the model reads security
- Schema quality: 187 → 209 ▼ functional
- “get_booking” added an optional parameter “verification_token” cosmetic
- “cancel_booking” added an optional parameter “cancellation_token” cosmetic
- “search_hotels” reworded the description of “location” cosmetic
- “resend_confirmation” dropped the optional parameter “updated_email” cosmetic
- “search_hotels” made “location” optional cosmetic
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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
- 26 Jul 26 61
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 3 Aug 2026 · Probed https://mcp.stayker.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.stayker.com | CN=WR3,O=Google Trust Services,C=US | 23 Jun 2026 | 21 Sept 2026 | RSA 2048 | SHA256-RSA | 63abed1bcba828e7094a413b76bc3663 |
| SANs: mcp.stayker.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
DNSSEC insecure
Validation of mcp.stayker.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| stayker.com. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.stayker.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.stayker.com/mcp | HTTPS enforced | 302 | https://mcp.stayker.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.
book_hotel ~269
Book a hotel room. Returns a secure checkout URL where the guest completes payment. Do not collect credit card numbers, payment info, or billing details in conversation. Guest pays the hotel directly. Their credit card statement shows the hotel name, not 1Stay. Hotel's own confirmation number. Loyalty points apply automatically. A 1Stay Booking Fee is added at checkout. Requires rate_code from get_hotel_details (expires in approximately 15 minutes). If expired, call get_hotel_details again for a fresh code.
| Name | Type | Req | Description |
|---|---|---|---|
| check_in | string | yes | Check-in date in YYYY-MM-DD format (e.g. 2026-05-06) |
| check_out | string | yes | Check-out date in YYYY-MM-DD format (e.g. 2026-05-07) |
| external_reference_id | string | — | Your unique reference ID for this booking (for idempotency and retrieval) |
| guest_email | string | yes | Guest email for confirmation |
| guest_name | string | yes | Guest full name |
| guests | integer | yes | Number of guests |
| hotel_id | string | yes | Hotel ID from search or details |
| rate_code | string | yes | Rate code from get_hotel_details — you MUST call get_hotel_details first to get a valid rate_code before booking |
No output schema declared.
No examples provided.
cancel_booking ~248
Cancel a hotel reservation. This is a two-step, server-confirmed action. Call 1 — provide guest first name, last name, and hotel confirmation number, and leave cancellation_token empty. The tool verifies the guest's identity and returns the cancellation terms (penalty, refundable amount, free-cancellation deadline, and a warning if the rate is non-refundable) plus a single-use cancellation_token. Nothing is cancelled yet. Call 2 — call again with the same details and the cancellation_token to execute the cancellation. The token is single-use and expires in about 10 minutes. Share the terms with the guest and get their confirmation before the second call. Non-refundable rates forfeit the full amount. Cancellation confirmation is emailed to the address on file.
| Name | Type | Req | Description |
|---|---|---|---|
| cancellation_token | string | — | Leave empty on the first call to preview the cancellation terms (penalty, refund, deadline) and receive a cancellation_token. Call again with that token to actually cancel. Single-use; expires in ~10… |
| confirmation_number | string | yes | Hotel confirmation number |
| first_name | string | yes | Guest first name on the reservation |
| last_name | string | yes | Guest last name on the reservation |
No output schema declared.
No examples provided.
get_booking ~174
Look up a reservation by booking ID (stk_bk_xxxx) or hotel confirmation number. Returns full booking details including hotel, dates, guest info, rate, and status. Guest-facing (anonymous) callers must first call lookup_booking to verify the guest's identity — that returns a verification_token, which you then pass here. Without a valid token, this tool returns no booking data. Developers authenticated with their own API key do not need a token; their access is scoped to their own bookings.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | string | yes | Booking ID (e.g. stk_bk_xxxx) or confirmation number |
| verification_token | string | — | Verification token returned by lookup_booking. Required for guest-facing (anonymous) lookups; obtain it by calling lookup_booking first. Not needed when authenticated with your own developer API key. |
No output schema declared.
No examples provided.
get_hotel_details ~217
Get rates and room details for a specific hotel. Returns room types, live rates, amenities, cancellation policies, and rate_codes required by book_hotel. Guest pays the hotel directly. Rates shown are what the hotel charges. A 1Stay Booking Fee is added at checkout. Loyalty points eligible. Room type notes: "Run of house" means the hotel assigns the room at check-in. "Suite" at select-service brands usually means a larger room with a sofa, not a separate bedroom. Non-refundable rates are cheaper but cannot be changed or canceled.
| Name | Type | Req | Description |
|---|---|---|---|
| check_in | string | yes | Check-in date in YYYY-MM-DD format (e.g. 2026-05-06) |
| check_out | string | yes | Check-out date in YYYY-MM-DD format (e.g. 2026-05-07) |
| guests | integer | — | Number of guests (default 2) |
| hotel_id | string | yes | Hotel ID from search results |
| rooms | integer | — | Number of rooms (default 1) |
No output schema declared.
No examples provided.
lookup_booking ~241
Look up a reservation by verifying the guest's identity. Returns the confirmation number and booking summary in conversation. Required before calling: 1. Guest full name (first and last) 2. At least one verification factor: email address used when booking, hotel confirmation number, or last 4 digits of the card used to book (check-in date also required for card verification) Do not call this tool without the guest's full name and at least one verification factor. If the guest cannot provide any verification factor, their reservation cannot be looked up — this is for the security of their booking. To resend the confirmation email, use resend_confirmation after verifying identity with this tool. To cancel, use cancel_booking.
| Name | Type | Req | Description |
|---|---|---|---|
| check_in_date | string | — | Check-in date (YYYY-MM-DD) — required with last_four_card |
| confirmation_number | string | — | Hotel confirmation number |
| string | — | Email address used when booking | |
| first_name | string | yes | Guest first name on the reservation |
| last_four_card | string | — | Last 4 digits of the card used to book |
| last_name | string | yes | Guest last name on the reservation |
No output schema declared.
No examples provided.
resend_confirmation ~96
Resend a hotel reservation confirmation email. Use after verifying the guest's identity with lookup_booking. The confirmation is always sent to the email address on the booking record. There is no way to redirect it to a different address. If the guest can no longer access that inbox, direct them to support at https://stayker.com/service — a different address cannot be set through this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_number | string | yes | Hotel confirmation number |
No output schema declared.
No examples provided.
search_hotels ~361
Search and book hotels by location and dates. Returns available properties with nightly rates across major brands, boutique, and independent hotels. Guest pays the hotel directly. Hotel's own confirmation number. Loyalty points apply.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_code | string | — | Two-letter hotel chain filter. MC=Marriott, HH=Hilton, HI=IHG, YX=Hyatt, BW=Best Western, WY=Wyndham, EL=Choice. Omit for boutique, independent, or unbranded searches. |
| check_in | string | yes | Check-in date in YYYY-MM-DD format (e.g. 2026-05-06). Must be today or later. |
| check_out | string | yes | Check-out date in YYYY-MM-DD format (e.g. 2026-05-07). Must be after check_in. |
| currency | string | — | Currency code (default USD) |
| cursor | string | — | Pagination cursor from previous search response |
| guests_per_room | integer | — | Guests per room (default 2) |
| latitude | number | — | Latitude — must be provided together with longitude |
| location | string | — | City, address, venue, or landmark (e.g. 'Nashville, TN' or 'Times Square, NYC'). Required unless latitude and longitude are both provided. |
| longitude | number | — | Longitude — must be provided together with latitude |
| max_results | integer | — | Max hotels to return, max 15 (default 10) |
| radius | integer | — | Search radius in miles (default 25, max 100) |
| rooms | integer | — | Number of rooms (default 1) |
| search_id | string | — | Search ID from previous results — pass with cursor for next page |
No output schema declared.
No examples provided.
search_tools ~67
List available 1Stay hotel booking tools. Filter by keyword: search, book, cancel, details. Omit keyword to list all tools.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | — | Keyword to filter tools (e.g. 'book', 'search', 'cancel'). Omit to list all tools. |
No output schema declared.
No examples provided.