Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DavisStirling

REMOTE · DAVISSTIRLING.ORG

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

0 this week 85 Trust /100

Last scanned (23 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

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 Security74
  • 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. 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
    • The server rewrote its instructions, which are the text every model session reads security
  • 7 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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 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.

  • 3 Nov 26 +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.

  • 1 Nov 26 +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.

  • 30 Oct 26 +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.

  • 27 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.

Diagnostics

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 21 Nov 2026 · Probed https://davisstirling.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=davisstirling.org CN=WE1,O=Google Trust Services,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA256 3a04a00b3be9120613b077150aa4e8f2
SANs: davisstirling.org, *.davisstirling.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of davisstirling.org. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725 8 Verified
davisstirling.org. No DS 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
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://davisstirling.org/mcp Verified 200
http (plaintext) http://davisstirling.org/mcp HTTPS enforced 301 https://davisstirling.org/mcp
MCP tools · 8 exposed · ~1,228 tokens

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 →

Tool Tokens
browse_topics ~101

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.

NameTypeReqDescription
topicstring–A topic slug or name, e.g. "meetings".
NameTypeReqDescription
leading_casesarray––
metaobjectyes–
sectionsarray––
topicobject––
topicsarray––
trailsarray––

No examples provided.

fetch ~105

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.

NameTypeReqDescription
idstringyesAn id from search, e.g. "cal.civ.4920" or "cal.case.nahrstedt-v-lakeside-village-1994".
NameTypeReqDescription
idstringyes–
metaobjectyes–
metadataobjectyes–
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

find_interpreting_cases ~190

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.

NameTypeReqDescription
include_formerboolean–Include citations of the former number (default true).
limitinteger–Cases to return (default 10).
min_tierstring–Lowest tier to include (default "cited").
section–yesA Davis-Stirling section: "4920", "§ 4920", "Civ. Code § 4920(b)(2)", or an id like "cal.civ.4920".
NameTypeReqDescription
casesarrayyes–
countsobjectyes–
metaobjectyes–
scopestringyes–
sectionobjectyes–

No examples provided.

get_court_case ~180

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.

NameTypeReqDescription
casestringyesA case name, reporter citation ("8 Cal.4th 361") or id.
includearray–Parts to return (default ["summary", "sections"]).
max_charsinteger–Opinion characters per page (default 15000).
offsetinteger–Opinion text offset (with opinion_text).
NameTypeReqDescription
caseobjectyes–
discussed_byarray––
discussesarray––
former_citationsarray––
landmark–––
map_placementobject––
metaobjectyes–
opinion–––
sectionsarray––
summaryobject––

No examples provided.

get_related_authorities ~153

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.

NameTypeReqDescription
authority–yesA section ("4920", "Civ. Code § 4920") or a case (name, citation like "8 Cal.4th 361", or id).
kindsarray–Connection types to return (default all).
limitinteger–Connections per type (default 10).
NameTypeReqDescription
authorityobjectyes–
connectionsarrayyes–
metaobjectyes–
truncatedobjectyes–

No examples provided.

get_statute_section ~188

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.

NameTypeReqDescription
includearray–Extra parts to return (default ["text"]).
pinpointstring–A subdivision, e.g. "(b)(2)". Also read from section.
section–yesA Davis-Stirling section: "4920", "§ 4920", "Civ. Code § 4920(b)(2)", or an id like "cal.civ.4920".
NameTypeReqDescription
casesarray––
cited_byarray––
cross_referencesarray––
definesarray––
definitionsarray––
explainer–––
former_numbersarrayyes–
hierarchyobjectyes–
history–yes–
metaobjectyes–
sectionobjectyes–
textobjectyes–
title–yes–
topic–yes–

No examples provided.

resolve_citation ~133

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.

NameTypeReqDescription
citation–yesThe citation as written, e.g. "Civ. Code § 1365.5" or "8 Cal.4th 361".
NameTypeReqDescription
inputstringyes–
matchesarrayyes–
metaobjectyes–
not_found_reasonstring|nullyes–
suggestionsarrayyes–

No examples provided.

search ~178

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.

NameTypeReqDescription
kindstring–Limit to statute sections or cases (default all).
limitinteger–Results to return (default 8).
querystringyesWhat to look for, in plain words or a citation.
topicstring–A topic slug from browse_topics, e.g. "meetings".
NameTypeReqDescription
metaobjectyes–
querystringyes–
resultsarrayyes–

No examples provided.

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.

remote · davisstirling.org

# add to Claude Code
claude mcp add --transport http org-davisstirling-davisstirling 'https://davisstirling.org/mcp'
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.