# Edifiable (remote · edifiable.fr)

French land-use plans (PLU): what a zone or a street allows, cited at the article. No key.

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

## Components

- remote · `edifiable.fr`: 74/100 (this document), [markdown](https://verifymcp.io/servers/fr-edifiable-edifiable/edifiable.md), [page](https://verifymcp.io/servers/fr-edifiable-edifiable/edifiable)

## Channel facts

- Endpoint: `https://edifiable.fr/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## 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-09-20.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 911 tokens (~227/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Edifiable MCP server?

Edifiable is a hosted endpoint at https://edifiable.fr/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 fr-edifiable-edifiable 'https://edifiable.fr/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "fr-edifiable-edifiable": {
      "url": "https://edifiable.fr/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fr-edifiable-edifiable": {
      "type": "http",
      "url": "https://edifiable.fr/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fr-edifiable-edifiable]
url = "https://edifiable.fr/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fr-edifiable-edifiable": {
      "type": "remote",
      "url": "https://edifiable.fr/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fr-edifiable-edifiable --url 'https://edifiable.fr/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fr-edifiable-edifiable:
    url: "https://edifiable.fr/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fr-edifiable-edifiable": {
      "Transport": "http",
      "Url": "https://edifiable.fr/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fr-edifiable-edifiable -t streamable-http -u 'https://edifiable.fr/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fr-edifiable-edifiable": {
      "type": "http",
      "url": "https://edifiable.fr/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-09-19 (score 74, +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-09-17 (score 73, +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-09-15 (score 72, +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-09-13 (score 71, +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-09-11 (score 70, 0)

- [security] Tool “get_french_urbanism_rules_for_street” rewrote its description, which is the text the model reads
- [functional] Schema quality: excellent → good
- [cosmetic] “get_french_urbanism_rules_for_street” added an optional parameter “numero”

### 2026-09-10 (score 70, +1)

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

### 2026-09-08 (score 69, +3)

- [security improvement] HSTS header: fail → pass

### 2026-09-06 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (4)

### `get_french_urbanism_zone_rules` (~188 tokens)

Regles d'urbanisme d'une zone en France

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 numerotation attendue rend zero article, et l'outil le dit plutot que de deviner.

Input parameters:

- `code_insee` (string, required): Code INSEE de la commune, cinq caracteres, par exemple 31395 (Muret).
- `zone` (string, required): Code de zone du plan local d'urbanisme, par exemple UA, UB, AU, A ou N.

### `search_french_urbanism_regulation` (~119 tokens)

Chercher dans le reglement d'urbanisme d'une commune francaise

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.

Input parameters:

- `code_insee` (string, required): Code INSEE de la commune, cinq caracteres, par exemple 31395 (Muret).
- `mots` (string, required): Les mots a chercher, par exemple « hauteur ».

### `get_french_urbanism_rules_for_street` (~244 tokens)

Regles d'urbanisme applicables a une rue en France

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 de rue : le terrain de ce numero - ses parcelles cadastrales reunies, ce qui les reunit, la zone lue a son contour et les chiffres du reglement ramenes a lui.

Input parameters:

- `code_insee` (string, required): Code INSEE de la commune, cinq caracteres, par exemple 31395 (Muret).
- `numero` (string): Le numero dans la voie, par exemple « 22 » ou « 12 bis » : rend le terrain de ce numero. Sans lui, la voie au point.
- `voie` (string, required): Nom de la voie en toutes lettres, par exemple « avenue Jacques Douzans ».

### `get_french_building_permit_pieces` (~114 tokens)

Pieces d'un permis de construire en France

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.

Input parameters:

- `code_insee` (string, required): Code INSEE de la commune, cinq caracteres, par exemple 31395 (Muret).

## Diagnostics

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

## Score history

- 2026-09-20: 74
- 2026-09-19: 74
- 2026-09-18: 73
- 2026-09-17: 73
- 2026-09-16: 72
- 2026-09-15: 72
- 2026-09-14: 71
- 2026-09-13: 71
- 2026-09-12: 70
- 2026-09-11: 70
- 2026-09-10: 70
- 2026-09-09: 69
- 2026-09-08: 69
- 2026-09-07: 66
- 2026-09-06: 66
- 2026-09-05: 65

## Common questions

### What is the Edifiable MCP server?

Edifiable is an MCP server listed in the public MCP registry as fr.edifiable/edifiable. French land-use plans (PLU): what a zone or a street allows, cited at the article. No key. This page covers its hosted endpoint (https://edifiable.fr/mcp).

### Is the Edifiable MCP server safe to use?

Edifiable scores 74 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 Edifiable MCP server expose?

Edifiable exposes 4 tools: get_french_urbanism_zone_rules, search_french_urbanism_regulation, get_french_urbanism_rules_for_street, get_french_building_permit_pieces. Their descriptions and schemas cost roughly 665 tokens of context every time the server is loaded.

### Does the Edifiable MCP server require authentication?

No. We connected to Edifiable without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Edifiable MCP server still maintained?

Edifiable is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://edifiable.fr/mcp
- Website: https://edifiable.fr/api
- Changelog RSS feed: https://verifymcp.io/servers/fr-edifiable-edifiable/edifiable.xml
- Changelog JSON feed: https://verifymcp.io/servers/fr-edifiable-edifiable/edifiable.json
- HTML version of this page: https://verifymcp.io/servers/fr-edifiable-edifiable/edifiable