io.github.OlivierLAVAUD/mcp-immo
NPM · MCP-IMMO-OLV
French real-estate intelligence from official open data: DVF, valuations, rents, tax, DPE, risks.
Available components
Last scanned (22 hours ago)
Scores higher than 82% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to OlivierLAVAUD/mcp-immo-olv). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 40 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2996 tokens (~142/item across 21 items; 21 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 77% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 13 Nov 26 0
- Stability: 0.97 → pass security
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 −2
- Stability: pass → 0.80 functional
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
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 21 Nov 2026 · Analysed npm/mcp-immo-olv@1.12.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | OlivierLAVAUD/mcp-immo-olv |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/OlivierLAVAUD/mcp-immo-olv/.github/workflows/publish.yml@refs/tags/v1.12.0 |
| Rekor log index | 3214875400 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ee65ade80354e725c0eae567b4615e893f0ac7d5830d9856a3bc7f17f795ab3d58380ea2677fbbd2224940c2ad4fb3b9c65f46a8e155e1c2d9c883c36 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
acquisition_costs Acquisition costs and yield simulation ~292
Simulate the costs of buying a French dwelling and its rental yield: droits de mutation (official 2026 scale, about 6.42 % for communes over 5 000 inhabitants), notary fees and publication, commune-average taxe foncière (REI), modelled asking rent (Carte des loyers), and gross / net yields. The price defaults to a comparables-based estimate (estimate_property) but can be replaced by an agreed or asking price. All figures are indicative — the taxe foncière is a commune average, never an individual tax notice, and rents are modelled asking rents, not regulated reference rents. Source: DVF, Carte des loyers, REI.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address in France |
| notary_model | string | – | Notary fee assumption: standard (typical card), hands_off (about +250 €), aggressive (bare minimum, 750 €) |
| price_eur | number | – | Known price in € (negotiated or asking). Absent: use the comparables-based estimate. |
| price_from | string | – | What price_eur means when provided; 'estimate' (default) lets the tool value the dwelling itself |
| rooms | integer | – | Main rooms (pièces) |
| surface_m2 | number | yes | Living surface in m² |
| type_local | string | yes | Dwelling type |
| Name | Type | Req | Description |
|---|---|---|---|
| acquisition_costs | object | yes | – |
| loyer | object | yes | – |
| price_eur | number | yes | – |
| price_from | string | yes | – |
| returns | object | yes | – |
| taxe_foncière_annuale | number | yes | Commune-average annual taxe foncière from the REI dataset — not an individual tax notice |
No examples provided.
backtest_estimator Walk-forward backtest of the valuation model ~185
Replay the comparable-sales estimator on the commune's own notarized sales: every historical sale is valued using only the sales recorded before it (no look-ahead, own deed excluded), then compared with the price actually paid. Returns MAPE, median and 90th-percentile absolute error, signed bias, P25–P75 range coverage and the same metrics by surface band and by year. Use it to say how reliable estimate_property is in this specific market.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Precise address (street or house number) in France |
| from_year | integer | – | First sale year to evaluate (default: every year available) |
| max_points | integer | – | Max sales evaluated, most recent first (default 250) |
| to_year | integer | – | Last sale year to evaluate |
| type_local | string | yes | Property type to backtest |
| Name | Type | Req | Description |
|---|---|---|---|
| by_surface_band | object | yes | – |
| by_year | object | yes | – |
| candidates | number | yes | – |
| caveats | array | yes | – |
| evaluated | number | yes | – |
| method | string | yes | – |
| overall | object | yes | – |
| query | object | yes | – |
| skipped_not_estimable | number | yes | – |
| source | string | yes | – |
| type | string | yes | – |
| worst_cases | array | yes | – |
| year_range | – | yes | – |
No examples provided.
cadastral_parcel Cadastral parcel at an address ~116
Official cadastral parcel(s) containing an address: unique cadastral id (idu) quoted on deeds, section, number and the official contenance in m². The contenance is the taxed area of the whole parcel, land included — not the dwelling's habitable surface — and the cadastre never records ownership. Source: IGN / DGFiP via API Carto.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Address in France (alternative to lat/lon) |
| lat | number | – | – |
| lon | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| caveats | array | yes | – |
| note | string | yes | – |
| parcels | array | yes | – |
| parcels_found | number | yes | – |
| point | object | yes | – |
| resolved_address | string|null | yes | – |
| source | string | yes | – |
| source_url | string | yes | – |
No examples provided.
commune_info Commune information ~61
Population, postcodes, département, région, surface and center coordinates of a French commune, by name or INSEE code.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Commune name or 5-char INSEE code (e.g. 'Lyon' or '69123') |
| Name | Type | Req | Description |
|---|---|---|---|
| communes | array | yes | – |
| note | string | – | – |
| source | string | yes | – |
No examples provided.
compare_properties Compare 2–5 addresses side by side ~146
Side-by-side comparison of 2 to 5 French addresses in one call: current market level (€/m²), comparables valuation with confidence, asking rents, DPE with legal rental status (décret n° 2024-501) and estimated energy cost, plus row-index rankings (cheapest market, best yield). Each section degrades independently, like property_report. Source: DVF, Carte des loyers, ADEME — official open data.
| Name | Type | Req | Description |
|---|---|---|---|
| radius_m | number | – | Search radius in meters around the address (default 500; ignored for city-wide queries) |
| targets | array | yes | 2 to 5 addresses to compare, in your order |
| Name | Type | Req | Description |
|---|---|---|---|
| caveats | array | yes | – |
| note | string | yes | – |
| query | object | yes | – |
| rankings | object | yes | – |
| rows | array | yes | – |
| source | string | yes | – |
No examples provided.
dpe_lookup Energy performance diagnostics (DPE) ~162
Find official energy performance certificates (DPE: energy label A-G, GES label, surface, construction year) filed for a French address, with the legal rental status at each label (décret n° 2024-501) and an estimated annual energy cost. Source: ADEME open data.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address in France |
| dataset | string | – | DPE register: existing dwellings (dpe03existant), new dwellings (dpe02neuf), or both (default all) |
| energy_price_eur_kwh | number | – | Tariff assumption for the energy-cost estimate in €/kWh (default 0.2562) |
| limit | integer | – | Max diagnostics returned (default 10) |
| Name | Type | Req | Description |
|---|---|---|---|
| by_dataset | array | yes | – |
| diagnostics | array | yes | – |
| note | string | yes | – |
| query | object | yes | – |
| source | string | yes | – |
| total_found | number | yes | – |
No examples provided.
estimate_property Estimate a property's value (comparables) ~119
Transparent comparables-based valuation of a flat or house at a precise French address: weighted median of nearby single-dwelling notarized sales, adjusted to current market level, with every comp and weight returned for audit. Also returns the official rent indicator and gross rental yield.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Precise address (street + number preferred) |
| rooms | integer | – | Main rooms (pièces principales) — refines the rent indicator |
| surface_m2 | number | yes | Living surface in m² |
| type_local | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| caveats | array | yes | – |
| estimate | object | yes | – |
| query | object | yes | – |
| rental | – | yes | – |
| source | string | yes | – |
No examples provided.
geocode_address Geocode a French address ~80
Resolve a French address, street, or city to normalized candidates with coordinates, INSEE city code and BAN id (Base Adresse Nationale). Use this first if an address is ambiguous.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max candidates (default 5) |
| query | string | yes | Free-form address, e.g. '10 rue de la Paix Paris' |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
| source | string | yes | – |
No examples provided.
iris_lookup IRIS neighbourhood of an address ~94
Identify the IRIS — INSEE's infra-communal statistical unit, about 2 000 inhabitants — containing an address: 9-character IRIS code, name, type and commune. Join that code to INSEE's IRIS tables for population and Filosofi income. Boundaries from IGN ADMINEXPRESS; this layer carries identity only, no socio-demographic figures.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address in France |
| Name | Type | Req | Description |
|---|---|---|---|
| caveats | array | yes | – |
| iris | – | yes | – |
| note | string | yes | – |
| point | object | yes | – |
| resolved_address | string | yes | – |
| source | string | yes | – |
| source_url | string | yes | – |
No examples provided.
natural_risks Natural & technological risks (Géorisques) ~79
Official risk report for a French address or point: flood, clay shrink-swell, radon, earthquake, industrial sites... Source: Géorisques (Ministère de la Transition écologique).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Address in France (alternative to lat/lon) |
| lat | number | – | – |
| lon | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string|null | yes | – |
| available | boolean | yes | false means Géorisques could not be reached: the risk status is UNKNOWN, not risk-free |
| commune | string|null | yes | – |
| naturalRisks | array | yes | – |
| note | string | yes | – |
| officialReportUrl | string|null | yes | – |
| resolved_address | string|null | yes | – |
| source | string | yes | – |
| technologicalRisks | array | yes | – |
| unavailable | object | – | – |
No examples provided.
nearby_amenities What is around an address (POIs) ~234
Nearby points of interest around a French address or point, from OpenStreetMap: public transport (train, metro, tram, bus stop), schools and higher education, everyday shops, health (pharmacy, doctor, hospital) and green/sport space — each with how many are within the radius and the closest ones, in metres as the crow flies. The transports category also breaks its count down by mode (train, metro, tram, bus), so a tram stop is answered in its own right rather than drowned in a single transport figure. Answers the neighbourhood question no official French dataset covers directly. When Overpass is unreachable, every count is UNKNOWN (null) rather than zero. Source: OpenStreetMap contributors (ODbL), via the Overpass API.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Address in France (alternative to lat/lon) |
| lat | number | – | – |
| limit | integer | – | How many closest POIs to list per category (default 3) |
| lon | number | – | – |
| radius_m | number | – | Search radius in meters around the point (default 1000) |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | yes | false: Overpass unreachable, so every count is UNKNOWN — not zero |
| categories | array | yes | – |
| caveats | array | yes | – |
| note | string | yes | – |
| point | object | yes | – |
| radius_m | number | yes | – |
| resolved_address | string|null | yes | – |
| source | string | yes | – |
| source_url | string | yes | – |
| unavailable | object | – | – |
No examples provided.
price_per_m2 Price per m² statistics (DVF) ~123
Compute price-per-m² statistics (median, mean, quartiles, per-year evolution) from actual notarized sales around a French address or across a commune. Data 2021-2025.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address, street or city in France |
| radius_m | number | – | Search radius in meters around the address (default 500; ignored for city-wide queries) |
| type_local | string | – | Filter by dwelling type |
| years | array | – | DVF years to include (2021-2025). Defaults to all. |
| Name | Type | Req | Description |
|---|---|---|---|
| all_period | object | yes | – |
| by_year | object | yes | – |
| last_12_months | – | yes | – |
| note | string | yes | – |
| query | object | yes | – |
| source | string | yes | – |
No examples provided.
property_report Full property due-diligence report ~241
One call, full dossier for a French address: price-per-m² market stats, recent notarized sales, energy diagnostics (DPE), natural & technological risks, commune profile, official rent indicators and an aggregate taxe foncière proxy — plus a comparables-based valuation, gross yield and yield after average property tax when type_local and surface_m2 are provided. Ideal first call when a user asks about a specific property. Pass `addresses` (2 to 5) instead of `address` to dossier several neighbourhoods in one call; each report is isolated, so one bad address returns its own error without sinking the batch.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Address in France (mutually exclusive with `addresses`) |
| addresses | array | – | 2 to 5 addresses to dossier in one call, for comparing neighbourhoods (mutually exclusive with `address`) |
| format | string | – | Answer shape: 'json' (default, structured dossier) or 'markdown' (same dossier rendered as shareable Markdown) |
| rooms | integer | – | – |
| surface_m2 | number | – | – |
| type_local | string | – | Filter by dwelling type |
| Name | Type | Req | Description |
|---|---|---|---|
| cadastre | – | – | – |
| caveats | array | – | – |
| commune | – | – | – |
| content | string | – | Rendered Markdown dossier, present when format is 'markdown' |
| energy_diagnostics | – | – | – |
| format | string | – | – |
| generated_from | string | – | – |
| iris | – | – | – |
| market | – | – | – |
| note | string | – | – |
| property_tax | – | – | – |
| query | object | – | Present in the batch form: the shared profile applied to every address |
| recent_sales_nearby | – | – | – |
| rent | – | – | – |
| rent_control | – | – | – |
| reports | array | – | One entry per requested address, in order |
| resolved_address | string | – | – |
| risks | – | – | – |
| urbanism | – | – | – |
| valuation | – | – | – |
No examples provided.
property_sales Real property sales around an address (DVF) ~168
List actual notarized property sales (price, date, surface, rooms) recorded by the French tax administration (DVF) around an address, or for a whole commune if only a city is given. Data 2021-2025, no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address, street or city in France |
| limit | integer | – | Max sales returned (default 30) |
| max_surface_m2 | number | – | – |
| min_surface_m2 | number | – | – |
| radius_m | number | – | Search radius in meters around the address (default 300; ignored for city-wide queries) |
| type_local | string | – | Filter by dwelling type |
| years | array | – | DVF years to include (2021-2025). Defaults to all. |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | – |
| query | object | yes | – |
| sales | array | yes | – |
| source | string | yes | – |
| total_matching_sales | number | yes | – |
No examples provided.
property_tax_estimate Average property tax by commune (REI) ~104
Returns the annual average charge per taxable REI article for taxe foncière on built properties, including published communal, intercommunal, syndicate, GEMAPI and TEOM components. It is an aggregate proxy, not an individual property's tax bill. Source: DGFiP REI via OFGL.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | Address, commune name or INSEE code |
| year | integer | – | REI tax year; defaults to the latest available year |
| Name | Type | Req | Description |
|---|---|---|---|
| caveats | array | yes | – |
| components | array | yes | – |
| coverage | string | yes | – |
| insee_code | string | yes | – |
| query | object | yes | – |
| source | string | yes | – |
| source_url | string | yes | – |
| typical_annual_charge_eur | number | yes | Average charge per taxable article in the commune, not an individual tax bill |
| year | number | yes | – |
No examples provided.
rent_control Rent-control reference rents ~164
Loyer de référence, loyer de référence majoré (the legal ceiling) and minoré, in €/m²/month, for a rent-controlled area — by number of rooms, construction period and furnished status. Covers only the areas whose authority publishes an open grid (Paris, Métropole de Lyon, Montpellier); the response states explicitly when an address is not covered instead of guessing. Sources: Ville de Paris, Métropole de Lyon, Montpellier Méditerranée Métropole.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address in France |
| furnished | boolean | – | Furnished (true) or unfurnished (false) |
| period | string | – | Construction period label, e.g. '1946-1970' |
| rooms | integer | – | Number of rooms (pièces) |
| Name | Type | Req | Description |
|---|---|---|---|
| area_label | string|null | – | – |
| caveats | array | – | – |
| city | string | – | – |
| covered | boolean | yes | – |
| covered_cities | array | – | – |
| furnished | boolean|null | – | – |
| matched | string | – | – |
| note | string | yes | – |
| period | string|null | – | – |
| query | object | yes | – |
| rooms | number|null | – | – |
| source | string | yes | – |
| source_url | string | – | – |
| values | object | – | – |
| year | string|null | – | – |
No examples provided.
rent_estimate Rent indicators (Carte des loyers) ~94
Official modelled asking rents (€/m²/month, charges included) for any French commune: apartments overall, 1-2 rooms, 3+ rooms, and houses. Source: Carte des loyers, Ministère du Logement / ANIL.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | Address, commune name or INSEE code |
| surface_m2 | number | – | If given, also returns the estimated monthly rent |
| Name | Type | Req | Description |
|---|---|---|---|
| indicators | object | yes | – |
| insee_code | string | yes | – |
| location | string | yes | – |
| note | string | yes | – |
| source | string | yes | – |
| year | number | yes | – |
No examples provided.
reverse_geocode Reverse geocode ~32
Find the nearest French address for GPS coordinates.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lon | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
| source | string | yes | – |
No examples provided.
risk_summary Risk summary: one line per risk ~128
Consumer-grade risk digest for a French address or point: one plain-language sentence each for flood, clay shrink-swell, radon, industrial sites (ICPE) and the DPE rental-ban schedule, plus a one-line headline and any other present risk named. Reuses Géorisques and ADEME. When Géorisques is unreachable every risk line reads UNKNOWN — never a clean bill of health. Source: Géorisques, ADEME.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Address in France (alternative to lat/lon) |
| lat | number | – | – |
| lon | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | yes | false: Géorisques unreachable, so every risk status is UNKNOWN, not risk-free |
| caveats | array | yes | – |
| dpe_error | string|null | – | – |
| headline | string | yes | One-sentence synthesis; states UNKNOWN explicitly when the source is down |
| items | array | yes | – |
| note | string | yes | – |
| other_present_risks | array | yes | Present risks outside the summarised categories, named so nothing is hidden |
| point | object | yes | – |
| resolved_address | string|null | yes | – |
| signals_count | number | yes | Items reading `present`: a risk signalled, or a rental ban that applies |
| source | string | yes | – |
| source_url | string | yes | – |
| unavailable | object | – | – |
No examples provided.
search_by_budget Find what a budget can buy in a zone ~243
The inverse of the estimator: 'with 300 k€, where can I buy?' For each commune of a département it computes the median €/m² from actual notarized sales (DVF, last 4 published years), divides the budget by it to get the surface the budget buys, and layers the modelled asking rent for the gross yield. Returns the qualifying communes ranked by surface, yield and price, plus the communes skipped for lack of data. The budget is the purchase price only — acquisition fees come on top (see acquisition_costs). Source: DVF, Carte des loyers, geo.api.gouv.fr.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_eur | number | yes | Purchase budget in €, fees excluded |
| max_communes | integer | – | Communes to scan, most populous first (default 15, max 40) |
| min_surface_m2 | number | – | Minimum surface the budget must buy (default 30) |
| type_local | string | – | Dwelling type; absent: all single-dwelling sales |
| zone | string | yes | Commune name, INSEE code, address, or département code (e.g. '69', '13') |
| Name | Type | Req | Description |
|---|---|---|---|
| budget_eur | number | yes | – |
| caveats | array | yes | – |
| communes | array | yes | – |
| errors | array | yes | – |
| not_enough_data | array | yes | – |
| note | string | yes | – |
| rankings | object | yes | – |
| type_local | string | yes | – |
| years_used | array | yes | – |
| zone | object | yes | – |
No examples provided.
urbanism_zoning Urbanism rules at an address (PLU) ~131
Urbanism zoning and prescriptions applicable to an address, from the Géoportail de l'urbanisme: zoning area label and type (U urban, AU to be urbanised, A agricultural, N natural), the regulation document reference, and the surface / linear / point prescriptions (emplacements réservés, protected areas, alignments…). It states which rules apply, never whether a project is permitted. Source: GPU, DGALN / IGN.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Address in France (alternative to lat/lon) |
| lat | number | – | – |
| lon | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| caveats | array | yes | – |
| coverage_note | string | – | – |
| note | string | yes | – |
| point | object | yes | – |
| prescriptions | array | yes | – |
| resolved_address | string|null | yes | – |
| source | string | yes | – |
| source_url | string | yes | – |
| zoning_areas | array | yes | – |
No examples provided.
How do I install the io.github.OlivierLAVAUD/mcp-immo server?
io.github.OlivierLAVAUD/mcp-immo runs locally as an npm package, launched with npx -y mcp-immo-olv. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-immo-olv
claude mcp add olivierlavaud-mcp-immo -- npx -y mcp-immo-olv
What is the io.github.OlivierLAVAUD/mcp-immo server?
io.github.OlivierLAVAUD/mcp-immo is listed in the public MCP registry as io.github.OlivierLAVAUD/mcp-immo. French real-estate intelligence from official open data: DVF, valuations, rents, tax, DPE, risks. This page covers its npm package (mcp-immo-olv).
Is the io.github.OlivierLAVAUD/mcp-immo server safe to use?
io.github.OlivierLAVAUD/mcp-immo scores 88 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.OlivierLAVAUD/mcp-immo server expose?
io.github.OlivierLAVAUD/mcp-immo exposes 21 tools: geocode_address, property_sales, price_per_m2, estimate_property, rent_estimate, and 16 more. Their descriptions and schemas cost roughly 2,996 tokens of context every time the server is loaded.
Is the io.github.OlivierLAVAUD/mcp-immo server still maintained?
io.github.OlivierLAVAUD/mcp-immo is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.OlivierLAVAUD/mcp-immo server under?
io.github.OlivierLAVAUD/mcp-immo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.OlivierLAVAUD/mcp-immo server?
VerifyMCP ran 16 checks on io.github.OlivierLAVAUD/mcp-immo, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.