Immo API — DVF immobilier France vs France Dvf
A side-by-side look at the Immo API — DVF immobilier France and France Dvf MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
I
Immo API — DVF immobilier FranceReal Estate · Remote HTTP/SSEDonnées immobilières DVF France : transactions, comparables GPS et statistiques de marché.39FairAuth: oauth 2.0Verdict: choose Immo API — DVF immobilier France for real estate work over a hosted endpoint; choose France Dvf for real estate as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
IChoose Immo API — DVF immobilier France when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Choose France Dvf when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
fr_property_sales, fr_property_sale, fr_property_stats.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | I Immo API — DVF immobilier France | |
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 39/100 · Fair | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Immo API — DVF immobilier France | View France Dvf |
Tools & capabilities
Immo API — DVF immobilier France tools
No tool names declared yet. Check the project README from the listing page.
France Dvf tools 3
fr_property_salesList recorded French property-transfer prices (DVF -- Demandes de valeurs foncieres, published by DGFiP) for a commune or postcode, optionally filtered by date range and property type. Each result is one recorded disposition (a specific parcel/lot in a transaction) with price, address-level commune, parcel id, property type, built surface, land surface, room count and coordinates. Pass commune as either a 5-digit INSEE code (e.g. "75111" for Paris 11e) or a commune name (e.g. "Lyon" matches all 9 Lyon arrondissements; "Paris 11e Arrondissement"). Use for "property sales in Paris 11e in 2025" or "recent house sales in Annecy". Covers a rolling five years; excludes Alsace, Moselle and Mayotte (see data_as_of/coverage_note in the response).fr_property_saleOne French property transaction ("mutation") by its DVF id_mutation, as returned by fr_property_sales. Returns every lot/parcel recorded under that transaction (a sale can bundle several parcels, e.g. a house plus a garage) with the shared transaction price, date and nature. Use after fr_property_sales to see the full set of parcels in a specific sale.fr_property_statsMedian and average price per square meter for a French commune and year, broken out by property type (Maison/Appartement), plus the total number of transactions. Computed only from single-lot sales (one parcel per transaction) with a positive built surface, because the DVF price field is the total for the whole transaction and would otherwise be double-counted or misattributed across bundled lots. Pass commune as a 5-digit INSEE code or a commune name; a name matching more than one commune (e.g. "Saint-Martin") returns the list of candidates instead of a number. Use for "median price per m2 in Lyon in 2024" or "how much do apartments go for in Nantes".
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Immo API — DVF immobilier France
{
"mcpServers": {
"immo-api-dvf-immobilier-france": {
"command": "npx",
"args": [
"-y",
"immo-api-dvf-immobilier-france"
]
}
}
}
France Dvf
{
"mcpServers": {
"france-dvf": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-france-dvf"
]
}
}
}
Frequently asked questions
Immo API — DVF immobilier France is categorized under Real Estate and uses a remote HTTP/SSE transport. France Dvf belongs to Real Estate and uses a local stdio subprocess. Pick Immo API — DVF immobilier France for real estate work and France Dvf for real estate.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Immo API — DVF immobilier France has no declared pricing — check the project's own site. Auth: oauth 2.0. France Dvf is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add immo-api-dvf-immobilier-france and france-dvf as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Immo API — DVF immobilier France has a quality signal of 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. France Dvf has 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars.