Zoning Signal is a remote MCP server that gives an AI agent 17 tools, among them describe_corridor, describe_entity, describe_meeting. It answers at https://zoningsignal.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Planning and zoning records: 25 jurisdictions in Lake, Orange, Osceola, Polk, Seminole counties, FL
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
describe_corridor | 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 dos Inputs: slug, lens |
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. Returns: voxel_lead (134-167 word voxel-disciplined identity prose), canonical_ Inputs: slug |
describe_meeting | 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, a Inputs: slug, lens |
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, Inputs: slug |
describe_place | 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 Inputs: slug, lens |
describe_watch | 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 (horizon / con Inputs: slug |
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. Call once per session to ground subsequent tool calls i |
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. Returns: total_resolved, directional accuracy (aligned Inputs: jurisdiction, corridor, brief |
list_corridors | 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, prima |
list_entities | 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 Perso Inputs: entity_class, place, search |
list_meetings | 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 Inputs: jurisdiction, from_date, to_date |
list_patterns | 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 (/p |
list_places | 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 Inputs: state |
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. Filter by status (pending / resolved / obsolete), horizon (imminent / Inputs: status, horizon, place, corridor, brief |
meeting_index | 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 fr Inputs: city, from_date, to_date |
semantic_search | 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). Us Inputs: q |
submit_agent_feedback | 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), Inputs: category, message, about_tool, about_url, agent_context, suggested_resolution |
Every block below points at https://zoningsignal.com/mcp. Pick your client and copy.
claude mcp add --transport http zoning-signal https://zoningsignal.com/mcp
{
"mcpServers": {
"zoning-signal": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://zoningsignal.com/mcp"]
}
}
}{
"mcpServers": {
"zoning-signal": {
"url": "https://zoningsignal.com/mcp"
}
}
}{
"servers": {
"zoning-signal": {
"type": "http",
"url": "https://zoningsignal.com/mcp"
}
}
}{
"context_servers": {
"zoning-signal": {
"url": "https://zoningsignal.com/mcp"
}
}
}{
"mcpServers": {
"zoning-signal": {
"serverUrl": "https://zoningsignal.com/mcp"
}
}
}{
"mcpServers": {
"zoning-signal": {
"url": "https://zoningsignal.com/mcp"
}
}
}name: Zoning Signal
version: 0.0.1
schema: v1
mcpServers:
- name: Zoning Signal
type: streamable-http
url: https://zoningsignal.com/mcp{
"mcpServers": {
"zoning-signal": {
"httpUrl": "https://zoningsignal.com/mcp"
}
}
}{
"mcpServers": {
"zoning-signal": {
"type": "http",
"url": "https://zoningsignal.com/mcp"
}
}
}{
"mcpServers": {
"zoning-signal": {
"url": "https://zoningsignal.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fzoningsignal.com%2Fmcp&type=streamable_http&id=zoning-signal&name=Zoning%20Signal
It answered our last check on 18 October 2026 in 546 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by zoningsignal.com and served from zoningsignal.com, the vendor's own domain: https://zoningsignal.com/mcp.
17, as returned by the server's own tools/list on 31 August 2026: describe_corridor, describe_entity, describe_meeting, describe_pattern, describe_place, describe_watch, describe_zoning_signal, get_track_record, and 9 more.
It answered our last check on 18 October 2026 in 546 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://zoningsignal.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.zoningsignal. Endpoint host: zoningsignal.com. ARD identifier: urn:air:com.zoningsignal:mcp:observatory.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.