Analytics

zoningsignal.com

Provides structured analytics and dossiers on zoning signals, patterns, and jurisdictional data for urban and land-use observatory purposes.

1 endpoint18 known toolsFirst detected May 28, 2026Last detected September 26, 2026

ENDPOINT 1

https://zoningsignal.com/mcp

No auth detected

MCP server metadata

Name: zoning-signal
Version: 2.3.0

Capabilities

toolsresourcespromptscompletionslogging

Server instructions

Zoning Signal: read-only planning and zoning records for 25 Central Florida jurisdictions in Lake, Orange, Osceola, Polk and Seminole counties, from 2024 on. Meeting agendas and minutes, place dossiers, corridors, named patterns and briefs, entities and watch items, each with citation-stable claims. The coverage resource (https://zoningsignal.com/coverage.json) lists every jurisdiction by county and the date range; coverage is exactly that list, so a county is covered only through the jurisdictions listed under it (the one county government covered is Lake County, for its unincorporated area). Start with semantic_search for any name, number or question; describe_* tools return structured records with claims[]; list_* tools enumerate each type. Dossier tools take a lens: synthesis (default), developer, investor, broker, attorney, business, resident or civic-leader.

Known tools 18

describe_zoning_signal

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.

Inferred read-only

list_places

List every place dossier (per-jurisdiction reading) the observatory publishes.

Inferred read-only

list_corridors

List every published corridor page.

Inferred read-only

list_patterns

List every named pattern in the Pattern Atlas.

Inferred read-only

describe_pattern

Return the full dossier for a named pattern: voxel_lead, signal_status (horizon/confidence), 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).

Inferred read-only

list_entities

List every named entity in the Decoder Index — the smallest citable unit of authority in the corpus.

Inferred read-only

describe_entity

Return the full structured dossier for a named entity — the canonical citable artifact for any actor, organization, ordinance, or project the corpus references.

Inferred read-only

meeting_index

Return meeting readings for a specific city across an optional date range.

Inferred read-only

list_meetings

Return meeting readings across all cities, optionally filtered by date range or jurisdiction substring.

Inferred read-only

list_watch_items

Return The Watch — the field's forward calendar of pending events, scheduled hearings, regulatory sunsets, and condition-triggered milestones the observatory is tracking.

Inferred read-only

get_track_record

Return the observatory's public calibration scorecard — the aggregate accuracy of past watch-item directional reads, horizon calls, and significance assessments across resolved watches.

Inferred read-only

describe_place

Return the dossier projection for a city, in the requested cognitive lens.

Inferred read-only

describe_corridor

Return the dossier projection for a corridor, in the requested cognitive lens.

Inferred read-only

describe_meeting

Return the full dossier projection for a meeting reading, in the requested cognitive lens.

Inferred read-only

describe_watch

Return the full dossier for a watch item — the observatory's forward-looking observation primitive.

Inferred read-only

submit_agent_feedback

Submit feedback to the observatory's operators about the MCP tool surface.

Inferred read-only

semantic_search

Search every record by exact words and by meaning at once: meeting agendas and minutes, place dossiers, corridors, named patterns and briefs, entities and watch items.

Inferred read-only

trace_connection

Trace how two named things in the planning record connect, and report how specific that connection is.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.zoning-signal]
url = "https://zoningsignal.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "zoning-signal": {
      "type": "http",
      "url": "https://zoningsignal.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: zoning-signal
Remote MCP URL: https://zoningsignal.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "zoning-signal": {
      "url": "https://zoningsignal.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "zoning-signal": {
      "type": "http",
      "url": "https://zoningsignal.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "zoning-signal",
  "transport": "streamable-http",
  "url": "https://zoningsignal.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for zoningsignal.com was fetched 2026-08-21T19:46:25.069Z and is being refreshed.

Trust status Neutral

zoningsignal.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.