Skip to content

Happy Island Cottage booking MCP server

com.happyislandcottage/bookinghappyislandcottage.comstreamable-httpv1.0.0Scanned

Availability, exact all in quotes and booking requests for 3 vacation homes on Anna Maria Island, FL

3 tools: 2 do something that can't be undone and 1 change things.

Tools: 0 delete, 2 irreversible, 1 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 2
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do 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.
Govern this server →

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 Happy Island Cottage booking MCP server can do

The Happy Island Cottage booking MCP server is published by happyislandcottage.com, a domain the MCP Registry verified. It has 3 tools. It can do things that cannot be undone, such as sending, paying or publishing (check_availability and request_booking) and create or change data (1 tool: get_quote), but cannot delete data. None of its tools only reads.

1 tool brings in text other people can write (request_booking); 2 tools can send data out of your system (check_availability and request_booking).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 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.

3 tools

Can't be undone 2Claude Code: ask
  • check_availabilityBooked date ranges and open windows for the three homes, from the live calendars (refreshed every 30 minutes).Can send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "check_availability" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Booked date ranges and open windows for the three homes, from the live calendars (refreshed every 30 minutes). Ranges are start to end with end exclusive: a checkout day is open for a new check in. openWindows lists every gap at least as long as that home's minimum stay inside the window you ask for (default today plus 180 days, longest 400). A window flagged clippedAtWindowEnd may continue past your 'to' date. Homes: Happy Island Cottage (happy-island-cottage, sleeps 6, 7 night minimum); Happy Turtle A (happy-turtle-a, sleeps 5, 3 night minimum); Happy Turtle B (happy-turtle-b, sleeps 4, 3 night minimum).

    Annotations the server declares

    • title: Check availability
    • readOnlyHint: true
    • openWorldHint: false
  • request_bookingSends a booking request to the owner on the guest's behalf, priced by the same engine as get_quote.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "request_booking" says "request": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Sends a booking request to the owner on the guest's behalf, priced by the same engine as get_quote. This is request to book: the owner confirms by email to the guest with a payment link, and nothing is charged now. Call it ONLY after the guest has seen the quote and explicitly asked you to send the request, and set guestApproved to true to confirm that. Every call reaches a real person: never send tests, duplicates or requests the guest has not approved. Errors: as get_quote, plus MISSING_CONTACT and GUEST_APPROVAL_REQUIRED. A request holds nothing. Dates are reserved when the deposit or full payment clears. Cancellation: full refund when cancelled 30 or more days before arrival; inside 30 days the stay is not refundable, except that returning direct guests can cancel anytime and a hurricane warning or mandatory evacuation order for Manatee County covering the stay dates means a full refund whenever cancelled.

    Annotations the server declares

    • title: Send a booking request
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 1Claude Code: ask
  • get_quoteExact all in price for one home and date range, from the same engine as the site's booking form: nightly subtotal, any discount, cleaning fee, pet fee, 7% sales tax plus surtax, 6%…1 finding

    Why it is in this group

    • The name "get_quote" says "get": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "get_quote" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "get_quote" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Exact all in price for one home and date range, from the same engine as the site's booking form: nightly subtotal, any discount, cleaning fee, pet fee, 7% sales tax plus surtax, 6% tourist development tax, total, and the payment schedule (20% deposit at booking and the balance 45 days before check in, or full payment when check in is 45 days away or less; returning guests with their returning guest code pay no deposit and no pet fee). Errors (each with a one sentence message): UNKNOWN_PROPERTY, BAD_DATES, PAST_DATES, BEYOND_HORIZON (last night after 2027-12-31; carries lastBookableDate), MIN_NIGHTS, UNAVAILABLE, OVER_CAPACITY (carries maxGuests). A request holds nothing. Dates are reserved when the deposit or full payment clears. Check in 3:00 PM, check out 10:00 AM. Read only; nothing is booked or held.

    Annotations the server declares

    • title: Get an exact quote
    • readOnlyHint: 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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
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 out2
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.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:23 UTC, unchanged since Oct 27, 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.

    Matched text

    https://happyislandcottage.com/mcp: tools/list returned 3 tools to an anonymous client, including request_booking (destructive), check_availability (irreversible), get_quote (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "check_availability" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "get_quote" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "get_quote" says "get": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools3 changed.~3 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http booking https://happyislandcottage.com/mcp
claude mcp add --transport http booking https://happyislandcottage.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.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__booking__check_availability",
      "mcp__booking__get_quote",
      "mcp__booking__request_booking"
    ],
    "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__check_availability outbound
  • mcp__booking__request_booking 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.happyislandcottage/booking/verify?hash=a360bff414c8de9b2cfa70f687ff98bd3f5263e61f60cbc4dab967ce56ff7bda" | jq -e '.changed == false'

Pinned hash a360bff414c8, from Nov 9, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.happyislandcottage/booking/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.happyislandcottage/booking
[![Anlyon Radar](https://radar.anlyon.com/badge/com.happyislandcottage/booking.svg)](https://radar.anlyon.com/servers/com.happyislandcottage/booking)

Source: MCP Registry. Synced Oct 27, 2026, 05:17 UTC.

Happy Island Cottage booking MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Happy Island Cottage booking MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 2 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 Happy Island Cottage 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 Happy Island Cottage booking MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: check_availability and request_booking.

What tools does the Happy Island Cottage booking MCP server have?

3 tools: 2 irreversible, 1 write. check_availability, request_booking and get_quote.

Does the Happy Island Cottage booking MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Happy Island Cottage booking MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_availability and request_booking.

Has the Happy Island Cottage booking MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.