gentry.fr, le logement en France
REMOTE · MCP.GENTRY.FR · SCANNED OCT 1
French housing data for every commune: sale prices, rents, property tax and rent control.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 930 tokens (~186/item across 5 items; 5 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 Management57
- Stability observed for 17 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the gentry.fr, le logement en France MCP server?
gentry.fr, le logement en France is a hosted endpoint at https://mcp.gentry.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.
remote · mcp.gentry.fr
claude mcp add --transport http fr-gentry-logement 'https://mcp.gentry.fr/mcp'
{
"mcpServers": {
"fr-gentry-logement": {
"url": "https://mcp.gentry.fr/mcp"
}
}
} {
"servers": {
"fr-gentry-logement": {
"type": "http",
"url": "https://mcp.gentry.fr/mcp"
}
}
} [mcp_servers.fr-gentry-logement] url = "https://mcp.gentry.fr/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fr-gentry-logement": {
"type": "remote",
"url": "https://mcp.gentry.fr/mcp",
"enabled": true
}
}
} openclaw mcp add fr-gentry-logement --url 'https://mcp.gentry.fr/mcp' --transport streamable-http
mcp_servers:
fr-gentry-logement:
url: "https://mcp.gentry.fr/mcp" {
"McpServers": {
"fr-gentry-logement": {
"Transport": "http",
"Url": "https://mcp.gentry.fr/mcp"
}
}
} assistant mcp add fr-gentry-logement -t streamable-http -u 'https://mcp.gentry.fr/mcp'
{
"mcpServers": {
"fr-gentry-logement": {
"type": "http",
"url": "https://mcp.gentry.fr/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +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.
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 1 Oct 2026 · Probed https://mcp.gentry.fr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.gentry.fr | CN=WR3,O=Google Trust Services,C=US | 5 Sept 2026 | 4 Dec 2026 | RSA 2048 | SHA256-RSA | cc4809aaa6074517129901389adc2f10 |
| SANs: mcp.gentry.fr, mcp.socs.fr, connexion.murmure.tech | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.gentry.fr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | present | 65381 | 13 | Verified |
| gentry.fr. | absent | 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=31556926 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.gentry.fr/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.gentry.fr/mcp | HTTPS enforced | 301 | https://mcp.gentry.fr/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 →
cherche_adresse Trouver une adresse française ~126
Résout une adresse ou un nom de commune en coordonnées et en code INSEE, via la Base Adresse Nationale. À appeler en premier quand la question porte sur un lieu : les autres outils de gentry travaillent sur le code INSEE, et Paris, Lyon et Marseille y sont désignés par leur arrondissement (75118) et non par leur commune (75056).
| Name | Type | Req | Description |
|---|---|---|---|
| limite | integer | – | Nombre de candidats à rendre (5 par défaut) |
| requete | string | yes | Adresse ou commune, en toutes lettres : « 12 rue Ordener Paris », « Nantes » |
No output schema declared.
No examples provided.
cherche_page Chercher dans gentry.fr ~132
Cherche par le sens dans tout gentry.fr : outils, classements, définitions et cartes. Répond à une question posée en langage courant (« passoire thermique », « est-ce que je peux construire sur ce terrain », « quartier où il fait bon vivre ») et rend les pages qui la traitent, avec leur adresse. À utiliser en premier quand on ignore si gentry couvre un sujet, avant de conclure que la donnée n'existe pas.
| Name | Type | Req | Description |
|---|---|---|---|
| limite | integer | – | Nombre de pages à rendre (6 par défaut) |
| question | string | yes | La question, en langage courant |
No output schema declared.
No examples provided.
classement_taxe_fonciere Taxe foncière des communes d'un département ~196
Compare la taxe foncière due dans les communes d'un département, sur des logements types (appartement et maison de surfaces standards). Rend le montant annuel en euros, le taux global voté et le classement des communes les moins et les plus chères. Le calcul applique le schéma de l'annexe III au Code général des impôts. À utiliser pour « où la taxe foncière est-elle la moins chère », ou pour situer une commune face à ses voisines.
| Name | Type | Req | Description |
|---|---|---|---|
| commune | string | yes | Commune, adresse, code INSEE ou numéro de département : « Bordeaux », « 33 », « 33063 » |
| limite | integer | – | Nombre de communes à citer de chaque côté du classement (5 par défaut) |
| scenario | string | – | Logement type à comparer. Sans valeur, le premier scénario publié est retenu, et la liste des scénarios disponibles est rendue. |
No output schema declared.
No examples provided.
encadrement_des_loyers Encadrement des loyers d'une commune ~145
Dit si une commune applique l'encadrement des loyers, et lequel des trois régimes : loyer libre, évolution encadrée (décret zones tendues, le loyer ne peut pas dépasser celui du locataire précédent à la relocation) ou loyers plafonnés (loi ELAN, un plafond en euros par mètre carré). Rend le barème en vigueur quand la commune en publie un. À utiliser pour toute question sur le montant légal d'un loyer, la relocation, ou le préavis réduit.
| Name | Type | Req | Description |
|---|---|---|---|
| commune | string | yes | Nom de commune, adresse ou code INSEE : « Lille », « 75118 » |
No output schema declared.
No examples provided.
fiche_commune Carte d'identité d'une commune ~129
Rend les chiffres publiés d'une commune française : prix d'achat médian au mètre carré pour une maison et pour un appartement, loyer d'annonce estimé, niveau de vie médian, taux de taxe foncière voté, population et communes limitrophes. Sources publiques (DVF, Filosofi, DGFiP, INSEE). À utiliser pour situer une commune, comparer deux communes ou répondre à « combien coûte l'immobilier à … ».
| Name | Type | Req | Description |
|---|---|---|---|
| commune | string | yes | Nom de commune, adresse ou code INSEE : « Rennes », « 35238 » |
No output schema declared.
No examples provided.
What is the gentry.fr, le logement en France MCP server?
gentry.fr, le logement en France is an MCP server listed in the public MCP registry as fr.gentry/logement. French housing data for every commune: sale prices, rents, property tax and rent control. This page covers its hosted endpoint (https://mcp.gentry.fr/mcp).
Is the gentry.fr, le logement en France MCP server safe to use?
gentry.fr, le logement en France scores 81 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 gentry.fr, le logement en France MCP server expose?
gentry.fr, le logement en France exposes 5 tools: cherche_page, cherche_adresse, fiche_commune, classement_taxe_fonciere, encadrement_des_loyers. Their descriptions and schemas cost roughly 728 tokens of context every time the server is loaded.
Does the gentry.fr, le logement en France MCP server require authentication?
No. We connected to gentry.fr, le logement en France without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the gentry.fr, le logement en France MCP server still maintained?
gentry.fr, le logement en France is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.