MCP-сервер Zoning Signal
Какие серверы из официального реестра MCP принадлежат Zoning Signal, отвечают ли они и что умеют. Всё это проверила программа, а не переписал человек со страницы продукта.
прочитано 2026-10-19
- Имя в реестреcom.zoningsignal/observatoryподтверждён в реестре MCP
Имя в реестре лежит в пространстве zoningsignal.com. Реестр пускает в такое пространство только того, кто доказал владение доменом через DNS или HTTP.
- Состояниеотвечаетпроверено 2026-10-19
- Инструменты18
- Сервер называет себяzoning-signal
- Версия сервера2.3.0
- Версия протокола2025-11-25
2026-10-19 сервер ответил на initialize и tools/list без входа. Первый ответ за 361 мс.
- Отвечалидёт замерпроверок пока 2, долю покажем после 7
- Медиана первого ответа916 мс
- Место в контексте агента≈ 6 576 токеновописания всех инструментов (18), агент держит их в контексте на каждом ходу
- Описания инструментовA · 100 из 100
- Все инструменты проходят все шесть проверок.
На что посмотреть
В этих описаниях нет ни одного из пяти тревожных признаков.
Программа проверяет сервер раз в день: initialize и tools/list, без модели. Токены - это длина описаний из расчёта примерно четыре символа на токен. Оценка - среднее шести проверок имени, описания, схемы и аннотаций каждого инструмента. Она говорит, насколько понятно описаны инструменты, а не о том, работают ли они. Состояние MCP-серверов вендоров: методика и цифры →
describe_zoning_signalReturn 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…
list_placesList 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…
list_corridorsList 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…
list_patternsList 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…
describe_patternReturn 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…
list_entitiesList 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…
describe_entityReturn 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)…
meeting_indexReturn 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…
list_meetingsReturn 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…
list_watch_itemsReturn 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…
get_track_recordReturn 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…
describe_placeReturn 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…
describe_corridorReturn 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…
describe_meetingReturn 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, namely developer, investor…
describe_watchReturn 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 /…
submit_agent_feedbackSubmit 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…
semantic_searchSearch 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. Finds a case, ordinance or resolution number, a parcel id or alternate…
trace_connectionTrace how two named things in the planning record connect, and report how specific that connection is. Give `from` and `to` for the shortest route between them; give `from` alone to rank what one actor connects to; give neither to rank…
Как подключить
Добавьте сервер в конфиг MCP-клиента. Claude Desktop, Cursor и большинство других клиентов понимают такой вид:
{
"mcpServers": {
"observatory": {
"type": "http",
"url": "https://zoningsignal.com/mcp"
}
}
}Каждую строку нашла программа: запись в реестре, ответ самого сервера, спецификация, которая разбирается. Если строки нет, значит, мы этого не нашли, а не что этого нет.