# Voya Homes public vacation-home search (remote · voyahomes.com)

Read-only Voya Homes search for date-bound availability, prices and property details.

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

## Components

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

## Channel facts

- Endpoint: `https://voyahomes.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-09-28.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 527 tokens (~131/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 79/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 25% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the Voya Homes public vacation-home search MCP server?

Voya Homes public vacation-home search is a hosted endpoint at https://voyahomes.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-voyahomes-voya-homes 'https://voyahomes.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-voyahomes-voya-homes": {
      "url": "https://voyahomes.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-voyahomes-voya-homes": {
      "type": "http",
      "url": "https://voyahomes.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-voyahomes-voya-homes]
url = "https://voyahomes.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-voyahomes-voya-homes --url 'https://voyahomes.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-voyahomes-voya-homes:
    url: "https://voyahomes.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-voyahomes-voya-homes": {
      "Transport": "http",
      "Url": "https://voyahomes.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-voyahomes-voya-homes -t streamable-http -u 'https://voyahomes.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-voyahomes-voya-homes": {
      "type": "http",
      "url": "https://voyahomes.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-09-28 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 66, +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-09-21 (score 65, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Tool coverage: 32% → 25%
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “find_homes”

### 2026-09-20 (score 65)

First indexed and scored.

## MCP tools (4)

### `list_destinations` (~36 tokens)

List Voya Homes destinations

Read-only. Lists destinations currently exposed by Voya Homes. It never creates a booking, intention, payment, hold or customer record.

Output parameters:

- `destinations` (array)
- `retrievedAt` (string)

### `search_homes` (~193 tokens)

Search Voya Homes availability and prices

Read-only search of vacation homes using destination, dates and guests. Returns current server-side availability, prices and links to continue on the Voya Homes property or checkout page. It never reserves, charges, creates an intention or sends a payment request.

Input parameters:

- `adults` (integer, required): Number of adults.
- `amenities` (array)
- `bedrooms` (integer)
- `categories` (array)
- `checkIn` (string, required): Check-in date in YYYY-MM-DD.
- `checkOut` (string, required): Check-out date in YYYY-MM-DD.
- `children` (integer): Number of children.
- `city` (string): Destination city. Orlando is currently bookable; other cities appear only when released by the inventory source.
- `language` (string)
- `maxPrice` (number)
- `minPrice` (number)
- `page` (integer)
- `pageSize` (integer)

Output parameters:

- `checkoutNote` (string)
- `page` (integer)
- `pageSize` (integer)
- `query` (object)
- `results` (array)
- `retrievedAt` (string)
- `total` (integer)
- `totalPages` (integer)

### `get_home` (~101 tokens)

Get Voya Homes property details

Read-only property details and optional date-bound price. When dates and guests are supplied, returns a server-side availability result plus a direct checkout URL. It never reserves, charges, creates an intention or modifies data.

Input parameters:

- `adults` (integer)
- `checkIn` (string)
- `checkOut` (string)
- `children` (integer)
- `houseCode` (string, required): Public Voya Homes property code.
- `language` (string)

Output parameters:

- `property` (object)
- `retrievedAt` (string)

### `find_homes` (~130 tokens)

Find Voya Homes properties by name and location

Read-only static catalog discovery by property name, public code, condominium, neighborhood, city, bedrooms or amenities. It does not check date availability or return a fixed price; use search_homes after selecting travel dates.

Input parameters:

- `amenities` (array)
- `city` (string)
- `language` (string)
- `maxGuests` (integer)
- `minBedrooms` (integer)
- `neighborhood` (string)
- `page` (integer)
- `pageSize` (integer)
- `query` (string): Property name, public code, condominium, address or amenity.

Output parameters:

- `discoveryNote` (string)
- `page` (integer)
- `pageSize` (integer)
- `query` (object)
- `results` (array)
- `retrievedAt` (string)
- `total` (integer)
- `totalPages` (integer)

## Diagnostics

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

## Score history

- 2026-09-28: 68
- 2026-09-27: 67
- 2026-09-26: 67
- 2026-09-25: 67
- 2026-09-24: 66
- 2026-09-23: 66
- 2026-09-22: 65
- 2026-09-21: 65
- 2026-09-20: 65

## Common questions

### What is the Voya Homes public vacation-home search MCP server?

Voya Homes public vacation-home search is an MCP server listed in the public MCP registry as com.voyahomes/voya-homes. Read-only Voya Homes search for date-bound availability, prices and property details. This page covers its hosted endpoint (https://voyahomes.com/mcp).

### Is the Voya Homes public vacation-home search MCP server safe to use?

Voya Homes public vacation-home search 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 Voya Homes public vacation-home search MCP server expose?

Voya Homes public vacation-home search exposes 4 tools: list_destinations, search_homes, get_home, find_homes. Their descriptions and schemas cost roughly 460 tokens of context every time the server is loaded.

### Does the Voya Homes public vacation-home search MCP server require authentication?

No. We connected to Voya Homes public vacation-home search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Voya Homes public vacation-home search MCP server still maintained?

Voya Homes public vacation-home search is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://voyahomes.com/mcp
- Repository: https://github.com/r2nrswkypf-cmyk/voyahomes
- Changelog RSS feed: https://verifymcp.io/servers/com-voyahomes-voya-homes/voyahomes.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-voyahomes-voya-homes/voyahomes.json
- HTML version of this page: https://verifymcp.io/servers/com-voyahomes-voya-homes/voyahomes