mcp-registry/io.github.cswarey16/nuvista-haven · registry v1.0.0 · server reports v4.1.0
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 19:26 UTC, the NuVista Haven MCP Server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
AI front desk for NuVista Haven vacation rentals: live availability, rates, booking links.
Point your MCP client at this streamable-http endpoint: https://nuvista-haven-mcp.onrender.com/mcp
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
8 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.cswarey16%2Fnuvista-haven/fixes
{
"name": "check_availability",
"description": "Check live availability for a property over a date range.",
"inputSchema": {
"type": "object",
"required": [
"property",
"check_in",
"check_out"
],
"properties": {
"check_in": {
"type": "string",
"description": "arrival date, YYYY-MM-DD."
},
"property": {
"type": "string",
"description": "property name or keyword (e.g. \"Farmhouse Haven\", \"pickleball\")."
},
"check_out": {
"type": "string",
"description": "departure date, YYYY-MM-DD."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Check Availability"
}{
"name": "get_booking_link",
"description": "Direct booking URL on nuvistahaven.com for a property.",
"inputSchema": {
"type": "object",
"required": [
"property"
],
"properties": {
"check_in": {
"type": "string",
"default": ""
},
"property": {
"type": "string"
},
"check_out": {
"type": "string",
"default": ""
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Get Booking Link"
}{
"name": "get_property_details",
"description": "Facts about a property: bedrooms, sleeps, bathrooms, amenities, highlights.\n\nAnswers \"does it have a hot tub?\", \"how many bedrooms?\", etc.\nFacts come from nuvistahaven.com; unknown values are null, never guessed.",
"inputSchema": {
"type": "object",
"required": [
"property"
],
"properties": {
"property": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Get Property Details"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.cswarey16/nuvista-haven"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.cswarey16/nuvista-haven"}) over MCP.
search_properties ~146 tokenscheck_availability ~135 tokensget_quote ~132 tokensget_property_details ~110 tokensget_booking_link ~87 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fio.github.cswarey16%2Fnuvista-haven?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.cswarey16%2Fnuvista-haven?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.cswarey16%2Fnuvista-haven.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3bea903297681065…, first seen 2026-11-16, included at leaf 299919 of 384,990. Version history · verify what your client received.
Compare: most reliable data servers · most reliable web servers · most reliable finance servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 19:26 UTC, the NuVista Haven MCP Server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
NuVista Haven MCP Server advertises 5 tools, including check_availability, get_booking_link, get_property_details, get_quote, search_properties.
Point your MCP client at this streamable-http endpoint: https://nuvista-haven-mcp.onrender.com/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.