# Happy Island Cottage booking (remote · happyislandcottage.com)

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

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `happyislandcottage.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-happyislandcottage-booking/happyislandcottage.md), [page](https://verifymcp.io/servers/com-happyislandcottage-booking/happyislandcottage)

## Channel facts

- Endpoint: `https://happyislandcottage.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1406 tokens (~468/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Happy Island Cottage booking MCP server?

Happy Island Cottage booking is a hosted endpoint at https://happyislandcottage.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-happyislandcottage-booking 'https://happyislandcottage.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-happyislandcottage-booking": {
      "url": "https://happyislandcottage.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-happyislandcottage-booking": {
      "type": "http",
      "url": "https://happyislandcottage.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-happyislandcottage-booking]
url = "https://happyislandcottage.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-happyislandcottage-booking": {
      "type": "remote",
      "url": "https://happyislandcottage.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-happyislandcottage-booking --url 'https://happyislandcottage.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-happyislandcottage-booking:
    url: "https://happyislandcottage.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-happyislandcottage-booking": {
      "Transport": "http",
      "Url": "https://happyislandcottage.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-happyislandcottage-booking -t streamable-http -u 'https://happyislandcottage.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-happyislandcottage-booking": {
      "type": "http",
      "url": "https://happyislandcottage.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 66, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_availability” rewrote its description, which is the text the model reads
- [security] Tool “get_quote” rewrote its description, which is the text the model reads
- [security] Tool “request_booking” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 352 → 468
- [cosmetic] “get_quote” reworded the description of “dog”
- [cosmetic] “request_booking” reworded the description of “dog”

### 2026-10-31 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 65, +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.

### 2026-10-28 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 64)

First indexed and scored.

## MCP tools (3)

### `check_availability` (~247 tokens)

Check availability

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).

Input parameters:

- `from` (string): First day to look at, YYYY-MM-DD (default today)
- `property` (string): happy-island-cottage = Happy Island Cottage, sleeps 6; happy-turtle-a = Happy Turtle A, sleeps 5; happy-turtle-b = Happy Turtle B, sleeps 4
- `to` (string): Last day, exclusive, YYYY-MM-DD (default from plus 180 days)

### `get_quote` (~353 tokens)

Get an exact quote

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.

Input parameters:

- `checkin` (string, required): Check in date, YYYY-MM-DD
- `checkout` (string, required): Check out date, YYYY-MM-DD
- `code` (string): Discount code, only if the guest already has one
- `dog` (boolean): True if the guest brings a dog (adds the pet fee). The REST endpoint calls this parameter pets; this server accepts pets as an alias.
- `guests` (integer): Number of guests, counted against the home's capacity
- `property` (string, required): happy-island-cottage = Happy Island Cottage, sleeps 6; happy-turtle-a = Happy Turtle A, sleeps 5; happy-turtle-b = Happy Turtle B, sleeps 4

### `request_booking` (~412 tokens)

Send a booking request

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.

Input parameters:

- `checkin` (string, required): Check in date, YYYY-MM-DD
- `checkout` (string, required): Check out date, YYYY-MM-DD
- `code` (string): Discount code, only if the guest already has one
- `dog` (boolean): True if the guest brings a dog (adds the pet fee). The REST endpoint calls this parameter pets; this server accepts pets as an alias.
- `email` (string, required): Guest's email; the owner replies here with the payment link
- `guestApproved` (boolean, required): Must be true: the guest saw this quote and asked you to send the request
- `guests` (integer, required): Number of guests
- `name` (string, required): Guest's full name
- `notes` (string): Anything the guest wants the owner to know (optional)
- `phone` (string): Guest's phone (optional)
- `property` (string, required): happy-island-cottage = Happy Island Cottage, sleeps 6; happy-turtle-a = Happy Turtle A, sleeps 5; happy-turtle-b = Happy Turtle B, sleeps 4

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-happyislandcottage-booking/happyislandcottage#diagnostics

## Score history

- 2026-11-05: 68
- 2026-11-04: 67
- 2026-11-03: 67
- 2026-11-02: 66
- 2026-11-01: 66
- 2026-10-31: 66
- 2026-10-30: 65
- 2026-10-29: 65
- 2026-10-28: 64
- 2026-10-27: 64

## Common questions

### What is the Happy Island Cottage booking MCP server?

Happy Island Cottage booking is an MCP server listed in the public MCP registry as com.happyislandcottage/booking. Availability, exact all in quotes and booking requests for 3 vacation homes on Anna Maria Island, FL. This page covers its hosted endpoint (https://happyislandcottage.com/mcp).

### Is the Happy Island Cottage booking MCP server safe to use?

Happy Island Cottage booking scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Happy Island Cottage booking MCP server expose?

Happy Island Cottage booking exposes 3 tools: check_availability, get_quote, request_booking. Their descriptions and schemas cost roughly 1,012 tokens of context every time the server is loaded.

### Does the Happy Island Cottage booking MCP server require authentication?

No. We connected to Happy Island Cottage booking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Happy Island Cottage booking MCP server still maintained?

Happy Island Cottage booking is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Happy Island Cottage booking MCP server?

VerifyMCP ran 12 checks on Happy Island Cottage booking, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Happy Island Cottage booking: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://happyislandcottage.com/mcp
- Website: https://happyislandcottage.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-happyislandcottage-booking/happyislandcottage.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-happyislandcottage-booking/happyislandcottage/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-happyislandcottage-booking/happyislandcottage.json
- HTML version of this page: https://verifymcp.io/servers/com-happyislandcottage-booking/happyislandcottage