# NORMOT — Israeli building norms (remote · mcp.normot.co.il)

Israeli building and planning norms: permits, fire, accessibility; Hebrew text, source, citation.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.normot.co.il`: 77/100 (this document), [markdown](https://verifymcp.io/servers/danvolsky-source-normot/mcp.md), [page](https://verifymcp.io/servers/danvolsky-source-normot/mcp)

## Channel facts

- Endpoint: `https://mcp.normot.co.il/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2713 tokens (~339/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the NORMOT — Israeli building norms MCP server?

NORMOT — Israeli building norms is a hosted endpoint at https://mcp.normot.co.il/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http danvolsky-source-normot 'https://mcp.normot.co.il/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "danvolsky-source-normot": {
      "url": "https://mcp.normot.co.il/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "danvolsky-source-normot": {
      "type": "http",
      "url": "https://mcp.normot.co.il/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.danvolsky-source-normot]
url = "https://mcp.normot.co.il/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "danvolsky-source-normot": {
      "type": "remote",
      "url": "https://mcp.normot.co.il/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add danvolsky-source-normot --url 'https://mcp.normot.co.il/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  danvolsky-source-normot:
    url: "https://mcp.normot.co.il/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "danvolsky-source-normot": {
      "Transport": "http",
      "Url": "https://mcp.normot.co.il/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add danvolsky-source-normot -t streamable-http -u 'https://mcp.normot.co.il/mcp'
