Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Casa Kimball

REMOTE · WWW.CASAKIMBALL.COM

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

+4 this week 67 Trust /100

Last scanned (15 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • 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. 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 Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 96% of tool parameters carry a description.Partial
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 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

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

  • 19 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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 14 Nov 26 0
    • Server version: 1.0.0 → 1.0.1 functional
  • 13 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 62

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://www.casakimball.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.casakimball.com CN=WR3,O=Google Trust Services,C=US 10 Nov 2026 8 Feb 2027 RSA 2048 SHA256-RSA 39d3554af8b72f7010bf2654f05efa34
SANs: www.casakimball.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.casakimball.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
casakimball.com. No DS 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
Header Value
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.casakimball.com/mcp Verified 200
http (plaintext) http://www.casakimball.com/mcp HTTPS enforced 302 https://www.casakimball.com/mcp
MCP tools · 6 exposed · ~954 tokens

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 →

Tool Tokens
check_availability ~82

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.

NameTypeReqDescription
check_instringyesArrival date, YYYY-MM-DD. Arrival is from 2pm.
check_outstringyesDeparture date, YYYY-MM-DD. Departure is by noon.

No output schema declared.

No examples provided.

find_open_dates ~113

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.

NameTypeReqDescription
fromstring–Look from this date, YYYY-MM-DD; default today.
monthsinteger–How many months to look across.
nightsinteger–Only windows with room for at least this many nights; default the minimum stay.

No output schema declared.

No examples provided.

get_house_info ~96

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.

NameTypeReqDescription
topicstring––

No output schema declared.

No examples provided.

get_quote ~213

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.

NameTypeReqDescription
add_onsarray–Optional add-on codes from get_quote's add_ons_available (boat tour, spa, bonfire, ...); priced for the whole party.
adultsintegeryesAdults (12 and up).
check_instringyesArrival date, YYYY-MM-DD. Arrival is from 2pm.
check_outstringyesDeparture date, YYYY-MM-DD. Departure is by noon.
childreninteger–Children aged 4 to 11. Adults and children together may not exceed 20.
toddlersinteger–Children under 4: free, and not counted toward the 20.

No output schema declared.

No examples provided.

request_hold ~303

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.

NameTypeReqDescription
add_onsarray–Optional add-on codes from get_quote's add_ons_available (boat tour, spa, bonfire, ...); priced for the whole party.
adultsintegeryesAdults (12 and up).
check_instringyesArrival date, YYYY-MM-DD. Arrival is from 2pm.
check_outstringyesDeparture date, YYYY-MM-DD. Departure is by noon.
childreninteger–Children aged 4 to 11. Adults and children together may not exceed 20.
emailstringyesThe guest's email address; the confirmation link goes here.
messagestring–Optional note for the house: the occasion, arrival plans, what the group loves.
namestringyesThe guest's full name.
phonestring–Optional phone number, with country code.
toddlersinteger–Children under 4: free, and not counted toward the 20.

No output schema declared.

No examples provided.

send_inquiry ~147

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.

NameTypeReqDescription
check_instring–Optional arrival date the guest has in mind.
check_outstring–Optional departure date.
emailstringyesWhere the house should reply.
guestsinteger–Optional head count, including day guests for an event.
messagestringyesThe question or request, in the guest's words where possible.
namestringyesThe guest's full name.

No output schema declared.

No examples provided.

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.

remote · www.casakimball.com

# add to Claude Code
claude mcp add --transport http com-casakimball-villa 'https://www.casakimball.com/mcp'
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.