Happy Island Cottage booking
REMOTE · HAPPYISLANDCOTTAGE.COM
Availability, exact all in quotes and booking requests for 3 vacation homes on Anna Maria Island, FL
Available components
Last scanned (4 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 2 Nov 26 0
- 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 security
- Schema quality: 352 → 468 ▼ functional
- “get_quote” reworded the description of “dog” cosmetic
- “request_booking” reworded the description of “dog” cosmetic
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 28 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://happyislandcottage.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=happyislandcottage.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 2c03e8949c325b910ef26e1b561fdada |
| SANs: happyislandcottage.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of happyislandcottage.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| happyislandcottage.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://happyislandcottage.com/mcp | Verified | 200 | |
| http (plaintext) | http://happyislandcottage.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_availability Check availability ~247
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
get_quote Get an exact quote ~353
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.
| Name | Type | Req | Description |
|---|---|---|---|
| checkin | string | yes | Check in date, YYYY-MM-DD |
| checkout | string | yes | 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 | yes | happy-island-cottage = Happy Island Cottage, sleeps 6; happy-turtle-a = Happy Turtle A, sleeps 5; happy-turtle-b = Happy Turtle B, sleeps 4 |
No output schema declared.
No examples provided.
request_booking Send a booking request ~412
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.
| Name | Type | Req | Description |
|---|---|---|---|
| checkin | string | yes | Check in date, YYYY-MM-DD |
| checkout | string | yes | 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. |
| string | yes | Guest's email; the owner replies here with the payment link | |
| guestApproved | boolean | yes | Must be true: the guest saw this quote and asked you to send the request |
| guests | integer | yes | Number of guests |
| name | string | yes | Guest's full name |
| notes | string | – | Anything the guest wants the owner to know (optional) |
| phone | string | – | Guest's phone (optional) |
| property | string | yes | happy-island-cottage = Happy Island Cottage, sleeps 6; happy-turtle-a = Happy Turtle A, sleeps 5; happy-turtle-b = Happy Turtle B, sleeps 4 |
No output schema declared.
No examples provided.
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.
remote · happyislandcottage.com
claude mcp add --transport http com-happyislandcottage-booking 'https://happyislandcottage.com/mcp'
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.