# ZoningVerdict (remote · zoningverdict.com)

Human-reviewed zoning answers with ordinance citations for covered US municipalities.

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `zoningverdict.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/com-zoningverdict-mcp/api-mcp.md), [page](https://verifymcp.io/servers/com-zoningverdict-mcp/api-mcp)

## Channel facts

- Endpoint: `https://zoningverdict.com/api/mcp?ref=mcp-registry`
- 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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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 961 tokens (~137/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-zoningverdict-mcp https://zoningverdict.com/api/mcp?ref=mcp-registry
```

### Codex

```toml
[mcp_servers.com-zoningverdict-mcp]
url = "https://zoningverdict.com/api/mcp?ref=mcp-registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-zoningverdict-mcp": {
      "type": "remote",
      "url": "https://zoningverdict.com/api/mcp?ref=mcp-registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-zoningverdict-mcp --url https://zoningverdict.com/api/mcp?ref=mcp-registry --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-zoningverdict-mcp:
    url: "https://zoningverdict.com/api/mcp?ref=mcp-registry"
```

### Other

```json
{
  "mcpServers": {
    "com-zoningverdict-mcp": {
      "type": "http",
      "url": "https://zoningverdict.com/api/mcp?ref=mcp-registry"
    }
  }
}
```

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-08-03 (score 66, +1)

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

### 2026-08-01 (score 65, +1)

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

### 2026-07-31 (score 64, +1)

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

### 2026-07-30 (score 63, 0)

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

### 2026-07-28 (score 63, +1)

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

### 2026-07-27 (score 62, +1)

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

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (7)

### `check_coverage` (~109 tokens)

Free coverage preflight for an address or municipality string. Returns whether ZoningVerdict covers it, available topics, pack version, and last-reviewed date. It does not identify a parcel's zoning district; use resolve_parcel_district only when the district determination is needed. Results are for information purposes only.

Input parameters:

- `address` (string): Street address text; city and state improve matching.
- `municipality` (string): Municipality slug or name.
- `q` (string): Address or municipality string.

### `list_municipalities` (~68 tokens)

List the municipalities ZoningVerdict covers, with each pack's version and last-reviewed date. Coverage is reviewed summaries of public zoning ordinances, for information purposes only. Start here when you do not have a street address; with an address, start with resolve_parcel_district.

### `list_districts` (~93 tokens)

List the zoning district codes for one municipality, with each district's name, category, and summary. Use these codes with get_district_rules; do not guess codes. If you have a street address, resolve_parcel_district identifies the district for you. Free, like list_municipalities. Reviewed summaries for information purposes only.

Input parameters:

- `municipality` (string, required): Municipality slug from list_municipalities.

### `get_district_rules` (~185 tokens)

Get the published rules for one zoning district by topic (setbacks, fences, accessory structures, and so on). District codes come from list_districts or resolve_parcel_district — do not guess them. Every rule carries its ordinance citation and source link plus the pack's last-reviewed date. Summaries for information, not legal advice; confirm with the municipality before acting.

Input parameters:

- `district` (string): District code, e.g. R-2. Get valid codes from list_districts or resolve_parcel_district; do not guess.
- `municipality` (string, required): Municipality slug from list_municipalities.
- `topic` (string): One of: permitted_uses, special_land_uses, setbacks, height, lot_coverage, lot_size, parking, adu, accessory_structures, fences, signs, home_occupation, variance_process.

### `ask_zoning_question` (~148 tokens)

Look up a published question-and-answer for a municipality and topic. Returns the matching reviewed answer with its citations, or reports honestly that no published answer exists and lists the topics that do have reviewed answers. Never generates new answers; confirm with the municipality before acting.

Input parameters:

- `municipality` (string, required): Municipality slug from list_municipalities.
- `query` (string): The question in plain words, used to find the best match.
- `topic` (string): Optional filter, one of: permitted_uses, special_land_uses, setbacks, height, lot_coverage, lot_size, parking, adu, accessory_structures, fences, signs, home_occupation, variance_process.

### `resolve_parcel_district` (~91 tokens)

Resolve a street address to its municipality and, where a GIS path exists, its zoning district. Start here when you have an address, then pass the returned district code to get_district_rules. The response discloses how the district was identified. Parcel boundaries and zoning lines can disagree near edges; confirm with the municipality before acting.

Input parameters:

- `address` (string, required): Street address, city, MI.

### `create_watch` (~154 tokens)

Start a $49/month watch on a covered municipality (optionally one topic): an email whenever a human-reviewed rule change is published, with the citation and the updated page. Returns a Stripe checkout URL; the subscription activates only after checkout completes, and every email carries unsubscribe and billing links. Alerts are reviewed summaries for information purposes. Use list_municipalities for coverage.

Input parameters:

- `municipality` (string, required): Municipality slug from list_municipalities.
- `topic` (string): Optional: watch one topic only, one of: permitted_uses, special_land_uses, setbacks, height, lot_coverage, lot_size, parking, adu, accessory_structures, fences, signs, home_occupation, variance_proce…

## Diagnostics

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

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 65
- 2026-07-31: 64
- 2026-07-30: 63
- 2026-07-29: 63
- 2026-07-28: 63
- 2026-07-27: 62
- 2026-07-26: 61

## Links

- Remote endpoint: https://zoningverdict.com/api/mcp?ref=mcp-registry
- Website: https://zoningverdict.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-zoningverdict-mcp/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-zoningverdict-mcp/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-zoningverdict-mcp/api-mcp