edifiable
Registry code: ee439ea0ffb1c4be
Edifiable lit les documents d'urbanisme francais deposes au Geoportail de l'urbanisme et repond a
quatre questions : ce que le reglement d'une zone autorise (hauteur, emprise, reculs, stationnement),
- endpoint
- https://edifiable.fr/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is edifiable live?
- Yes — it answered the hub's last check (checked 4m ago). It answered 99% of checks over the last 30 days.
- Is edifiable free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does edifiable have?
- 4 tools: get_french_urbanism_zone_rules, search_french_urbanism_regulation, get_french_building_permit_pieces, get_french_urbanism_rules_for_street.
- Is edifiable safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.6%· all time 99.6%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- topic
- government & legal legal
- used for
- get french zoning rules for a plan zone
- find which zone applies to a street
- search a commune's urban planning regulation
- list documents for a french building permit
- takes → gives
- text → text, data
- tools
- 4 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_french_urbanism_zone_rules reads unknown 14h ago
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.
{ "type": "object", "required": [ "code_insee", "zone" ], "properties": { "zone": { "type": "string", "description": "Code de zone du plan local d'urbanisme, par exemple UA, UB, AU, A ou N." }, "code_insee": { "type": "string", "pattern": "^[0-9][0-9AB][0-9]{3}$", "description": "Code INSEE de la commune, cinq caracteres, par exemple 31395 (Muret)." } }, "additionalProperties": false }arguments 19 linessearch_french_urbanism_regulation reads unknown 10h ago
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.
{ "type": "object", "required": [ "code_insee", "mots" ], "properties": { "mots": { "type": "string", "minLength": 3, "description": "Les mots a chercher, par exemple « hauteur »." }, "code_insee": { "type": "string", "pattern": "^[0-9][0-9AB][0-9]{3}$", "description": "Code INSEE de la commune, cinq caracteres, par exemple 31395 (Muret)." } }, "additionalProperties": false }arguments 20 linesget_french_building_permit_pieces reads unknown 14h ago
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.
{ "type": "object", "required": [ "code_insee" ], "properties": { "code_insee": { "type": "string", "pattern": "^[0-9][0-9AB][0-9]{3}$", "description": "Code INSEE de la commune, cinq caracteres, par exemple 31395 (Muret)." } }, "additionalProperties": false }arguments 14 linesget_french_urbanism_rules_for_street reads unknown 14h ago
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.
{ "type": "object", "required": [ "code_insee", "voie" ], "properties": { "voie": { "type": "string", "minLength": 2, "description": "Nom de la voie en toutes lettres, par exemple « avenue Jacques Douzans »." }, "numero": { "type": "string", "description": "Le numero dans la voie, par exemple « 22 » ou « 12 bis » : rend le terrain de ce numero. Sans lui, la voie au point." }, "code_insee": { "type": "string", "pattern": "^[0-9][0-9AB][0-9]{3}$", "description": "Code INSEE de la commune, cinq caracteres, par exemple 31395 (Muret)." } }, "additionalProperties": false }arguments 24 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idee439ea0ffb1c4be.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/ee439ea0ffb1c4be/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/ee439ea0ffb1c4be?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.