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

ZoningVerdict

REMOTE · ZONINGVERDICT.COM · SCANNED AUG 3

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

+4 this week 66 Trust /100
Trust breakdown (6 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 →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · zoningverdict.com

# add to Claude Code
claude mcp add --transport http com-zoningverdict-mcp https://zoningverdict.com/api/mcp?ref=mcp-registry
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add com-zoningverdict-mcp --url https://zoningverdict.com/api/mcp?ref=mcp-registry --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-zoningverdict-mcp:
    url: "https://zoningverdict.com/api/mcp?ref=mcp-registry"
// mcp.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 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.

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

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

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 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
  • 28 Jul 26 +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.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 61

    First indexed and scored.

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 3 Aug 2026 · Probed https://zoningverdict.com/api/mcp?ref=mcp-registry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zoningverdict.com CN=YR1,O=Let's Encrypt,C=US 11 Jun 2026 9 Sept 2026 RSA 2048 SHA256-RSA 589c57860513c045ce621aeb58b72caa51c
SANs: zoningverdict.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f
DNSSEC insecure

Validation of zoningverdict.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
zoningverdict.com. absent 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
strict-transport-security max-age=63072000
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://zoningverdict.com/api/mcp?ref=mcp-registry Verified 200
http (plaintext) http://zoningverdict.com/api/mcp?ref=mcp-registry HTTPS enforced 308 https://zoningverdict.com/api/mcp?ref=mcp-registry
MCP tools — 7 exposed · ~848 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.

Tool Tokens
ask_zoning_question ~148

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.

NameTypeReqDescription
municipalitystringyesMunicipality slug from list_municipalities.
querystringThe question in plain words, used to find the best match.
topicstringOptional filter, one of: permitted_uses, special_land_uses, setbacks, height, lot_coverage, lot_size, parking, adu, accessory_structures, fences, signs, home_occupation, variance_process.

No output schema declared.

No examples provided.

check_coverage ~109

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.

NameTypeReqDescription
addressstringStreet address text; city and state improve matching.
municipalitystringMunicipality slug or name.
qstringAddress or municipality string.

No output schema declared.

No examples provided.

create_watch ~154

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.

NameTypeReqDescription
municipalitystringyesMunicipality slug from list_municipalities.
topicstringOptional: 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…

No output schema declared.

No examples provided.

get_district_rules ~185

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.

NameTypeReqDescription
districtstringDistrict code, e.g. R-2. Get valid codes from list_districts or resolve_parcel_district; do not guess.
municipalitystringyesMunicipality slug from list_municipalities.
topicstringOne of: permitted_uses, special_land_uses, setbacks, height, lot_coverage, lot_size, parking, adu, accessory_structures, fences, signs, home_occupation, variance_process.

No output schema declared.

No examples provided.

list_districts ~93

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.

NameTypeReqDescription
municipalitystringyesMunicipality slug from list_municipalities.

No output schema declared.

No examples provided.

list_municipalities ~68

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

resolve_parcel_district ~91

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.

NameTypeReqDescription
addressstringyesStreet address, city, MI.

No output schema declared.

No examples provided.