booking MCP server
nz.wanakahaus/bookingwanakahaus.nzstreamable-httpv1.0.1Scanned
Book Wanaka Haus, an Architectural Passive home in Wānaka NZ. Availability, quotes, Stripe checkout.
5 tools: 1 can delete or cancel things, 1 do something that can't be undone, 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- No findings
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 booking MCP server can do
The booking MCP server is published by wanakahaus.nz, a domain the MCP Registry verified. It has 5 tools. It can delete or cancel things (1 tool: cancel_booking), do things that cannot be undone, such as sending, paying or publishing (search_availability) and create or change data (1 tool: create_booking). 2 tools only read.
1 tool can send data out of your system (search_availability).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.0.1.
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.
5 tools
Deletes or cancels 1Claude Code: deny
cancel_bookingCancel a Wanaka Haus booking under the published policy (full refund to 14 days before arrival, 50% to 7 days, none inside 7).No findings
Why it is in this group
- The name "cancel_booking" says "cancel": a word for removing or ending something.
Description, as the server wrote it Cancel a Wanaka Haus booking under the published policy (full refund to 14 days before arrival, 50% to 7 days, none inside 7). Requires the guest email the booking was made with.
Can't be undone 1Claude Code: ask
search_availabilityOpen and booked nights for Wanaka Haus (sleeps 8, Wānaka NZ) in a date window, up to 18 months ahead.Can send data outNo findings
Why it is in this group
- The name "search_availability" says "search": a word for reading.
- The description's first verb is "open": a word for a change.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it Open and booked nights for Wanaka Haus (sleeps 8, Wānaka NZ) in a date window, up to 18 months ahead. Ranges are check-in inclusive, check-out exclusive.
Changes things 1Claude Code: ask
create_bookingBook Wanaka Haus: atomically holds the dates for 30 minutes and returns a Stripe Checkout URL.No findings
Why it is in this group
- The name "create_booking" says "create": a word for a change.
Description, as the server wrote it Book Wanaka Haus: atomically holds the dates for 30 minutes and returns a Stripe Checkout URL. The booking confirms only when payment completes on that URL — give it to your user to pay (or pay with an agent wallet's one-time card). No account or API key needed.
Only reads 2Show 2 read-only tools
get_bookingStatus of a Wanaka Haus booking: held, confirmed, cancelled or lapsed.No findings
Why it is in this group
- The name "get_booking" says "get": a word for reading.
Description, as the server wrote it Status of a Wanaka Haus booking: held, confirmed, cancelled or lapsed.
get_quoteItemised NZD total for a stay at Wanaka Haus.No findings
Why it is in this group
- The name "get_quote" says "get": a word for reading.
Description, as the server wrote it Itemised NZD total for a stay at Wanaka Haus. Validates the stay rules (minimum nights, peak-season minimum, guest cap) and checks the dates are open, before you commit to a booking.
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.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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.
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, 19:16 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://wanakahaus.nz/api/mcp: tools/list returned 5 tools to an anonymous client, including cancel_booking (destructive), search_availability (irreversible), create_booking (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
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.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http booking https://wanakahaus.nz/api/mcpclaude mcp add --transport http booking https://wanakahaus.nz/api/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__booking__get_quote",
"mcp__booking__get_booking"
],
"ask": [
"mcp__booking__search_availability",
"mcp__booking__create_booking"
],
"deny": [
"mcp__booking__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 booking. Review it before you use it.
Capability tags behind 1 rule
- mcp__booking__search_availability outbound
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/nz.wanakahaus/booking/verify?hash=12ab44a7b5708ae14712e8984af1564cda4d1129a31bc3afee43e66785795ef2" | jq -e '.changed == false'Pinned hash 12ab44a7b570, from Nov 18, 2026, 22:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/nz.wanakahaus/booking/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/nz.wanakahaus/booking)Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.
booking MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the booking MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the booking MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: cancel_booking.
Can the booking MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: search_availability.
What tools does the booking MCP server have?
- 5 tools: 1 destructive, 1 irreversible, 1 write, 2 read. cancel_booking, search_availability, create_booking, get_quote and get_booking.
Does the booking MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the booking 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): search_availability.
Has the booking MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.