Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
NORMOT — Israeli building norms is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
Israeli building and planning norms: permits, fire, accessibility; Hebrew text, source, citation.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http normot-israeli-building-norms-mcp https://mcp.normot.co.il/mcp
# 2 — ask your agent for something these tools do
# search_norms, get_norm, list_profile_options and 5 more
NORMOT — Israeli building norms costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DSAll 1 server
danvolsky-source1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http normot-israeli-building-norms-mcp https://mcp.normot.co.il/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Hebrew search words, e.g. מעקה, ממ"ד, רוחב מדרגות |
| limit | integer | no | — |
| offset | integer | no | For the next page; at most 100 (no bulk export) |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Norm id, e.g. u-rb01-preconditions (the last part of https://normot.co.il/u/{id}) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| which | array | no | Only these lists; omit for all |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| use | string | no | Use code, or several comma-separated for a mixed building, e.g. residential or retail,office. See list_profile_options. |
| city | string | no | Municipality slug, e.g. tel-aviv, jerusalem. See list_profile_options. |
| stage | string | no | Project stage |
| status | string | no | New building or existing building |
| height_class | string | no | Building height class |
| track | string | no | Permit track |
| role | string | no | Whose obligations to show, e.g. a role code from list_profile_options |
| site | string | no | Comma-separated plot condition codes that apply; 'none' = checked and none apply; omit = not checked |
| features | string | no | Comma-separated project element codes, e.g. pool; omit = not checked |
| floor_area | number | no | Floor area, m² |
| building_height | number | no | Building height, m |
| storeys | integer | no | — |
| dwelling_units | integer | no | — |
| occupancy | integer | no | Number of occupants |
| beds | integer | no | — |
| rooms | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| use | string | no | Use code, or several comma-separated for a mixed building, e.g. residential or retail,office. See list_profile_options. |
| city | string | no | Municipality slug, e.g. tel-aviv, jerusalem. See list_profile_options. |
| stage | string | no | Project stage |
| status | string | no | New building or existing building |
| height_class | string | no | Building height class |
| track | string | no | Permit track |
| role | string | no | Whose obligations to show, e.g. a role code from list_profile_options |
| site | string | no | Comma-separated plot condition codes that apply; 'none' = checked and none apply; omit = not checked |
| features | string | no | Comma-separated project element codes, e.g. pool; omit = not checked |
| floor_area | number | no | Floor area, m² |
| building_height | number | no | Building height, m |
| storeys | integer | no | — |
| dwelling_units | integer | no | — |
| occupancy | integer | no | Number of occupants |
| beds | integer | no | — |
| rooms | integer | no | — |
| area | string | no | Requirement area code, e.g. fire, egress, protected-space, parking |
| state | string | no | applies = applies; data = depends on missing project data; review = needs a specialist |
| q | string | no | Hebrew words to filter by |
| offset | integer | no | Multiple of 50 for the next page |
For one norm and a project profile: does it apply, why (by use, authority, stage) and which conditions could change that.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| use | string | no | Use code, or several comma-separated for a mixed building, e.g. residential or retail,office. See list_profile_options. |
| city | string | no | Municipality slug, e.g. tel-aviv, jerusalem. See list_profile_options. |
| stage | string | no | Project stage |
| status | string | no | New building or existing building |
| height_class | string | no | Building height class |
| track | string | no | Permit track |
| role | string | no | Whose obligations to show, e.g. a role code from list_profile_options |
| site | string | no | Comma-separated plot condition codes that apply; 'none' = checked and none apply; omit = not checked |
| features | string | no | Comma-separated project element codes, e.g. pool; omit = not checked |
| floor_area | number | no | Floor area, m² |
| building_height | number | no | Building height, m |
| storeys | integer | no | — |
| dwelling_units | integer | no | — |
| occupancy | integer | no | Number of occupants |
| beds | integer | no | — |
| rooms | integer | no | — |
| id | string | yes | Norm id |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phase | string | no | Phase code from the overview, e.g. submission, design_control |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| use | string | no | Use code, or several comma-separated for a mixed building, e.g. residential or retail,office. See list_profile_options. |
| city | string | no | Municipality slug, e.g. tel-aviv, jerusalem. See list_profile_options. |
| stage | string | no | Project stage |
| status | string | no | New building or existing building |
| height_class | string | no | Building height class |
| track | string | no | Permit track |
| role | string | no | Whose obligations to show, e.g. a role code from list_profile_options |
| site | string | no | Comma-separated plot condition codes that apply; 'none' = checked and none apply; omit = not checked |
| features | string | no | Comma-separated project element codes, e.g. pool; omit = not checked |
| floor_area | number | no | Floor area, m² |
| building_height | number | no | Building height, m |
| storeys | integer | no | — |
| dwelling_units | integer | no | — |
| occupancy | integer | no | Number of occupants |
| beds | integer | no | — |
| rooms | integer | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install NORMOT — Israeli building norms or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 0.1.0 · scanned 7 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestbd976b5d8e7104997f3422f54ae009dbb7b466be65aa2789e894e48442a36f05
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_norms | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_norm | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_profile_options | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| project_overview | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| project_requirements | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_norm_for_project | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| permit_stages | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| source_changes | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestbd976b5d8e710499
Scanned2026-11-07
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish NORMOT — Israeli building norms can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.