France Dvf
NPM · @PIPEWORX/MCP-FRANCE-DVF · 2 COMPONENTS
france-dvf — France's official property-transfer price records ('Demandes de valeurs foncieres'…
Available components
Last scanned (10 hours ago)
Scores higher than 72% of npm servers
Category Data and Analytics
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-france-dvf). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 776 tokens (~258/item across 3 items; 3 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 Management20
- Stability observed for 6 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.10 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 79
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-france-dvf@0.2.1
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 | pipeworx-io/mcp-france-dvf |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-france-dvf/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637319030 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:fe63482756eab8f08748965b760624544ecabea17ba314739908f51a51844e0ca75f4bbc0d9a593e582294e7a6249509aa6790e4d84767a51ac23320d |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
fr_property_sale ~111
One 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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id_mutation from a fr_property_sales result, e.g. "2025-123456". |
No output schema declared.
No examples provided.
fr_property_sales ~362
List 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).
| Name | Type | Req | Description |
|---|---|---|---|
| commune | string | – | 5-digit INSEE commune code (e.g. "75111") or a commune name (case-insensitive prefix match, e.g. "Lyon"). |
| from | string | – | Earliest sale date, YYYY-MM-DD (inclusive). |
| limit | number | – | Max results, 1-200. Default 25. |
| offset | number | – | Pagination offset. Default 0. |
| postcode | string | – | 5-digit French postal code, e.g. "75011". |
| to | string | – | Latest sale date, YYYY-MM-DD (inclusive). |
| type | string | – | Property type: "Maison" (house), "Appartement" (apartment), "Dépendance" (outbuilding), or "Local industriel. commercial ou assimilé" (commercial/industrial). |
No output schema declared.
No examples provided.
fr_property_stats ~248
Median 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".
| Name | Type | Req | Description |
|---|---|---|---|
| commune | string | yes | 5-digit INSEE commune code (e.g. "69381" for Lyon 1er) or a commune name (e.g. "Lyon 1er Arrondissement", "Nantes"). A bare multi-arrondissement city name like "Lyon" or "Paris" returns all its arron… |
| year | number | yes | Calendar year, e.g. 2024. |
No output schema declared.
No examples provided.
How do I install the France Dvf MCP server?
France Dvf runs locally as an npm package, launched with npx -y @pipeworx/mcp-france-dvf. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-france-dvf
claude mcp add pipeworx-io-france-dvf -- npx -y @pipeworx/mcp-france-dvf
What is the France Dvf MCP server?
France Dvf is an MCP server listed in the public MCP registry as io.github.pipeworx-io/france-dvf. france-dvf, France's official property-transfer price records ('Demandes de valeurs foncieres'… This page covers its npm package (@pipeworx/mcp-france-dvf).
Is the France Dvf MCP server safe to use?
France Dvf scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 France Dvf MCP server expose?
France Dvf exposes 3 tools: fr_property_sales, fr_property_sale, fr_property_stats. Their descriptions and schemas cost roughly 721 tokens of context every time the server is loaded.
Is the France Dvf MCP server still maintained?
France Dvf is still listed as active in the MCP registry. We last reached this channel on 5 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 France Dvf MCP server under?
France Dvf declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.