Remote MCP · Endpoint

DavisStirling MCP server

No. DavisStirling answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://davisstirling.org/mcp

The last check completed an MCP handshake.

Registry name
org.davisstirling/davisstirling
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
390 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
California HOA law: Davis-Stirling Act text and 189 court decisions. Read-only, no auth.
Listing
From the official MCP registry (active).
Recent checks of DavisStirling
CheckedResultHandshake
1 hour agoHandshake completed390 ms
17 hours agoHandshake completed278 ms
1 day agoHandshake completed298 ms
3 days agoHandshake completed326 ms
5 days agoHandshake completed325 ms
7 days agoHandshake completed296 ms
10 days agoHandshake completed328 ms
12 days agoHandshake completed400 ms
14 days agoHandshake completed251 ms
16 days agoHandshake completed296 ms
18 days agoHandshake completed362 ms
20 days agoHandshake completed66 ms
22 days agoHandshake completed247 ms
23 days agoHandshake completed383 ms

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

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.

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