1stay MCP server
com.stayker/1staystayker.comstreamable-httpv1.0.0Scanned
Hotel booking MCP server. Search, book, and manage reservations across 250K+ properties worldwide.
8 tools: 1 can delete or cancel things, 1 do something that can't be undone, 1 change things and 5 only read.
- Reads private data · 1
- Reads text others write · 6
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the 1stay MCP server can do
The 1stay MCP server is published by stayker.com, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (1 tool: cancel_booking), do things that cannot be undone, such as sending, paying or publishing (resend_confirmation) and create or change data (1 tool: book_hotel). 5 tools only read.
1 tool reads private data (get_booking); 6 tools bring in text other people can write (search_hotels, get_hotel_details, book_hotel and 3 more); 1 tool can send data out of your system (resend_confirmation). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Deletes or cancels 1Claude Code: deny
cancel_bookingPrepare a hotel cancellation for completion on a secure 1Stay page.Reads text others write1 finding
Why it is in this group
- The name "cancel_booking" says "cancel": a word for removing or ending something.
- The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "cancel_booking" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "cancel_booking" says "cancel": a word for removing or ending something.
Description, as the server wrote it Prepare a hotel cancellation for completion on a secure 1Stay page. Verifies the guest's first name, last name, and hotel confirmation number, then returns the hotel policy classification and any cancellation deadline recorded with the reservation, plus a short-lived cancellation_url. 1Stay does not estimate a refund, credit, penalty, or hotel charge. Calling this tool never cancels the reservation. The guest must review the terms and select Cancel reservation on the secure page. A later verified booking-status lookup reporting status cancelled is the authoritative confirmation that the reservation was cancelled.
Annotations the server declares
- title: Cancel Booking
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Can't be undone 1Claude Code: ask
resend_confirmationResend a hotel reservation confirmation email.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "resend_confirmation" says "resend": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "resend_confirmation" says "resend": it sends or publishes something to other people.
Description, as the server wrote it Resend a hotel reservation confirmation email. Use either the confirmation number from a successful lookup_booking call, or the guest's full name and email address when they do not know their confirmation number, card last four, or check-in date. The email contains the hotel confirmation number the guest can then use with lookup_booking or cancel_booking. Recovery requests never reveal whether a reservation matched. The confirmation is sent only to the email address already on the booking record; there is no recipient override. Email changes are handled at https://stayker.com/service.
Annotations the server declares
- title: Resend Confirmation
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
Changes things 1Claude Code: ask
book_hotelBook exactly one hotel room.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Book exactly one hotel room. The first 1Stay release does not support multi-room searches or reservations. Returns a secure checkout URL. This tool accepts no guest identity or payment fields. Name, email, phone, and payment details are collected on the secure checkout page. Guest pays the hotel directly. Their credit card statement shows the hotel name, not 1Stay. Hotel's own confirmation number. Loyalty points apply automatically. The displayed total includes taxes and any applicable, itemized 1Stay Booking Fee. Requires a rate_code from get_hotel_details, valid approximately 15 minutes. Expired codes are rejected.
Annotations the server declares
- title: Book Hotel
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 5Show 5 read-only tools
get_bookingLook up a reservation exclusively by the hotel confirmation number shown in the guest's confirmation email.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_booking" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it Look up a reservation exclusively by the hotel confirmation number shown in the guest's confirmation email. Internal Stayker booking IDs are never accepted or disclosed by MCP. Returns full booking details including hotel, dates, guest info, rate, and status. Anonymous access requires a verification_token issued by lookup_booking and scoped to a single booking. Without a valid token, no booking data is returned. Developers authenticated with their own API key do not need a token; their access is scoped to their own bookings.
Annotations the server declares
- title: View Booking Details
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_hotel_detailsGet rates and room details for exactly one room at a specific hotel.Reads text others writeNo findings
Why it is in this group
- The name "get_hotel_details" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get rates and room details for exactly one room at a specific hotel. Returns room types, live rates, amenities, cancellation policies, and rate_codes required by book_hotel. Guest pays the hotel directly. Displayed totals include taxes and any applicable, itemized 1Stay Booking Fee. 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.
Annotations the server declares
- title: Hotel Details
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
lookup_bookingLook up a reservation by verifying the guest's identity.No findings
Why it is in this group
- The name "lookup_booking" says "lookup": a word for reading.
Description, as the server wrote it Look up a reservation by verifying the guest's identity. Returns the confirmation number and booking summary in conversation. Requires the guest's full name plus either the hotel confirmation number, or the booking email together with the last 4 digits of the card used to book. An email address alone is not enough. An optional check-in date can narrow repeat stays.
Annotations the server declares
- title: Find Reservation
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
search_hotelsSearch hotels by location and dates for exactly one room.Reads text others writeNo findings
Why it is in this group
- The name "search_hotels" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Search hotels by location and dates for exactly one room. Returns available properties with nightly rates across major brands, boutique, and independent hotels. The first 1Stay release supports one room per search and reservation. Guest pays the hotel directly. Hotel's own confirmation number. Loyalty points apply.
Annotations the server declares
- title: Search Hotels
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
search_toolsList available 1Stay hotel booking tools.No findings
Why it is in this group
- The name "search_tools" says "search": a word for reading.
Description, as the server wrote it List available 1Stay hotel booking tools. An optional keyword filters by search, book, cancel, or details; absence of a keyword returns all tools.
Annotations the server declares
- title: Search Tools
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__1stay__resend_confirmation"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:47 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.stayker.com/mcp: tools/list returned 8 tools to an anonymous client, including cancel_booking (destructive), resend_confirmation (irreversible), book_hotel (write)
Findings
Matches of fixed checks, with the text they matched.
- Warncancel_booking
The server marks "cancel_booking" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "cancel_booking" says "cancel": a word for removing or ending something.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http 1stay https://mcp.stayker.com/mcpclaude mcp add --transport http 1stay https://mcp.stayker.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__1stay__search_hotels",
"mcp__1stay__get_hotel_details",
"mcp__1stay__lookup_booking",
"mcp__1stay__get_booking",
"mcp__1stay__search_tools"
],
"ask": [
"mcp__1stay__book_hotel",
"mcp__1stay__resend_confirmation"
],
"deny": [
"mcp__1stay__cancel_booking"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as 1stay. Review it before you use it.
Capability tags behind 6 rules
- mcp__1stay__search_hotels untrusted-input
- mcp__1stay__get_hotel_details untrusted-input
- mcp__1stay__book_hotel untrusted-input
- mcp__1stay__resend_confirmation untrusted-input, outbound
- mcp__1stay__get_booking private-data, untrusted-input
- mcp__1stay__cancel_booking untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.stayker/1stay/verify?hash=0ecc59870d701a31ece32ea060cd2bdf2fc58426d1663678a019cabe5e2299fb" | jq -e '.changed == false'Pinned hash 0ecc59870d70, from Nov 11, 2026, 02:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.stayker/1stay/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.stayker/1stay)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:05 UTC.
1stay MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the 1stay MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the 1stay MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: cancel_booking.
Can the 1stay MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: resend_confirmation.
What tools does the 1stay MCP server have?
- 8 tools: 1 destructive, 1 irreversible, 1 write, 5 read. cancel_booking, resend_confirmation, book_hotel, search_hotels, get_hotel_details, lookup_booking, get_booking and search_tools.
Does the 1stay MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the 1stay MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): resend_confirmation.
Has the 1stay MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.