Yardi Virtuoso

Name: Yardi Virtuoso MCP Server
Availability: InStock
Author: Yardi Virtuoso

HIPAA CompliantSOC2 ReadyISO 27001 Ready

Finance5 tools

Query Yardi property data and file maintenance work orders from an AI agent. Anthropic lists 5 tools, three of them work-order shaped, but the same listing advertises portfolio analysis and invoice approval that no listed tool performs. OAuth sign-in, identity-only scopes.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 23 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Yardi Virtuoso via MCP

https://mcp.virtuoso.ai/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Yardi Virtuoso Tools & Capabilities (5)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

The tool listing does not cover the advertised product. Anthropic's own connector page describes portfolio NOI analysis, market benchmarking and an invoice approval queue. None of the five listed tools performs any of them. Five is a floor, and a risk assessment built on the verb census is measuring the listing rather than the connector.
Yardi's documentation for this server is not publicly readable, so it publishes no tool list we could diff. The nominated documentation URL returns HTTP 401 and renders Intercom's not-authorized page. This is the "no vendor enumeration" case, and it is not a case of us failing to find the page — the help centre's own payload declares allContentRestricted as true with an empty collection list, which is Intercom stating that the entire article set is private.
We could not read tool schemas or safety annotations. Cloudflare returned 403 to our anonymous initialize request before it reached the MCP server, so no parameter-level detail is published here. The directory's own probe of this endpoint recorded the same 403.
The OAuth scopes carry no capability information. Four standard OpenID Connect values, no application scope, and the identical list on two sibling servers that Anthropic records as having different permissions. Nothing at the grant separates reading a work order from creating one.
What a work order write actually triggers is unresolved. We could not establish whether creating one dispatches a vendor or incurs a cost, or whether marking one complete releases an invoice. Yardi's product documentation is behind a Cloudflare challenge on every path we tried, including robots.txt. We did not attempt to bypass it.
Whether resident data is reachable is unresolved. No listed tool names a person record, and the connector page never says resident, tenant or lease. But work orders attach to occupied units, and the advertised financial surface would sit beside resident ledgers if it exists. We did not authenticate, so we could not check.
Yardi's privacy statement does not govern resident data. It excludes "Client Data" — resident and tenant information — from its scope entirely. The applicable terms are your own agreement with Yardi, not the public document.
virtuoso.ai yields nothing to a reader. Every path we requested, including an invented one, returned a byte-identical 1,893-byte single-page-app shell. All of them are HTTP 200, and none of them means anything.
Three Yardi connectors share this host and are easy to confuse. Yardi Virtuoso (5 tools, Read and write), Yardi Matrix (33 tools, Read) and Yardi Deal Manager (14 tools, community tier — not in this catalogue). They are separate listings with separate endpoints.
No rate limits, plan gates or pricing are documented publicly. We found none, which is not the same as there being none.