# Vocasa (remote · mcp.vocasa.ai)

Rental property analysis your AI can call

- Trust score: 87/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.vocasa.ai`: 87/100 (this document), [markdown](https://verifymcp.io/servers/ai-vocasa-vocasa/mcp.md), [page](https://verifymcp.io/servers/ai-vocasa-vocasa/mcp)

## Channel facts

- Endpoint: `https://mcp.vocasa.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

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

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 609 tokens (~152/item across 4 items; 2 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 84% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Vocasa MCP server?

Vocasa is a hosted endpoint at https://mcp.vocasa.ai/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 ai-vocasa-vocasa 'https://mcp.vocasa.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-vocasa-vocasa": {
      "url": "https://mcp.vocasa.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-vocasa-vocasa": {
      "type": "http",
      "url": "https://mcp.vocasa.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-vocasa-vocasa]
url = "https://mcp.vocasa.ai/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ai-vocasa-vocasa --url 'https://mcp.vocasa.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-vocasa-vocasa:
    url: "https://mcp.vocasa.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-vocasa-vocasa": {
      "Transport": "http",
      "Url": "https://mcp.vocasa.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-vocasa-vocasa -t streamable-http -u 'https://mcp.vocasa.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-vocasa-vocasa": {
      "type": "http",
      "url": "https://mcp.vocasa.ai/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-04 (score 87, +1)

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

### 2026-11-02 (score 86, +1)

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

### 2026-10-30 (score 85, +1)

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

### 2026-10-28 (score 84, +1)

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

### 2026-10-26 (score 83, +1)

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

### 2026-10-24 (score 82, +1)

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

### 2026-10-22 (score 81, +1)

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

### 2026-10-20 (score 80, +1)

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

## MCP tools (2)

### `analyze_rental` (~358 tokens)

Analyze a rental property

Analyze a US residential property as a rental investment. Give an address or the key facts (price, beds, baths, square feet, ZIP). Add any numbers the user knows, such as their expected rent, tax or insurance; they override our estimates. Returns an investment score, IRR over a 15-year hold, monthly cash flow, cap rate, cash-on-cash return and DSCR, with the source of every input shown. Estimates only, not an appraisal.

Input parameters:

- `address` (string): Street address, ideally with city, state and ZIP.
- `bathrooms` (number)
- `bedrooms` (integer): Total bedrooms (all units together for a 2- or 3-family).
- `down_payment_pct` (number): Down payment as a percent of price (default 20).
- `hoa_monthly` (number): Monthly HOA fee in dollars; 0 when omitted.
- `insurance_annual` (number): Annual insurance in dollars; overrides our estimate.
- `interest_rate` (number): Annual mortgage rate in percent (default: the current 30-year average we use).
- `list_price` (number, required): Asking or purchase price in US dollars.
- `loan_term_years` (integer): Loan term in years (default 30).
- `monthly_rent` (number): The user's expected total monthly rent; overrides our estimate.
- `property_tax_annual` (number): Annual property tax in dollars; overrides our estimate.
- `property_type` (string)
- `square_feet` (number)
- `units` (integer): Number of units in the building, when known.
- `zip` (string): 5-digit US ZIP code. Needed when no address with a ZIP is given.

Output parameters:

- `band` (string)
- `cap_rate` (number)
- `cash_on_cash` (number)
- `disclaimer` (string)
- `dscr` (number)
- `gross_yield` (number)
- `inputs_used` (object)
- `irr` (number|null)
- `irr_hold_years` (integer)
- `irr_note` (string)
- `message` (string)
- `method_url` (string)
- `monthly_cash_flow` (number)
- `next_steps` (array)
- `outcome` (string)
- `score` (integer)
- `summary` (string)

### `deal_score` (~157 tokens)

Look up a Deal Score

Look up NestCalc's independent Deal Score for a for-sale listing, or list the current top deals (WINs) in a covered city. Scores are published for every listing, including low ones, and are never changed for anyone. Covered today: Cincinnati. For any other property, use analyze_rental. Not an appraisal.

Input parameters:

- `address` (string): Street address of a for-sale listing, with city or ZIP when known.
- `city` (string): A city, to list its current WINs.
- `limit` (integer): How many WINs to list for a city (default 10).
- `listing_id` (string): The listing's public id (its slug), e.g. 2268-rice-st.

Output parameters:

- `address` (string)
- `band` (string)
- `cap_rate` (number)
- `cash_on_cash` (number)
- `city` (string)
- `current_list_price` (number)
- `deal_score` (integer)
- `disclaimer` (string)
- `dscr` (number)
- `gross_yield` (number)
- `inputs_used` (object)
- `irr` (number|null)
- `irr_hold_years` (integer)
- `irr_note` (string)
- `ledger_ref` (string)
- `listing_id` (string)
- `message` (string)
- `method_url` (string)
- `monthly_cash_flow` (number)
- `outcome` (string)
- `page_url` (string)
- `rank_in_city` (integer)
- `ranked_of` (integer)
- `score_version` (integer)
- `scored_at` (string)
- `spec_id` (string)
- `status` (string)
- `summary` (string)
- `wins` (array)
- `wins_total` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-vocasa-vocasa/mcp#diagnostics

## Score history

- 2026-11-05: 87
- 2026-11-04: 87
- 2026-11-03: 86
- 2026-11-02: 86
- 2026-11-01: 85
- 2026-10-31: 85
- 2026-10-30: 85
- 2026-10-29: 84
- 2026-10-28: 84
- 2026-10-27: 83
- 2026-10-26: 83
- 2026-10-25: 82
- 2026-10-24: 82
- 2026-10-23: 81
- 2026-10-22: 81
- 2026-10-21: 80
- 2026-10-20: 80
- 2026-10-19: 79
- 2026-10-18: 79
- 2026-10-17: 78
- 2026-10-16: 78
- 2026-10-15: 78
- 2026-10-14: 77
- 2026-10-13: 77
- 2026-10-12: 76
- 2026-10-10: 75
- 2026-10-07: 74

## Common questions

### What is the Vocasa MCP server?

Vocasa is an MCP server listed in the public MCP registry as ai.vocasa/vocasa. Rental property analysis your AI can call. This page covers its hosted endpoint (https://mcp.vocasa.ai/mcp).

### Is the Vocasa MCP server safe to use?

Vocasa scores 87 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 Vocasa MCP server expose?

Vocasa exposes 2 tools: analyze_rental, deal_score. Their descriptions and schemas cost roughly 515 tokens of context every time the server is loaded.

### Does the Vocasa MCP server require authentication?

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

### Is the Vocasa MCP server still maintained?

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

VerifyMCP ran 13 checks on Vocasa, 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://mcp.vocasa.ai/mcp
- Website: https://vocasa.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-vocasa-vocasa/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-vocasa-vocasa/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-vocasa-vocasa/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-vocasa-vocasa/mcp