@pipeworx/france-dvf

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/france-dvf’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 3

France’s official property-transfer price records — “Demandes de valeurs foncieres” (DVF), published by the Direction generale des finances publiques (DGFiP) — every recorded sale (and a handful of other transfer types) with price, commune, parcel, property type, surface and coordinates. Fleet #2935.

DGFiP publishes DVF as a rolling five-year bulk release twice a year (April/October), not as an API, so Pipeworx keeps a copy refreshed on that same twice-yearly cycle. The underlying file carries no personal names — it is address- and parcel-level, not person-level.

Tools

• fr_property_sales(commune?, postcode?, from?, to?, type?, limit?, offset?) — list recorded transactions for a commune (5-digit INSEE code or a name, e.g. "75111" or "Lyon" — a name matches every commune whose name starts with it, so "Lyon" returns sales across all 9 Lyon arrondissements) and/or postcode, with optional date-range and property-type filters. Each result is one disposition (a specific parcel/lot in a transaction).
• fr_property_sale(id) — one transaction (“mutation”) by its id_mutation (from a fr_property_sales result), with every parcel/lot it bundles and the shared transaction price, date and nature.
• fr_property_stats(commune, year) — median and average price per m² for a commune and year, broken out by property type (Maison/Appartement), plus the total transaction count. A commune name matching more than one commune (e.g. "Saint-Martin", or a bare multi-arrondissement city name like "Lyon") returns the list of candidates instead of a number — pass one INSEE code to disambiguate.

Every response carries data_as_of (the release date of the loaded copy), source, licence and coverage_note.

Why price-per-m² is computed from single-lot sales only

valeur_fonciere is the total price of the whole transaction, not of one parcel — a single sale can bundle several lots (e.g. a house plus a garage, or several apartments in one deed). Dividing that total by one lot’s surface would silently misstate the price per m². fr_property_stats therefore computes price/m² only from transactions with exactly one recorded lot, of a residential type (Maison/Appartement) with a positive built surface. fr_property_sales and fr_property_sale are not filtered this way — they return every recorded disposition, and each one carries single_lot_sale so a caller can apply the same filter itself.

Commune matching

Pass the 5-digit INSEE commune code for an exact match. A name is matched case-insensitively as a prefix ("Lyon" matches "Lyon 1er Arrondissement" through "Lyon 9e Arrondissement", and also "Lyons-la-Foret", a different commune that happens to share the prefix) — it is not accent-folding, so an accented name should be typed with its accents, or looked up by INSEE code instead.

Auth

Keyless. The tools answer only through the Pipeworx gateway, which holds the copy of the data; a standalone npm install has no data to read, and every tool throws a clear “not bound in this runtime” error there instead of returning an empty list.

Data sources

• DGFiP, Demandes de valeurs foncieres (DVF) — the rolling five-year bulk release, refreshed twice a year (April/October). Covers metropolitan France and the overseas departments, excluding Alsace (departments 67, 68), Moselle (57) and Mayotte (976), which keep a separate land registry (Livre foncier) this release does not cover.

Licence: Licence Ouverte / Open Licence v2.0 (Etalab) — free reuse including commercial use, on two conditions this pack is built to honour:

1. The data must not be used to indirectly re-identify the individuals behind a transaction.
2. The data must not be made indexable by external search engines.

This pack exposes records only through MCP tool calls answered by the gateway — there is no crawlable listing page for a search engine to index — and the underlying file carries no names, so a caller sees exactly the address- and parcel-level detail the publisher already releases, no more.

Tools

• fr_property_sales — List DVF property-transfer records for a commune or postcode, with date/type filters.
• fr_property_sale — One DVF transaction by id_mutation, with every lot/parcel it covers.
• fr_property_stats — Median/average DVF price per m2 for a commune and year, by property type.