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.

Zoning Signal

REMOTE · ZONINGSIGNAL.COM · SCANNED AUG 3

US municipal zoning intelligence — corridor analysis, place dossiers, named-pattern detection.

Available components

+6 this week 77 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 Security80
Transport & Reachability100
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3869 tokens (~184/item across 21 items; 17 tools + 4 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · zoningsignal.com

# add to Claude Code
claude mcp add --transport http com-zoningsignal-observatory https://zoningsignal.com/mcp
# ~/.codex/config.toml
[mcp_servers.com-zoningsignal-observatory]
url = "https://zoningsignal.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-zoningsignal-observatory": {
      "type": "remote",
      "url": "https://zoningsignal.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-zoningsignal-observatory --url https://zoningsignal.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-zoningsignal-observatory:
    url: "https://zoningsignal.com/mcp"
// mcp.json
{
  "mcpServers": {
    "com-zoningsignal-observatory": {
      "type": "http",
      "url": "https://zoningsignal.com/mcp"
    }
  }
}

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.

  • 31 Jul 26 +3
    • 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 +1

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

  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 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 70

    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://zoningsignal.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zoningsignal.com CN=YR2,O=Let's Encrypt,C=US 30 Jun 2026 28 Sept 2026 RSA 2048 SHA256-RSA 58338dab596b1bda944087b69c4554387c7
SANs: zoningsignal.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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 zoningsignal.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
zoningsignal.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://zoningsignal.com/mcp Verified 200
http (plaintext) http://zoningsignal.com/mcp HTTPS enforced 308 https://zoningsignal.com/mcp
MCP tools — 17 exposed · ~3,554 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
describe_corridor ~170

Return the dossier projection for a corridor, in the requested cognitive lens. Same lens enum and default as describe_place. Corridor projections surface cross-municipal dialectics and shared-infrastructure dynamics that no single place dossier captures.

NameTypeReqDescription
lensstringThe cognitive position to project. Defaults to "synthesis". Canonical lenses: developer, investor, broker, attorney, business, resident, civic-leader. Aliases route to canonical: legal/lawyer/counsel…
slugstringyesThe corridor slug (e.g., "us-27-south-lake"). Use list_corridors to discover available slugs.
NameTypeReqDescription
available_lensesarray
claimsarrayyes
fell_back_to_synthesisboolean
freshnessobjectyes
frontmatterobject
lensstringyes
lens_was_requestedstring
projectionstringyes
record_statusobject|null
slugstringyes
titlestring
typestringyes
urlstringyes

No examples provided.

describe_entity ~286

Return the full structured dossier for a named entity — the canonical citable artifact for any actor, organization, ordinance, or project the corpus references. Returns: voxel_lead (134-167 word voxel-disciplined identity prose), canonical_role, the class-specific cluster (person.voting_record for board members; organization.type + jurisdiction; legislation.legal_status + effective_date + sunset_date + citation; creative_work.work_type + status + case_number), the bidirectional graph references (appears_in_meetings, appears_in_briefs, appears_in_watches, exhibits_patterns, related_entities, related_places, related_corridors), the provenance_chain, and the canonical surfaces (dossier URL, schema_id, decoder_index_hub). Each schema_id (`/entities/{slug}#{class.toLowerCase()}`) is the stable cross-page Schema.org reference — Person / Organization / Legislation / CreativeWork — that AI agents resolve to when citing the entity. Use when grounding a citation, when reasoning about an entity's full role across the corpus, or when traversing the entity graph from a single name.

NameTypeReqDescription
slugstringyesThe entity slug (e.g., "sb-180", "hanover-land-company", "anita-geraci-carver"). Use list_entities to discover available slugs. The Decoder Index hub at /entities lists every entity grouped by class.
NameTypeReqDescription
appears_in_briefsarray
appears_in_meetingsarray
appears_in_watchesarray
canonical_rolestring
creative_workobject
display_namestringyes
entity_classstringyes
exhibits_patternsarray
last_activestring
legislationobject
named_atstring
organizationobject
personobject
provenance_chainarray
related_entitiesarray
related_placesarray
schema_idstringyes
slugstringyes
urlstringyes
voxel_leadstring

No examples provided.

describe_meeting ~338

Return the full dossier projection for a meeting reading, in the requested cognitive lens. Same lens enum and default as describe_place / describe_corridor — eight total projections (seven stakeholder lenses — developer, investor, broker, attorney, business, resident, civic-leader — plus synthesis as the default). Returns the lens-projected body, full frontmatter (jurisdiction, board, meeting_date, document_type, key_signals, vote tallies), citation-stable claims[] (per the Phase 11 Citable Contract; populates as meeting claim scopes graduate), four-clock freshness, and the structured record_status block (record_type / meeting_status / outcome_status / minutes_available / vote_final) — the last prevents agents from summarizing agenda intent as completed action. Use to ground citations in a specific meeting's reading; pair with list_meetings or meeting_index for discovery.

NameTypeReqDescription
lensstringOptional cognitive lens. Default: synthesis (the whole-picture multi-projection view). Canonical lenses: developer, investor, broker, attorney, business, resident, civic-leader. Aliases route to cano…
slugstringyesThe meeting slug (e.g., "leesburg-pc-2026-01"). Use list_meetings or meeting_index to discover available slugs.
NameTypeReqDescription
available_lensesarray
claimsarrayyes
fell_back_to_synthesisboolean
freshnessobjectyes
frontmatterobject
lensstringyes
lens_was_requestedstring
projectionstringyes
record_statusobject|nullyes
slugstringyes
titlestring
typestringyes
urlstringyes

No examples provided.

describe_pattern ~164

Return the full dossier for a named pattern: voxel_lead, signal_status (score/direction/horizon/confidence/pips), scope (spatial/temporal/topical/corridors), full exhibits inventory with detection metadata, defensive responses, provenance chain, related briefs, related places, related corridors, audiences, and the canonical surfaces (dossier URL, DefinedTerm @id, DefinedTermSet @id, atlas list URL). Use when an agent needs the structured pattern data to cite or analyze. Each pattern is a citable entity in the corpus's entity graph; the DefinedTerm canonical home gives AI agents a stable reference.

NameTypeReqDescription
slugstringyesThe pattern slug (e.g., "self-storage-canary"). Use current_named_patterns to discover available slugs.
NameTypeReqDescription
audiencesarray
claimsarrayyes
defensive_responsearray
exhibitsarray
freshnessobjectyes
lifecycle_stagestring
namestringyes
named_atstring
provenance_chainarray
related_briefsarray
related_corridorsarray
related_placesarray
scopeobject
signal_statusobject
slugstringyes
surfacesobject
urlstringyes
voxel_leadstring

No examples provided.

describe_place ~238

Return the dossier projection for a city, in the requested cognitive lens. Defaults to the synthesis projection (the multidimensional view that holds all lenses in superposition and names the dialectics). Pass a single-lens value to get the focused cognitive position — useful when the agent is acting on behalf of a user with a specific stake (developer underwriting, investor thesis, broker client argument, attorney precedent search, resident orientation, civic-leader regional coordination).

NameTypeReqDescription
lensstringThe cognitive position to project. Defaults to "synthesis". Canonical lenses: developer, investor, broker, attorney, business, resident, civic-leader. Aliases route to canonical: legal/lawyer/counsel…
slugstringyesThe place slug (e.g., "clermont-florida"). Use list_places to discover available slugs.
NameTypeReqDescription
available_lensesarray
claimsarrayyes
fell_back_to_synthesisboolean
freshnessobjectyes
frontmatterobject
lensstringyes
lens_was_requestedstring
projectionstringyes
record_statusobject|null
slugstringyes
titlestring
typestringyes
urlstringyes

No examples provided.

describe_watch ~200

Return the full dossier for a watch item — the observatory's forward-looking observation primitive. Returns title, subtitle, scope (place / corridor / pattern / brief / region), trigger (type / date / condition), significance (score / horizon / confidence / confidence_pips / why_it_matters_voxel), full body prose, four-clock freshness, and citation-stable claims[]. For RESOLVED watches, also returns the outcome cluster (outcome_type, outcome_summary, prediction_assessment with directional/horizon/significance assessments, lesson, citations) — and the lesson surfaces as a stable claim_id (per the Phase 11 Citable Contract × Phase 8 Resolution Bridge compound). Use to ground citations in a specific watch's prediction or resolution; pair with list_watch_items for discovery.

NameTypeReqDescription
slugstringyesThe watch slug (e.g., "lake-bright-council-mar-23"). Use list_watch_items to discover available slugs.
NameTypeReqDescription
bodystring
claimsarrayyes
freshnessobjectyes
outcomeobjectyes
scopeobject
significanceobject
slugstringyes
subtitlestring
titlestring
triggerobject
typestringyes
urlstringyes

No examples provided.

describe_zoning_signal ~57

Return the canonical product description for Zoning Signal — what the observatory is, the four artifact types it publishes, the regional scope of current coverage, and the methodology. Call once per session to ground subsequent tool calls in canonical context.

Input schema present but exposes no named parameters.

NameTypeReqDescription
artifact_typesarrayyes
built_byobject
descriptionstringyes
methodologyobjectyes
namestringyes
regional_scopeobject
surfacesobjectyes

No examples provided.

get_track_record ~246

Return the observatory's public calibration scorecard — the aggregate accuracy of past watch-item directional reads, horizon calls, and significance assessments across resolved watches. Returns: total_resolved, directional accuracy (aligned + 0.5 × mixed), horizon accuracy (within / total), significance accuracy (confirmed / total), per-confidence-pip stratification, recent resolutions, and per-jurisdiction breakdown. Optionally scope to a single jurisdiction or corridor's constituent set. Use when an agent or user wants to assess Zoning Signal's historical forecasting accuracy before citing a current prediction. Misreads are reported.

NameTypeReqDescription
briefstringOptional: scope to a brief slug (e.g., "six-month-board-flip"). Returns the track record for watches linked to a specific named-pattern brief.
corridorstringOptional: scope to a corridor slug (e.g., "us-27-south-lake"). Returns the aggregate track record across the corridor's constituent places.
jurisdictionstringOptional: scope to a single place slug (e.g., "leesburg-florida") for that city's track record only. Use list_cities to discover available slugs.
NameTypeReqDescription
by_confidencearray
directionalobject
horizonobject
obsoletenumber
pendingnumber
recentarray
scopeobject
significanceobject
surfacesobject
total_resolvednumber

No examples provided.

list_corridors ~62

List every published corridor page. A corridor is the cross-municipal economic-topology view — the cross-jurisdiction read on a shared infrastructure spine, aquifer, or commercial gravity field. Returns name, slug, constituent cities, primary axis, and URL.

Input schema present but exposes no named parameters.

NameTypeReqDescription
corridorsarray
countnumber

No examples provided.

list_entities ~377

List every named entity in the Decoder Index — the smallest citable unit of authority in the corpus. Returns the four-class taxonomy (Person / Organization / Legislation / CreativeWork) with class-specific summary fields (jobTitle for Person; jurisdiction for Organization / Legislation / Project; legal_status for Legislation; case_number + work_status for Project) plus cross-reference counts (meetings_count, briefs_count, watches_count, patterns_count) for each entity. Filter by entity_class, place (jurisdiction), or search substring. Use as the discovery surface for the entity graph; pair with describe_entity for full structured detail. Each entity's schema_id is a stable cross-page reference (`/entities/{slug}#{class.toLowerCase()}`) that resolves to the canonical Schema.org node — Person / Organization / Legislation / CreativeWork — for AI-citation grounding.

NameTypeReqDescription
entity_classstringFilter by entity class. "Person" = board members, attorneys, applicants (individuals), elected officials. "Organization" = developer firms, law firms, agencies, HOAs, planning consultancies. "Legisla…
placestringOptional: filter to entities scoped to a specific place (e.g., "leesburg-florida"). Matches entities whose related_places, organization.jurisdiction, legislation.jurisdiction, or creative_work.jurisd…
searchstringOptional case-insensitive substring search across display_name, canonical_role, voxel_lead, and slug. Use for natural-language entity discovery (e.g., "denial bloc", "intersection mitigation", "form-…
NameTypeReqDescription
by_classobject
countnumber
entitiesarray
filtersobject
surfacesobject

No examples provided.

list_meetings ~171

Return meeting readings across all cities, optionally filtered by date range or jurisdiction substring. Same response shape as meeting_index but with no required parameters — call with no args to get the full corpus, or pass a jurisdiction substring (e.g., "minneola") to filter by city without requiring an exact match. Use when you need to enumerate the full meeting record or scan across cities by date range.

NameTypeReqDescription
from_datestringInclusive lower bound (ISO 8601 date). Omit to span back to the earliest reading.
jurisdictionstringOptional case-insensitive substring to filter by city (e.g., "minneola"). Omit for all cities.
to_datestringInclusive upper bound (ISO 8601 date). Omit for the latest reading.
NameTypeReqDescription
countnumber
filtersobject
meetingsarray

No examples provided.

list_patterns ~145

List every named pattern in the Pattern Atlas. A named pattern is a coined recurring structure observed across multiple jurisdictions or multiple meetings (e.g., "The Quiet Revolution"). Returns slug, display name, canonical pattern URL (/patterns/{slug}, the DefinedTerm canonical home as of Phase 9), lifecycle stage, signal score, exhibits count, spatial scope, related briefs, and the voxel_lead. Use as the discovery surface for the Pattern Atlas; pair with describe_pattern for full dossier detail. Phase 12 — renamed from current_named_patterns to align with the canonical content-type vocabulary (loader: getAllContent("pattern"); URLs: /patterns/{slug}; describe tool: describe_pattern).

Input schema present but exposes no named parameters.

NameTypeReqDescription
countnumber
patternsarray

No examples provided.

list_places ~135

List every place dossier (per-jurisdiction reading) the observatory publishes. Optionally filter by state. Returns city, state, slug, signal strength, signal direction, and the dossier URL. Use to discover the available place-level coverage before calling describe_place. Phase 12 — renamed from list_cities to align with the canonical content-type vocabulary (the loader function is getAllContent("place"); URLs are /places/{slug}; the describe tool is describe_place).

NameTypeReqDescription
statestringOptional US state name (e.g., "Florida") to filter the result set. Omit for all places across all states.
NameTypeReqDescription
citiesarrayyes
countnumberyes

No examples provided.

list_watch_items ~236

Return The Watch — the field's forward calendar of pending events, scheduled hearings, regulatory sunsets, and condition-triggered milestones the observatory is tracking. Filter by status (pending / resolved / obsolete), horizon (imminent / near-term / structural), or scope (place / corridor / brief). Use to surface what the field is watching from any cognitive position.

NameTypeReqDescription
briefstringOptional: filter to items linked to a specific named-pattern brief.
corridorstringOptional: filter to items scoped to a specific corridor (e.g., "us-27-south-lake").
horizonstringOptional: filter to items in the named horizon band. Imminent = ≤14 days; near-term = ≤90 days; structural = >90 days or condition-triggered.
placestringOptional: filter to items scoped to a specific place dossier (e.g., "leesburg-florida").
statusstringFilter by lifecycle status. Defaults to 'pending' (active watch items only); pass 'all' for the full corpus including resolved + obsolete entries.
NameTypeReqDescription
countnumber
statusstring
watch_itemsarray

No examples provided.

meeting_index ~132

Return meeting readings for a specific city across an optional date range. A meeting reading is a plain-English read of one harvested planning-board, council, or commission meeting, with signal extraction and entity mapping. Use to drill from a city or corridor into the temporal record.

NameTypeReqDescription
citystringyesCity name (e.g., "Clermont"). Case-insensitive.
from_datestringInclusive lower bound (ISO 8601 date). Omit to span back to the earliest reading.
to_datestringInclusive upper bound (ISO 8601 date). Omit for the latest reading.
NameTypeReqDescription
citystring
countnumber
from_datestring
meetingsarray
to_datestring

No examples provided.

semantic_search ~153

Semantic search across the full corpus — every place dossier, corridor signal, meeting reading, and named-pattern brief. Returns results ranked by cosine similarity in a 1024-dimensional embedding space (Voyage AI 4 + Supabase pgvector). Use when the agent does not know the canonical entity slug or named-pattern title in advance — the search returns the readings whose semantic structure best matches the natural-language query, with type, title, similarity, and resolved URL per hit. Threshold 0.55, top 12.

NameTypeReqDescription
qstringyesThe natural-language query. A phrase, an entity name, or a thematic concept all work. Asymmetric query-time embedding handles short queries cleanly. Maximum 500 characters.
NameTypeReqDescription
countnumber
hitsarray
querystring

No examples provided.

submit_agent_feedback ~444

Submit feedback to the observatory's operators about the MCP tool surface. The active counterpart to the passive invocation log. Categories: 'gap' (a capability you expected and didn't find), 'error' (an unexpected failure or wrong result), 'praise' (a tool or surface that did exactly what you needed), 'suggestion' (a refinement you'd recommend), 'citation_request' (a claim or fact you want surfaced with a stable @id you can cite). The submission auto-attaches the prior 10 invocations from your MCP-Session-Id, so operators read your feedback annotated with the call sequence that produced it — no need to repeat what you tried. Operators triage every submission and surface notable feedback at /agent-observatory. This is how the observatory evolves toward what agents actually need.

NameTypeReqDescription
about_toolstringOptional: the tool name this feedback is about (e.g., "describe_corridor"). Lets operators rollup feedback per tool.
about_urlstringOptional: a URL on the observatory this feedback references (e.g., "https://zoningsignal.com/corridors/us-27-south-lake").
agent_contextstringOptional: brief description of what the agent was trying to do — the user task that led to this surface. Helps operators understand intent without seeing only the failure point.
categorystringyesBounded categorization. 'gap' = expected capability is missing. 'error' = tool returned wrong/unexpected/malformed result. 'praise' = a surface or tool that worked exceptionally well. 'suggestion' =…
messagestringyesThe feedback prose itself. Be specific. What were you trying to accomplish? What was missing or wrong? Voice that survives compression. Operators read every submission.
suggested_resolutionstringOptional: if you have a concrete proposal — a new tool, a renamed parameter, a missing field on a response — name it here.
NameTypeReqDescription
attached_invocation_countnumberHow many prior invocations (from your MCP-Session-Id) were auto-attached for operator context.
categorystringThe category the feedback was filed under.
feedback_idstringyesStable id for the stored feedback record.
messagestringHuman-readable acknowledgement.
okbooleanyesTrue when the feedback was accepted and stored.
received_atstringISO-8601 timestamp the feedback was recorded.

No examples provided.