# DavisStirling (remote · davisstirling.org)

California HOA law: Davis-Stirling Act text and 189 court decisions. Read-only, no auth.

- Trust score: 85/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `davisstirling.org`: 85/100 (this document), [markdown](https://verifymcp.io/servers/org-davisstirling-davisstirling/davisstirling.md), [page](https://verifymcp.io/servers/org-davisstirling-davisstirling/davisstirling)

## Channel facts

- Endpoint: `https://davisstirling.org/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-21.

- **Endpoint Security**: 74/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1320 tokens (~165/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 DavisStirling MCP server?

DavisStirling is a hosted endpoint at https://davisstirling.org/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 org-davisstirling-davisstirling 'https://davisstirling.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-davisstirling-davisstirling": {
      "url": "https://davisstirling.org/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.org-davisstirling-davisstirling]
url = "https://davisstirling.org/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add org-davisstirling-davisstirling --url 'https://davisstirling.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-davisstirling-davisstirling:
    url: "https://davisstirling.org/mcp"
```

### Netclaw

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

### Vellum

```bash
assistant mcp add org-davisstirling-davisstirling -t streamable-http -u 'https://davisstirling.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-davisstirling-davisstirling": {
      "type": "http",
      "url": "https://davisstirling.org/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-09 (score 85, +1)

- [security] Stability: 0.97 → pass
- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-11-07 (score 84, +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-06 (score 83, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 83, +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-11-03 (score 82, +1)

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

### 2026-11-01 (score 81, +1)

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

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

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

### 2026-10-27 (score 79, +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.

## MCP tools (8)

### `search` (~178 tokens)

Search California HOA law

Use this when the user asks about California HOA, condominium or common-interest-development law and you need the governing statute sections or court decisions. Searches the Davis-Stirling Act (Civil Code §§4000–6150) and the court decisions interpreting it; returns ranked results, each with a verbatim snippet, citation and link. Do not use it for other states, commercial or industrial CIDs (§§6500–6876), the Corporations Code, local ordinances, or a specific association’s governing documents.

Input parameters:

- `kind` (string): Limit to statute sections or cases (default all).
- `limit` (integer): Results to return (default 8).
- `query` (string, required): What to look for, in plain words or a citation.
- `topic` (string): A topic slug from browse_topics, e.g. "meetings".

Output parameters:

- `meta` (object)
- `query` (string)
- `results` (array)

### `fetch` (~105 tokens)

Fetch a document

Use this to read the full document for an id returned by search: a statute section’s official text, or a court decision’s DavisStirling summary followed by the start of the opinion, with source and currency information. Do not use it to search; use search first to get an id.

Input parameters:

- `id` (string, required): An id from search, e.g. "cal.civ.4920" or "cal.case.nahrstedt-v-lakeside-village-1994".

Output parameters:

- `id` (string)
- `meta` (object)
- `metadata` (object)
- `text` (string)
- `title` (string)
- `url` (string)

### `get_statute_section` (~188 tokens)

Get a Davis-Stirling section

Use this when you need the official text of a Davis-Stirling Act section (California Civil Code) by number, optionally one subdivision, with its last amendment, cross-references, defined terms and the cases that cite it. Accepts "4920", "§ 4920(b)(2)" or "Civ. Code § 4920". Do not use it for other codes (Corporations, Government, Code of Civil Procedure) or for court cases.

Input parameters:

- `include` (array): Extra parts to return (default ["text"]).
- `pinpoint` (string): A subdivision, e.g. "(b)(2)". Also read from section.
- `section` (required): A Davis-Stirling section: "4920", "§ 4920", "Civ. Code § 4920(b)(2)", or an id like "cal.civ.4920".

Output parameters:

- `cases` (array)
- `cited_by` (array)
- `cross_references` (array)
- `defines` (array)
- `definitions` (array)
- `explainer`
- `former_numbers` (array)
- `hierarchy` (object)
- `history`
- `meta` (object)
- `section` (object)
- `text` (object)
- `title`
- `topic`

### `get_court_case` (~180 tokens)

Get a California HOA court decision

Use this when the user names or cites a California HOA court decision (e.g. "Nahrstedt", "8 Cal.4th 361") or you need what a case held. Returns the court, date and citations, the Davis-Stirling sections the opinion cites (with the court’s own sentence), the cases it cites, a clearly labeled DavisStirling summary, and optionally pages of the opinion text. Do not use it for statutes or for decisions outside this library.

Input parameters:

- `case` (string, required): A case name, reporter citation ("8 Cal.4th 361") or id.
- `include` (array): Parts to return (default ["summary", "sections"]).
- `max_chars` (integer): Opinion characters per page (default 15000).
- `offset` (integer): Opinion text offset (with opinion_text).

Output parameters:

- `case` (object)
- `discussed_by` (array)
- `discusses` (array)
- `former_citations` (array)
- `landmark`
- `map_placement` (object)
- `meta` (object)
- `opinion`
- `sections` (array)
- `summary` (object)

### `find_interpreting_cases` (~190 tokens)

Find cases citing a section

Use this when the user asks which court decisions interpret or apply a Davis-Stirling section. Includes decisions citing its pre-2014 number (former Civil Code §§1350–1378, via the verified AB 805 table), ranked by how central the section is to each opinion, each with the court’s own sentence. Do not use it as a complete citator: it covers only the decisions in this library.

Input parameters:

- `include_former` (boolean): Include citations of the former number (default true).
- `limit` (integer): Cases to return (default 10).
- `min_tier` (string): Lowest tier to include (default "cited").
- `section` (required): A Davis-Stirling section: "4920", "§ 4920", "Civ. Code § 4920(b)(2)", or an id like "cal.civ.4920".

Output parameters:

- `cases` (array)
- `counts` (object)
- `meta` (object)
- `scope` (string)
- `section` (object)

### `get_related_authorities` (~153 tokens)

Get related authorities

Use this when you need what a section or case is connected to: sections it cites or that cite it, defined terms it relies on, procedural steps before and after it, and cases that cite it or that it cites. Every connection carries the verbatim text that creates it. Do not use it to find topically similar law; it returns only these fixed connection types.

Input parameters:

- `authority` (required): A section ("4920", "Civ. Code § 4920") or a case (name, citation like "8 Cal.4th 361", or id).
- `kinds` (array): Connection types to return (default all).
- `limit` (integer): Connections per type (default 10).

Output parameters:

- `authority` (object)
- `connections` (array)
- `meta` (object)
- `truncated` (object)

### `resolve_citation` (~133 tokens)

Check a citation

Use this when you need to check a California HOA citation before relying on it: a Davis-Stirling section (current, or a former pre-2014 number like "Civ. Code 1363"), or a case by reporter citation or name. Returns the current authority and, for former numbers, where the provision lives now per the AB 805 recodification table. Do not use it for citations to other states or other California codes.

Input parameters:

- `citation` (required): The citation as written, e.g. "Civ. Code § 1365.5" or "8 Cal.4th 361".

Output parameters:

- `input` (string)
- `matches` (array)
- `meta` (object)
- `not_found_reason` (string|null)
- `suggestions` (array)

### `browse_topics` (~101 tokens)

Browse Davis-Stirling topics

Use this when the user wants an overview of an area of HOA law (e.g. board meetings, elections, assessments and collections, records, architectural review, disputes) or asks what this source covers. Omit topic to list all subject areas; pass one to get its sections and leading cases. Do not use it to answer a specific legal question; use search.

Input parameters:

- `topic` (string): A topic slug or name, e.g. "meetings".

Output parameters:

- `leading_cases` (array)
- `meta` (object)
- `sections` (array)
- `topic` (object)
- `topics` (array)
- `trails` (array)

## Diagnostics

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

## Score history

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

## Common questions

### What is the DavisStirling MCP server?

DavisStirling is an MCP server listed in the public MCP registry as org.davisstirling/davisstirling. California HOA law: Davis-Stirling Act text and 189 court decisions. Read-only, no auth. This page covers its hosted endpoint (https://davisstirling.org/mcp).

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

DavisStirling scores 85 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 DavisStirling MCP server expose?

DavisStirling exposes 8 tools: search, fetch, get_statute_section, get_court_case, find_interpreting_cases, and 3 more. Their descriptions and schemas cost roughly 1,228 tokens of context every time the server is loaded.

### Does the DavisStirling MCP server require authentication?

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

### Is the DavisStirling MCP server still maintained?

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

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