Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Edifiable 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.
What it does
French land-use plans (PLU): what a zone or a street allows, cited at the article. No key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http edifiable-mcp https://edifiable.fr/mcp
# 2 — ask your agent for something these tools do
# get_french_urbanism_zone_rules, search_french_urbanism_regulation, get_french_urbanism_rules_for_street and 1 more
Edifiable costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 edifiable-mcp https://edifiable.fr/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
4 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.
Ce qu'une zone d'un plan local d'urbanisme francais autorise. Quand la commune est compilee, les regles en clair - hauteur, emprise, reculs, stationnement, espaces verts - chacune avec sa valeur, la condition qui la declenche et la phrase du reglement qui la porte ; puis le texte integral des articles de la zone. Meme texte que le jumeau .md de la page de zone. Un document qui ne suit pas la numer
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code_insee | string | yes | Code INSEE de la commune, cinq caracteres, par exemple 31395 (Muret). |
| zone | string | yes | Code de zone du plan local d'urbanisme, par exemple UA, UB, AU, A ou N. |
Cherche des mots dans le texte du reglement d'urbanisme d'une commune francaise et rend les articles qui les contiennent, avec leur zone et leur numero. Utile quand on ne sait pas dans quel article une regle se trouve : cloture, piscine, toiture, stationnement.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code_insee | string | yes | Code INSEE de la commune, cinq caracteres, par exemple 31395 (Muret). |
| mots | string | yes | Les mots a chercher, par exemple « hauteur ». |
La zone du plan local d'urbanisme au droit d'une rue francaise et ce que le reglement en dit : les regles du chapitre avec les cas propres au secteur en avant, ce que le plan graphique impose ici, les autres zones que la voie longe a 120 m, les prescriptions et servitudes dessinees autour, les pieces du permis que le terrain declenche. Meme texte que le jumeau .md de la page de rue. Avec le numero
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code_insee | string | yes | Code INSEE de la commune, cinq caracteres, par exemple 31395 (Muret). |
| voie | string | yes | Nom de la voie en toutes lettres, par exemple « avenue Jacques Douzans ». |
| numero | string | no | Le numero dans la voie, par exemple « 22 » ou « 12 bis » : rend le terrain de ce numero. Sans lui, la voie au point. |
Les pieces a joindre a une demande de permis de construire pour une maison individuelle en France (formulaire Cerfa 13406*15), en distinguant celles qui sont exigees partout de celles que le terrain declenche : sismicite, plan de prevention des risques, monument historique. Faits lus au centre de la commune, pas a une adresse.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code_insee | string | yes | Code INSEE de la commune, cinq caracteres, par exemple 31395 (Muret). |
- 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 Edifiable or to call it, at any volume.
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.
| 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 |
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.
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 |
|---|---|---|
| get_french_urbanism_zone_rules | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search_french_urbanism_regulation | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_french_urbanism_rules_for_street | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_french_building_permit_pieces | 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
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.
No release note was published with this version.
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.
Any signed-in account that does not publish Edifiable can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.