Remote MCP · Endpoint

Vocasa MCP server

No. Vocasa answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.vocasa.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.vocasa/vocasa
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
226 ms
Tools exposed
2 tools
Uptime, last 30 days
93.3% from 15 checks
Described by its publisher as
Rental property analysis your AI can call
Website
https://vocasa.ai/
Listing
From the official MCP registry (active).
Recent checks of Vocasa
CheckedResultHandshake
1 hour agoHandshake completed226 ms
6 hours agoHandshake completed125 ms
2 days agoHandshake completed674 ms
4 days agoHandshake completed195 ms
7 days agoHandshake completed163 ms
9 days agoHandshake completed281 ms
11 days agoHandshake completed186 ms
13 days agoHandshake completed157 ms
15 days agoHandshake completed331 ms
17 days agoHandshake completed371 ms
19 days agoHandshake completed207 ms
21 days agoHandshake completed147 ms
23 days agoHandshake completed425 ms
24 days agoFailed - the server returned an HTTP error—
25 days agoHandshake completed1.61 s

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Vocasa and makes no claim about it beyond what these checks measured.