```

### Other

```json
{
  "mcpServers": {
    "danvolsky-source-normot": {
      "type": "http",
      "url": "https://mcp.normot.co.il/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 77, +1)

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

### 2026-11-18 (score 76, +1)

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

### 2026-11-16 (score 75, +1)

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

### 2026-11-14 (score 74, +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.

### 2026-11-12 (score 73, +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.

### 2026-11-10 (score 72, +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.

### 2026-11-08 (score 71, +1)

- [functional regression] Schema quality: 234 → 339
- [functional improvement] Tool coverage: 77% → 100%
- [functional] Server version: 0.1.0 → 0.1.1
- [cosmetic] “check_norm_for_project” reworded the description of “beds”
- [cosmetic] “check_norm_for_project” reworded the description of “building_height”
- [cosmetic] “check_norm_for_project” reworded the description of “dwelling_units”
- [cosmetic] “check_norm_for_project” reworded the description of “features”
- [cosmetic] “check_norm_for_project” reworded the description of “floor_area”
- [cosmetic] “check_norm_for_project” reworded the description of “height_class”
- [cosmetic] “check_norm_for_project” reworded the description of “id”
- [cosmetic] “check_norm_for_project” reworded the description of “occupancy”
- [cosmetic] “check_norm_for_project” reworded the description of “role”
- [cosmetic] “check_norm_for_project” reworded the description of “rooms”
- [cosmetic] “check_norm_for_project” reworded the description of “stage”
- [cosmetic] “check_norm_for_project” reworded the description of “status”
- [cosmetic] “check_norm_for_project” reworded the description of “storeys”
- [cosmetic] “check_norm_for_project” reworded the description of “track”
- [cosmetic] “project_overview” reworded the description of “beds”
- [cosmetic] “project_overview” reworded the description of “building_height”
- [cosmetic] “project_overview” reworded the description of “dwelling_units”
- [cosmetic] “project_overview” reworded the description of “features”
- [cosmetic] “project_overview” reworded the description of “floor_area”
- [cosmetic] “project_overview” reworded the description of “height_class”
- [cosmetic] “project_overview” reworded the description of “occupancy”
- [cosmetic] “project_overview” reworded the description of “role”
- [cosmetic] “project_overview” reworded the description of “rooms”
- [cosmetic] “project_overview” reworded the description of “stage”
- [cosmetic] “project_overview” reworded the description of “status”
- [cosmetic] “project_overview” reworded the description of “storeys”
- [cosmetic] “project_overview” reworded the description of “track”
- [cosmetic] “project_requirements” reworded the description of “beds”
- [cosmetic] “project_requirements” reworded the description of “building_height”
- [cosmetic] “project_requirements” reworded the description of “dwelling_units”
- [cosmetic] “project_requirements” reworded the description of “features”
- [cosmetic] “project_requirements” reworded the description of “floor_area”
- [cosmetic] “project_requirements” reworded the description of “height_class”
- [cosmetic] “project_requirements” reworded the description of “occupancy”
- [cosmetic] “project_requirements” reworded the description of “role”
- [cosmetic] “project_requirements” reworded the description of “rooms”
- [cosmetic] “project_requirements” reworded the description of “stage”
- [cosmetic] “project_requirements” reworded the description of “status”
- [cosmetic] “project_requirements” reworded the description of “storeys”
- [cosmetic] “project_requirements” reworded the description of “track”
- [cosmetic] “search_norms” reworded the description of “limit”
- [cosmetic] “source_changes” reworded the description of “beds”
- [cosmetic] “source_changes” reworded the description of “building_height”
- [cosmetic] “source_changes” reworded the description of “dwelling_units”
- [cosmetic] “source_changes” reworded the description of “features”
- [cosmetic] “source_changes” reworded the description of “floor_area”
- [cosmetic] “source_changes” reworded the description of “height_class”
- [cosmetic] “source_changes” reworded the description of “occupancy”
- [cosmetic] “source_changes” reworded the description of “role”
- [cosmetic] “source_changes” reworded the description of “rooms”
- [cosmetic] “source_changes” reworded the description of “stage”
- [cosmetic] “source_changes” reworded the description of “status”
- [cosmetic] “source_changes” reworded the description of “storeys”
- [cosmetic] “source_changes” reworded the description of “track”

### 2026-11-07 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (8)

### `search_norms` (~114 tokens)

Search norms

Search Israeli building and planning norms by Hebrew words (substring search over norm texts, sections and document titles; norms in force come first). Returns norms with their permanent URL; call get_norm for the full text and citation.

Input parameters:

- `limit` (integer): How many norms to return, 1–20
- `offset` (integer): For the next page; at most 100 (no bulk export)
- `query` (string, required): Hebrew search words, e.g. מעקה, ממ"ד, רוחב מדרגות

### `get_norm` (~85 tokens)

Get one norm

One norm by id: full Hebrew text, applicability, source document and section, dates in force, numeric values, exceptions, how its text was checked against print (print_check), and a ready citation line (cite).

Input parameters:

- `id` (string, required): Norm id, e.g. u-rb01-preconditions (the last part of https://normot.co.il/u/{id})

### `list_profile_options` (~71 tokens)

List project profile options

Valid codes for a project profile: uses, stages, cities (municipality slugs), plot conditions (sites), project elements (features), roles and requirement areas. Call before project_overview or project_requirements if unsure of a code.

Input parameters:

- `which` (array): Only these lists; omit for all

### `project_overview` (~507 tokens)

Project overview (what applies)

For a project profile (use, city, stage and optional details): how many norms apply, which depend on missing data or need a specialist, the next permit actions with their legal source, and which questions would narrow the list most. Every omitted detail keeps norms in (over-inclusive by design).

Input parameters:

- `beds` (integer): Number of beds, e.g. in a hotel, hospital or care home; used for thresholds in norms
- `building_height` (number): Building height, m; used for height thresholds in norms
- `city` (string): Municipality slug, e.g. tel-aviv, jerusalem. See list_profile_options.
- `dwelling_units` (integer): Number of dwelling units (apartments)
- `features` (string): Comma-separated project element codes from list_profile_options (features), e.g. pool; 'none' = checked and none apply; omit = not checked
- `floor_area` (number): Floor area, m²; used for area thresholds in norms
- `height_class` (string): Building height class: low, high or multistory. Omit if unknown (no norm is excluded)
- `occupancy` (integer): Number of occupants; used for occupancy thresholds in norms
- `role` (string): Show the norms for one party, e.g. architect, developer, fire (fire safety consultant), authority: a role code from list_profile_options. Omit for all parties
- `rooms` (integer): Number of rooms; used for thresholds in norms
- `site` (string): Comma-separated plot condition codes that apply; 'none' = checked and none apply; omit = not checked
- `stage` (string): Project stage: feasibility (היתכנות ותכנון ראשוני), design (תכנון מפורט), permit (רישוי ובקשה להיתר), execution (ביצוע באתר), completion (גמר וטופס 4), operation (תפעול ותחזוקה). Omit = all stages
- `status` (string): new = new building; existing = existing building
- `storeys` (integer): Number of storeys; used for thresholds in norms
- `track` (string): Permit track: standard, short or fast. Omit if unknown (no norm is excluded)
- `use` (string): Use code, or several comma-separated for a mixed building, e.g. residential or retail,office. See list_profile_options.

### `project_requirements` (~574 tokens)

Project requirements

The norms that apply to a project profile, 50 per page, filterable by requirement area (e.g. fire, egress, parking, accessibility), by state and by Hebrew words. Texts are clipped; call get_norm for the full text.

Input parameters:

- `area` (string): Requirement area code, e.g. fire, egress, protected-space, parking
- `beds` (integer): Number of beds, e.g. in a hotel, hospital or care home; used for thresholds in norms
- `building_height` (number): Building height, m; used for height thresholds in norms
- `city` (string): Municipality slug, e.g. tel-aviv, jerusalem. See list_profile_options.
- `dwelling_units` (integer): Number of dwelling units (apartments)
- `features` (string): Comma-separated project element codes from list_profile_options (features), e.g. pool; 'none' = checked and none apply; omit = not checked
- `floor_area` (number): Floor area, m²; used for area thresholds in norms
- `height_class` (string): Building height class: low, high or multistory. Omit if unknown (no norm is excluded)
- `occupancy` (integer): Number of occupants; used for occupancy thresholds in norms
- `offset` (integer): Multiple of 50 for the next page
- `q` (string): Hebrew words to filter by
- `role` (string): Show the norms for one party, e.g. architect, developer, fire (fire safety consultant), authority: a role code from list_profile_options. Omit for all parties
- `rooms` (integer): Number of rooms; used for thresholds in norms
- `site` (string): Comma-separated plot condition codes that apply; 'none' = checked and none apply; omit = not checked
- `stage` (string): Project stage: feasibility (היתכנות ותכנון ראשוני), design (תכנון מפורט), permit (רישוי ובקשה להיתר), execution (ביצוע באתר), completion (גמר וטופס 4), operation (תפעול ותחזוקה). Omit = all stages
- `state` (string): applies = applies; data = depends on missing project data; review = needs a specialist
- `status` (string): new = new building; existing = existing building
- `storeys` (integer): Number of storeys; used for thresholds in norms
- `track` (string): Permit track: standard, short or fast. Omit if unknown (no norm is excluded)
- `use` (string): Use code, or several comma-separated for a mixed building, e.g. residential or retail,office. See list_profile_options.

### `check_norm_for_project` (~504 tokens)

Why a norm applies to a project

For one norm and a project profile: does it apply, why (by use, authority, stage) and which conditions could change that.

Input parameters:

- `beds` (integer): Number of beds, e.g. in a hotel, hospital or care home; used for thresholds in norms
- `building_height` (number): Building height, m; used for height thresholds in norms
- `city` (string): Municipality slug, e.g. tel-aviv, jerusalem. See list_profile_options.
- `dwelling_units` (integer): Number of dwelling units (apartments)
- `features` (string): Comma-separated project element codes from list_profile_options (features), e.g. pool; 'none' = checked and none apply; omit = not checked
- `floor_area` (number): Floor area, m²; used for area thresholds in norms
- `height_class` (string): Building height class: low, high or multistory. Omit if unknown (no norm is excluded)
- `id` (string, required): Norm id from search_norms or project_requirements, e.g. u-rb01-preconditions
- `occupancy` (integer): Number of occupants; used for occupancy thresholds in norms
- `role` (string): Show the norms for one party, e.g. architect, developer, fire (fire safety consultant), authority: a role code from list_profile_options. Omit for all parties
- `rooms` (integer): Number of rooms; used for thresholds in norms
- `site` (string): Comma-separated plot condition codes that apply; 'none' = checked and none apply; omit = not checked
- `stage` (string): Project stage: feasibility (היתכנות ותכנון ראשוני), design (תכנון מפורט), permit (רישוי ובקשה להיתר), execution (ביצוע באתר), completion (גמר וטופס 4), operation (תפעול ותחזוקה). Omit = all stages
- `status` (string): new = new building; existing = existing building
- `storeys` (integer): Number of storeys; used for thresholds in norms
- `track` (string): Permit track: standard, short or fast. Omit if unknown (no norm is excluded)
- `use` (string): Use code, or several comma-separated for a mixed building, e.g. residential or retail,office. See list_profile_options.

### `permit_stages` (~107 tokens)

Building permit stages (Rishuy Zamin)

The building-permit process mapped to the stages of the Planning Administration's online system רישוי זמין, with the norms behind each step, plus how the database's texts were checked and the measured error rates. Without a phase: an overview of all phases. With a phase code: its steps and norms. The mapping is NORMOT's work, not a Planning Administration publication.

Input parameters:

- `phase` (string): Phase code from the overview, e.g. submission, design_control

### `source_changes` (~487 tokens)

Recent source changes

What NORMOT's monitor detected in its sources (changed documents, expiring norms, latest Reshumot issues) and what was verified. With a profile, only documents relevant to that project.

Input parameters:

- `beds` (integer): Number of beds, e.g. in a hotel, hospital or care home; used for thresholds in norms
- `building_height` (number): Building height, m; used for height thresholds in norms
- `city` (string): Municipality slug, e.g. tel-aviv, jerusalem. See list_profile_options.
- `dwelling_units` (integer): Number of dwelling units (apartments)
- `features` (string): Comma-separated project element codes from list_profile_options (features), e.g. pool; 'none' = checked and none apply; omit = not checked
- `floor_area` (number): Floor area, m²; used for area thresholds in norms
- `height_class` (string): Building height class: low, high or multistory. Omit if unknown (no norm is excluded)
- `occupancy` (integer): Number of occupants; used for occupancy thresholds in norms
- `role` (string): Show the norms for one party, e.g. architect, developer, fire (fire safety consultant), authority: a role code from list_profile_options. Omit for all parties
- `rooms` (integer): Number of rooms; used for thresholds in norms
- `site` (string): Comma-separated plot condition codes that apply; 'none' = checked and none apply; omit = not checked
- `stage` (string): Project stage: feasibility (היתכנות ותכנון ראשוני), design (תכנון מפורט), permit (רישוי ובקשה להיתר), execution (ביצוע באתר), completion (גמר וטופס 4), operation (תפעול ותחזוקה). Omit = all stages
- `status` (string): new = new building; existing = existing building
- `storeys` (integer): Number of storeys; used for thresholds in norms
- `track` (string): Permit track: standard, short or fast. Omit if unknown (no norm is excluded)
- `use` (string): Use code, or several comma-separated for a mixed building, e.g. residential or retail,office. See list_profile_options.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/danvolsky-source-normot/mcp#diagnostics

## Score history

- 2026-11-21: 77
- 2026-11-20: 77
- 2026-11-19: 76
- 2026-11-18: 76
- 2026-11-17: 75
- 2026-11-16: 75
- 2026-11-15: 74
- 2026-11-14: 74
- 2026-11-13: 73
- 2026-11-12: 73
- 2026-11-11: 72
- 2026-11-10: 72
- 2026-11-09: 71
- 2026-11-08: 71
- 2026-11-07: 70
- 2026-11-06: 69

## Common questions

### What is the NORMOT — Israeli building norms MCP server?

NORMOT — Israeli building norms is an MCP server listed in the public MCP registry as io.github.danvolsky-source/normot. Israeli building and planning norms: permits, fire, accessibility; Hebrew text, source, citation. This page covers its hosted endpoint (https://mcp.normot.co.il/mcp).

### Is the NORMOT — Israeli building norms MCP server safe to use?

NORMOT — Israeli building norms scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the NORMOT — Israeli building norms MCP server expose?

NORMOT — Israeli building norms exposes 8 tools: search_norms, get_norm, list_profile_options, project_overview, project_requirements, and 3 more. Their descriptions and schemas cost roughly 2,449 tokens of context every time the server is loaded.

### Does the NORMOT — Israeli building norms MCP server require authentication?

No. We connected to NORMOT — Israeli building norms without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the NORMOT — Israeli building norms MCP server still maintained?

NORMOT — Israeli building norms is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the NORMOT — Israeli building norms MCP server?

VerifyMCP ran 13 checks on NORMOT — Israeli building norms, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.normot.co.il/mcp
- Repository: https://github.com/danvolsky-source/normot-mcp
- Website: https://normot.co.il/
- Changelog RSS feed: https://verifymcp.io/servers/danvolsky-source-normot/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/danvolsky-source-normot/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/danvolsky-source-normot/mcp.json
- HTML version of this page: https://verifymcp.io/servers/danvolsky-source-normot/mcp
