# Casa Kimball (remote · www.casakimball.com)

Plan a stay at an oceanfront villa in Cabrera, Dominican Republic: open dates, exact quotes, holds.

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

## Components

- remote · `www.casakimball.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-casakimball-villa/www.md), [page](https://verifymcp.io/servers/com-casakimball-villa/www)

## Channel facts

- Endpoint: `https://www.casakimball.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (request_hold).
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1163 tokens (~193/item across 6 items; 6 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**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% 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 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Casa Kimball MCP server?

Casa Kimball is a hosted endpoint at https://www.casakimball.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-casakimball-villa 'https://www.casakimball.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-casakimball-villa": {
      "url": "https://www.casakimball.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-casakimball-villa": {
      "type": "http",
      "url": "https://www.casakimball.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-casakimball-villa]
url = "https://www.casakimball.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-casakimball-villa --url 'https://www.casakimball.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-casakimball-villa:
    url: "https://www.casakimball.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-casakimball-villa": {
      "Transport": "http",
      "Url": "https://www.casakimball.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-casakimball-villa -t streamable-http -u 'https://www.casakimball.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-casakimball-villa": {
      "type": "http",
      "url": "https://www.casakimball.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-21 (score 67, +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-19 (score 66, +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-17 (score 65, +1)

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

### 2026-11-15 (score 64, +1)

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

### 2026-11-14 (score 63, 0)

- [functional] Server version: 1.0.0 → 1.0.1

### 2026-11-13 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 62)

First indexed and scored.

## MCP tools (6)

### `get_house_info` (~96 tokens)

About the house

Facts about Casa Kimball. "overview" has the essentials in one page: who it sleeps, the nightly rates by season, what every stay adds, payment and cancellation terms, and arrival times. The others go deeper: house (the place itself), rooms, dining (the chef and meals), activities, arrival (airports and transfers), spa, events (weddings and celebrations), faq.

Input parameters:

- `topic` (string)

### `find_open_dates` (~113 tokens)

Find open dates

Open stretches on the calendar, long enough for a stay. Each window gives the first possible arrival, the last possible departure, and how many nights fit between them. Turnover days around other stays are already excluded, and arrivals open 7 days out.

Input parameters:

- `from` (string): Look from this date, YYYY-MM-DD; default today.
- `months` (integer): How many months to look across.
- `nights` (integer): Only windows with room for at least this many nights; default the minimum stay.

### `check_availability` (~82 tokens)

Check dates

Whether the whole villa is free for exact dates, counting the turnover days around other stays, the 7-day booking lead time, and the season's minimum stay.

Input parameters:

- `check_in` (string, required): Arrival date, YYYY-MM-DD. Arrival is from 2pm.
- `check_out` (string, required): Departure date, YYYY-MM-DD. Departure is by noon.

### `get_quote` (~213 tokens)

Price a stay

The exact itemized price of a stay, from the same engine as the booking page: the nightly rental by season, the meal plan, the 12% gratuity, the refundable security deposit, and any add-ons. Also says whether the dates are open, lists the add-ons, and gives a link that opens the booking page on this stay.

Input parameters:

- `add_ons` (array): Optional add-on codes from get_quote's add_ons_available (boat tour, spa, bonfire, ...); priced for the whole party.
- `adults` (integer, required): Adults (12 and up).
- `check_in` (string, required): Arrival date, YYYY-MM-DD. Arrival is from 2pm.
- `check_out` (string, required): Departure date, YYYY-MM-DD. Departure is by noon.
- `children` (integer): Children aged 4 to 11. Adults and children together may not exceed 20.
- `toddlers` (integer): Children under 4: free, and not counted toward the 20.

### `request_hold` (~303 tokens)

Hold dates for the guest

Sets the dates aside for 2 hours and emails the guest a link. The guest opens it, reads the payment and cancellation terms, and accepts; only then are the dates held, for 72 hours, and the itemized invoice sent. Nothing is charged. Use the guest's own name and email address, with their permission, after get_quote: the email goes to them, and the house will reply there. One open request per email address at a time.

Input parameters:

- `add_ons` (array): Optional add-on codes from get_quote's add_ons_available (boat tour, spa, bonfire, ...); priced for the whole party.
- `adults` (integer, required): Adults (12 and up).
- `check_in` (string, required): Arrival date, YYYY-MM-DD. Arrival is from 2pm.
- `check_out` (string, required): Departure date, YYYY-MM-DD. Departure is by noon.
- `children` (integer): Children aged 4 to 11. Adults and children together may not exceed 20.
- `email` (string, required): The guest's email address; the confirmation link goes here.
- `message` (string): Optional note for the house: the occasion, arrival plans, what the group loves.
- `name` (string, required): The guest's full name.
- `phone` (string): Optional phone number, with country code.
- `toddlers` (integer): Children under 4: free, and not counted toward the 20.

### `send_inquiry` (~147 tokens)

Message the house

Passes a message to the house team, who reply to the guest by email. For weddings and events, long stays, larger groups, or any question the other tools don't answer. Use the guest's own name and email address, with their permission.

Input parameters:

- `check_in` (string): Optional arrival date the guest has in mind.
- `check_out` (string): Optional departure date.
- `email` (string, required): Where the house should reply.
- `guests` (integer): Optional head count, including day guests for an event.
- `message` (string, required): The question or request, in the guest's words where possible.
- `name` (string, required): The guest's full name.

## Diagnostics

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

## Score history

- 2026-11-21: 67
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 65
- 2026-11-16: 64
- 2026-11-15: 64
- 2026-11-14: 63
- 2026-11-13: 63
- 2026-11-12: 62

## Common questions

### What is the Casa Kimball MCP server?

Casa Kimball is an MCP server listed in the public MCP registry as com.casakimball/villa. Plan a stay at an oceanfront villa in Cabrera, Dominican Republic: open dates, exact quotes, holds. This page covers its hosted endpoint (https://www.casakimball.com/mcp).

### Is the Casa Kimball MCP server safe to use?

Casa Kimball scores 67 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 Casa Kimball MCP server expose?

Casa Kimball exposes 6 tools: get_house_info, find_open_dates, check_availability, get_quote, request_hold, send_inquiry. Their descriptions and schemas cost roughly 954 tokens of context every time the server is loaded.

### Does the Casa Kimball MCP server require authentication?

No. We connected to Casa Kimball without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Casa Kimball MCP server still maintained?

Casa Kimball is still listed as active in the MCP registry. We last reached this channel on 21 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 Casa Kimball MCP server?

VerifyMCP ran 13 checks on Casa Kimball, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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://www.casakimball.com/mcp
- Website: https://www.casakimball.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-casakimball-villa/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-casakimball-villa/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-casakimball-villa/www.json
- HTML version of this page: https://verifymcp.io/servers/com-casakimball-villa/www
