
Voya Homes MCP server
Which MCP servers are Voya Homes's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-19
- Registry namecom.voyahomes/voya-homesverified in the MCP registry
The registry name sits under voyahomes.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-19
- Tools4
- Server calls itselfvoya-homes-public
- Server version1.1.0
- Protocol version2025-03-26
On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 557 ms.
- Whether its tools do the product's job has not been judged yet.
Once connected
- Parameters are untyped or undescribed in 3 of 4 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score96 of 100answers 100 · definitions 88 · context 100 · connects 100
- Answered100% of days16 of 16 daily checks
- Median first answer790 ms
- Space in an agent's context≈ 833 tokensthe definitions of all its tools (4), which an agent carries on every turn
- Tool definitionsB · 88 of 100
- Typed results4 of 4 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 3 of 4
What an agent can do with it
- not sure · search vacation homes by destination, dates and guest count
- not sure · compare total prices before committing to a booking
- cannot · pay for a stay by PIX or credit card
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
list_destinationsRead-only. Lists destinations currently exposed by Voya Homes. It never creates a booking, intention, payment, hold or customer record.
search_homesRead-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…
get_homeRead-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.
find_homesRead-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.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"voya-homes": {
"type": "http",
"url": "https://voyahomes.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http voyahomes https://voyahomes.com/mcpclaude.ai, ChatGPT and other clients: add https://voyahomes.com/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.