NORMOT — Israeli building norms
REMOTE · MCP.NORMOT.CO.IL
Israeli building and planning norms: permits, fire, accessibility; Hebrew text, source, citation.
Available components
Last scanned (18 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Documents and Files
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 → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +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.
- 18 Nov 26 +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.
- 16 Nov 26 +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.
- 14 Nov 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.
- 12 Nov 26 +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.
- 10 Nov 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.
- 8 Nov 26 +1
- Schema quality: 234 → 339 ▼ functional
- Tool coverage: 77% → 100% ▲ functional
- Server version: 0.1.0 → 0.1.1 functional
- “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” cosmetic
- 7 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
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 21 Nov 2026 · Probed https://mcp.normot.co.il/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.normot.co.il | CN=YR2,O=Let's Encrypt,C=US | 5 Nov 2026 | 3 Feb 2027 | RSA 2048 | SHA256-RSA | 62e9dac621d73badec3003ebb1c0f3665c1 |
| SANs: mcp.normot.co.il | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.normot.co.il. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| il. | DS published | 35088 | 13 | Verified |
| co.il. | DS published | 7144 | 13 | Verified |
| normot.co.il. | No DS | 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 |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.normot.co.il/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.normot.co.il/mcp | HTTPS enforced | 308 | https://mcp.normot.co.il/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_norm_for_project Why a norm applies to a project ~504
For one norm and a project profile: does it apply, why (by use, authority, stage) and which conditions could change that.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
get_norm Get one norm ~85
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).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Norm id, e.g. u-rb01-preconditions (the last part of https://normot.co.il/u/{id}) |
No output schema declared.
No examples provided.
list_profile_options List project profile options ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| which | array | – | Only these lists; omit for all |
No output schema declared.
No examples provided.
permit_stages Building permit stages (Rishuy Zamin) ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| phase | string | – | Phase code from the overview, e.g. submission, design_control |
No output schema declared.
No examples provided.
project_overview Project overview (what applies) ~507
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
project_requirements Project requirements ~574
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
search_norms Search norms ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many norms to return, 1–20 |
| offset | integer | – | For the next page; at most 100 (no bulk export) |
| query | string | yes | Hebrew search words, e.g. מעקה, ממ"ד, רוחב מדרגות |
No output schema declared.
No examples provided.
source_changes Recent source changes ~487
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · mcp.normot.co.il
claude mcp add --transport http danvolsky-source-normot 'https://mcp.normot.co.il/mcp'
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.