WEE WiLDS Booking MCP server
com.weewilds/bookingweewilds.comstreamable-httpv1.2.0Scanned
Live availability, pricing and booking enquiries for WEE WiLDS glamping pods, Cairngorms, Scotland.
4 tools: 1 do something that can't be undone and 3 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- 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 WEE WiLDS Booking MCP server can do
The WEE WiLDS Booking MCP server is published by weewilds.com, a domain the MCP Registry verified. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_inquiry), but cannot delete data. 3 tools only read.
1 tool reads private data (get_unit_details); 1 tool brings in text other people can write (send_inquiry); 1 tool can send data out of your system (send_inquiry). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
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, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.2.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.
4 tools
Can't be undone 1Claude Code: ask
send_inquiryEmail a booking inquiry to hello@weewilds.com on behalf of a guest.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "send_inquiry" says "send": 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 "send_inquiry" says "send": it sends or publishes something to other people.
Description, as the server wrote it Email a booking inquiry to hello@weewilds.com on behalf of a guest. Requires an access token (Authorization: Bearer header). Without one this tool sends nothing and returns the direct booking URL instead — send the guest there, or to hello@weewilds.com. Does NOT create an OwnerRez booking directly — the host will reply to the guest_email to confirm availability and arrange payment. Rate-limited to 5 inquiries per hour per client. Args: unit: One of "muckle-meadow-pod", "cosie-coorie-pod", "bb". check_in: Arrival date YYYY-MM-DD. check_out: Departure date YYYY-MM-DD, must be after check_in. guest_name: Guest's full name. guest_email: Valid email — the host replies here. guests: Number of guests (1–10). notes: Optional special requests (dietary, arrival time, etc.).
Annotations the server declares
- title: Send booking enquiry
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 3Show 3 read-only tools
get_availabilityCheck whether a WEE WiLDS unit is available for a date range.No findings
Why it is in this group
- The name "get_availability" says "get": a word for reading.
Description, as the server wrote it Check whether a WEE WiLDS unit is available for a date range. Args: unit: One of "muckle-meadow-pod", "cosie-coorie-pod", "bb". The "bb" slug returns per-room availability across all 4 B&B rooms. check_in: Arrival date in YYYY-MM-DD format. Must not be in the past. check_out: Departure date in YYYY-MM-DD format. Must be after check_in. Returns: For pods: {available, blocked_dates_in_range, name, url, ...}. For "bb": {rooms: [{room, available, ...}], any_room_available, ...}. On invalid input: {error, valid_units}.
Annotations the server declares
- title: Check availability
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_pricingGet the price range for a WEE WiLDS unit.No findings
Why it is in this group
- The name "get_pricing" says "get": a word for reading.
Description, as the server wrote it Get the price range for a WEE WiLDS unit. Returns a static min/max GBP range. Dynamic per-night quotes are not yet available — for an exact quote, use send_inquiry. Args: unit: One of "muckle-meadow-pod", "cosie-coorie-pod", "bb". check_in: Ignored for now (kept for forward-compat with dynamic pricing). check_out: Ignored for now (kept for forward-compat with dynamic pricing).
Annotations the server declares
- title: Get price range
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_unit_detailsGet full description, amenities, access notes, and policies for a unit.Reads private dataNo findings
Why it is in this group
- The name "get_unit_details" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "note": it reads notes.
Description, as the server wrote it Get full description, amenities, access notes, and policies for a unit. Args: unit: One of "muckle-meadow-pod", "cosie-coorie-pod", "bb". For "bb", returns the 4 rooms plus shared amenities. Returns: {unit, details: {name, type, size_sqm, amenities, rooms?, ...}, policies, location}.
Annotations the server declares
- title: Get unit details
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- 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.
1 path 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 write1
- 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__booking__send_inquiry"
]
}
}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:50 UTC, unchanged since Nov 13, 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
- 1
- 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 1 tool that changes things (1 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.weewilds.com/mcp/: tools/list returned 4 tools to an anonymous client, including send_inquiry (irreversible)
Posture changes
- Nov 13, 2026
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 1
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: no to not observed
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.
PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 1 (and 2 more).View diff
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 1
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: no to not observed
Tools4 changed.~4 changedView diff
- Changed:get_availabilityOnly readstitleinputSchemaannotations
- Changed:get_pricingOnly readstitleinputSchemaannotations
- Changed:get_unit_detailsOnly readstitleinputSchemaannotations
- Changed:send_inquiryCan't be undonetitleinputSchemaannotations
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http booking https://mcp.weewilds.com/mcp/claude mcp add --transport http booking https://mcp.weewilds.com/mcp/Run 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_availability",
"mcp__booking__get_pricing",
"mcp__booking__get_unit_details"
],
"ask": [
"mcp__booking__send_inquiry"
],
"deny": []
}
}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 2 rules
- mcp__booking__get_unit_details private-data
- mcp__booking__send_inquiry untrusted-input, 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/com.weewilds/booking/verify?hash=265a1a3d60c260bcc942b685baa7ce2630c8df12e9c3351ab3276c743baf6f4f" | jq -e '.changed == false'Pinned hash 265a1a3d60c2, from Nov 13, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.weewilds/booking/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.weewilds/booking)Source: MCP Registry. Synced Nov 13, 2026, 09:17 UTC.
WEE WiLDS Booking MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the WEE WiLDS Booking MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 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 WEE WiLDS Booking MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the WEE WiLDS Booking MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: send_inquiry.
What tools does the WEE WiLDS Booking MCP server have?
- 4 tools: 1 irreversible, 3 read. send_inquiry, get_availability, get_pricing and get_unit_details.
Does the WEE WiLDS Booking MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the WEE WiLDS 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): send_inquiry.
Has the WEE WiLDS Booking MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.