Haveny MCP server

Which servers in the official MCP registry are Haveny's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to Haveny

Whose server it is

Registry nameco.haveny/california-hoa-lawverified in the MCP registry

The registry name sits under haveny.co. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13

Stateanswerschecked 2026-10-13
Tools4
Server calls itselfHaveny HOA Law (California)
Server version0.2.0
Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 298 ms.

Tools it offers4 tools · read 2026-10-13

lookup_hoa_statute
Look up a California Davis-Stirling Civil Code or Corporations Code section and get its heading, a one-line description of what the section covers, and links to the Haveny articles that explain it. Use this when the user mentions a…
get_homeowner_rights
Find the Haveny articles that cover a California HOA situation described from the homeowner side (records request, election, special assessment, rule enforcement, unresponsive management). Returns up to three articles, each with its…
get_board_obligations
Find the Haveny articles that cover a California HOA board topic (discipline, elections, records, rule changes, fiduciary duties, business judgment rule). Use when the user is on a board or asking about board duties. Returns up to three…
search_hoa_knowledge
Free-text search across Haveny's California HOA articles. Returns up to three matching articles, each with its title, link and a one-line topic. Use when the user's question is broad or none of the other tools fit. IMPORTANT: This tool…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "california-hoa-law": {
      "type": "http",
      "url": "https://haveny-mcp.havenyy.workers.dev/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.