Vocasa
REMOTE · MCP.VOCASA.AI
Rental property analysis your AI can call
Available components
Last scanned (7 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 84% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
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 5 Nov 2026 · Probed https://mcp.vocasa.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.vocasa.ai | CN=YE2,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5a076c0730dbf9a54446a94cc5d102b2d6d |
| SANs: mcp.vocasa.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.vocasa.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| vocasa.ai. | absent | 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 |
|---|---|
| strict-transport-security | max-age=31536000 |
| 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://mcp.vocasa.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.vocasa.ai/mcp | HTTPS enforced | 301 | https://mcp.vocasa.ai/mcp |
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 →
analyze_rental Analyze a rental property ~358
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| band | string | – | – |
| cap_rate | number | – | – |
| cash_on_cash | number | – | – |
| disclaimer | string | yes | – |
| dscr | number | – | – |
| gross_yield | number | – | – |
| inputs_used | object | – | – |
| irr | number|null | – | – |
| irr_hold_years | integer | – | – |
| irr_note | string | – | – |
| message | string | – | – |
| method_url | string | yes | – |
| monthly_cash_flow | number | – | – |
| next_steps | array | – | – |
| outcome | string | yes | – |
| score | integer | – | – |
| summary | string | – | – |
No examples provided.
deal_score Look up a Deal Score ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| band | string | – | – |
| cap_rate | number | – | – |
| cash_on_cash | number | – | – |
| city | string | – | – |
| current_list_price | number | – | – |
| deal_score | integer | – | – |
| disclaimer | string | yes | – |
| 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 | yes | – |
| monthly_cash_flow | number | – | – |
| outcome | string | yes | – |
| 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 | – | – |
No examples provided.
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.
remote · mcp.vocasa.ai
claude mcp add --transport http ai-vocasa-vocasa 'https://mcp.vocasa.ai/mcp'
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.