CaLesVaut
REMOTE · CALESVAUT.FR
Is this listing too expensive? French property sales (DVF), crime, rents, risks, schools
Available components
Last scanned (5 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Maps and Location
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3112 tokens (~311/item across 10 items; 10 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 Management10
- Stability observed for 3 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 18 Oct 26 +1
- Tool “commune_profile” rewrote its description, which is the text the model reads security
- 17 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “appraise_listing” rewrote its description, which is the text the model reads security
- Tool “commune_profile” rewrote its description, which is the text the model reads security
- Schema quality: 268 → 305 ▼ functional
- “find_place” reworded the description of “query” cosmetic
- Tool “commune_profile” changed its title: Rents, energy ratings and natural risks of a French commune → Rents, energy ratings, natural risks, local taxes and internet of a French commune cosmetic
- 16 Oct 26 +1
- Tool “appraise_listing” rewrote its description, which is the text the model reads security
- Tool “commune_profile” rewrote its description, which is the text the model reads security
- Tool “crime_stats” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “amenities_nearby” reworded the description of “place” cosmetic
- “appraise_listing” reworded the description of “place” cosmetic
- “commune_profile” reworded the description of “place” cosmetic
- “crime_stats” reworded the description of “place” cosmetic
- “property_prices” reworded the description of “place” cosmetic
- “recent_sales” reworded the description of “place” cosmetic
- “sales_at_address” reworded the description of “address” cosmetic
- “sea_views” reworded the description of “place” cosmetic
- “street_prices” reworded the description of “place” cosmetic
- Tool “commune_profile” changed its title: Rents, energy ratings and natural risks of a French commune or a US county → Rents, energy ratings and natural risks of a French commune cosmetic
- Tool “crime_stats” changed its title: Recorded crime of a French commune or a US county → Recorded crime of a French commune cosmetic
- 15 Oct 26 66
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 18 Oct 2026 · Probed https://calesvaut.fr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=calesvaut.fr | CN=YE2,O=Let's Encrypt,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 56e63ac09dc531fc31c7a51c8e8ad54a584 |
| SANs: *.calesvaut.fr, calesvaut.fr | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of calesvaut.fr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | present | 65381 | 13 | Verified |
| calesvaut.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://calesvaut.fr/mcp | Verified | 200 | |
| http (plaintext) | http://calesvaut.fr/mcp | HTTPS enforced | 301 | https://calesvaut.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 →
amenities_nearby Amenities and nuisances nearby ~192
Schools (maternelle, primaire, collège/lycée), bakeries, night clubs, noisy bars and every bar or café within a radius (France): count per kind and the nearest ones.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address with its postcode or city (e.g. "17 rue Gambey, 75011 Paris"), located where its sales were recorded (else its street's). Ignored when lat and lng are given. |
| lat | number | – | Latitude (WGS84). |
| lng | number | – | Longitude (WGS84). |
| place | string | – | City, city start or postcode (e.g. "Carnac", "Paris 11e", "75011"); with address, the place it is in. Ignored when lat and lng are given. |
| radius_m | integer | – | Radius in metres (default 500, at most 3000). |
No output schema declared.
No examples provided.
appraise_listing Appraise a listing ~382
Compares a French listing's asking price with recent recorded sales (DVF) of the same type and a similar size around it (the smallest radius with enough of them): estimate with its interquartile range, gap and verdict, closest comparables (sales over 2.5 times off the median price per m² are left out as no market price), a headline such as "12 % au-dessus du marché", local price trend, the commune's main crime rates against France, its rent for the type (monthly rent for the floor area, gross yield at the asking price), its share of passoires thermiques (DPE F or G) for the type, its natural risks, its local tax rates (taxe foncière, waste tax, taxe d'habitation on second homes), its home internet (fibre and wired speeds), each mobile operator's 4G coverage level at the address (mobile_4g) and their antennas, amenities within 500 m, and the address's sea view when it has one.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address with its postcode or city (e.g. "17 rue Gambey, 75011 Paris"), located where its sales were recorded (else its street's). Ignored when lat and lng are given. |
| lat | number | – | Latitude (WGS84). |
| lng | number | – | Longitude (WGS84). |
| place | string | – | City, city start or postcode (e.g. "Carnac", "Paris 11e", "75011"); with address, the place it is in. Ignored when lat and lng are given. |
| price | number | yes | Asking price. |
| surface | number | – | Floor area in m². |
| type | string | – | "Appartement" or "Maison" (others compare with every sale). |
No output schema declared.
No examples provided.
commune_profile Rents, energy ratings, natural risks, local taxes and internet of a French commune ~602
For a French commune (by name, INSEE code or position) or département: asking rents per m² (charges included) for flats, small and large flats and houses, with their range (ANIL/DHUP Carte des loyers); the energy ratings (DPE A–G) of its dwellings diagnosed since July 2021 and the share of passoires thermiques (F or G, which may no longer be let: G since 2025, F from 2028), per flats and houses (ADEME); its natural risks: the risks listed by the state (DDRM), natural disaster (CatNat) decrees since 1982, prevention plans, radon potential (Géorisques); its local tax rates (DGFiP, in %): taxe foncière on buildings and on land, the household waste tax (TEOM; null where a fee pays for it), taxe d'habitation (on second homes and vacant dwellings only since 2023) with the commune's surcharge on second homes, the latest year's and the first's, the taxe foncière year by year, and for a commune how each rate splits between the commune, its syndicates, its intercommunality (named), special taxes and GEMAPI; its median price per m² of recorded sales (DVF) for flats, houses and both over the latest two years against the two before, and year by year; its home internet (ARCEP Ma connexion internet): the share of premises fibre, cable, copper DSL (copper_closed: no new subscribers), fixed 4G, radio and satellite reach, the share getting 8 and 30 Mbit/s and 1 Gbit/s by wire, and its premises by best technology; each mobile operator's 4G coverage of its homes (Orange, SFR, Bouygues Telecom, Free Mobile: the share of homes at each level of ARCEP's simulated maps, very good meaning indoors; metropolitan France), and their antennas in the commune (sites with 4G, 5G, 5G at 3.5 GHz). Each compared with its département and France.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address with its postcode or city (e.g. "17 rue Gambey, 75011 Paris"), located where its sales were recorded (else its street's). Ignored when lat and lng are given. |
| commune | string | – | Commune name or INSEE code (e.g. "Carnac", "56034"), or a département code ("56"). |
| lat | number | – | Latitude (WGS84). |
| lng | number | – | Longitude (WGS84). |
| place | string | – | City, city start or postcode (e.g. "Carnac", "Paris 11e", "75011"); with address, the place it is in. Ignored when lat and lng are given. |
No output schema declared.
No examples provided.
crime_stats Recorded crime of a French commune ~229
Offences recorded by police and gendarmerie (SSMSI, latest year) for a French commune — by name, INSEE code or position — per indicator, as rates per 1,000 inhabitants (per 1,000 dwellings for burglaries), next to its département, région and France, with the yearly trend.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address with its postcode or city (e.g. "17 rue Gambey, 75011 Paris"), located where its sales were recorded (else its street's). Ignored when lat and lng are given. |
| commune | string | – | Commune name or INSEE code (e.g. "Carnac", "56034"), or a département code ("56"). |
| lat | number | – | Latitude (WGS84). |
| lng | number | – | Longitude (WGS84). |
| place | string | – | City, city start or postcode (e.g. "Carnac", "Paris 11e", "75011"); with address, the place it is in. Ignored when lat and lng are given. |
No output schema declared.
No examples provided.
find_place Find a place ~77
Resolves a city name or postcode: its centre, extent and number of recorded sales, and the French communes of that name (INSEE codes) for crime_stats.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | City, its start, a word of its name ("Hardelot" for Neufchâtel-Hardelot) or postcode. |
No output schema declared.
No examples provided.
property_prices Property prices around a place ~232
Median sale price and price per m² of recorded sales within a radius, overall, per property type and per year, over the last years of data.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address with its postcode or city (e.g. "17 rue Gambey, 75011 Paris"), located where its sales were recorded (else its street's). Ignored when lat and lng are given. |
| lat | number | – | Latitude (WGS84). |
| lng | number | – | Longitude (WGS84). |
| place | string | – | City, city start or postcode (e.g. "Carnac", "Paris 11e", "75011"); with address, the place it is in. Ignored when lat and lng are given. |
| radius_m | integer | – | Radius in metres (default 500, at most 3000). |
| type | string | – | Property type as the source names it, e.g. "Appartement" or "Maison" in France. |
| years | integer | – | Years of sales counted back from the latest (default 5, at most 12). |
No output schema declared.
No examples provided.
recent_sales Recent sales around a place ~247
The latest recorded sales within a radius (date, price, floor area, price per m², rooms, type, address, distance).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address with its postcode or city (e.g. "17 rue Gambey, 75011 Paris"), located where its sales were recorded (else its street's). Ignored when lat and lng are given. |
| lat | number | – | Latitude (WGS84). |
| limit | integer | – | Sales returned (default 20, at most 100). |
| lng | number | – | Longitude (WGS84). |
| max_price | integer | – | Maximum price. |
| min_surface | integer | – | Minimum floor area in m². |
| place | string | – | City, city start or postcode (e.g. "Carnac", "Paris 11e", "75011"); with address, the place it is in. Ignored when lat and lng are given. |
| radius_m | integer | – | Radius in metres (default 300, at most 2000). |
| type | string | – | Property type as the source names it, e.g. "Appartement" or "Maison" in France. |
No output schema declared.
No examples provided.
sales_at_address Sales at an address ~192
Every recorded sale at a street address (date, price, floor area, price per m², rooms, type), newest first, and a summary of its street with its latest other sales. Spellings are loose: "17 bis avenue de Saint-Mandé" finds "17 B AV DE ST MANDE". Without a number, the street's sales. When the street is not found, similar street names.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Street address, with its postcode or city unless place gives it (e.g. "17 rue Gambey, 75011 Paris"). |
| limit | integer | – | Sales returned (default 50, at most 200). |
| place | string | – | City or postcode the address is in, when the address does not say. |
| type | string | – | Property type as the source names it, e.g. "Appartement" or "Maison" in France. |
No output schema declared.
No examples provided.
sea_views Homes with a sea view (France) ~351
The sale addresses around a place whose sun goes down (or comes up) into the sea, month by month, with how far the shore is and their latest sale. Worked out from OpenStreetMap for France's sale addresses within 300 m of the coast: the sun's direction must reach the shore past no building but the home's own, no wood, no dune but a narrow one at the door, no cliff upwards, then cross open water. A ground-level estimate: floors, trees and relief are not known. An address missing here may still see the sea from upstairs; say so rather than that it has no view. The same view shows as sea_view on the sales of sales_at_address, recent_sales and appraise_listing.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address with its postcode or city (e.g. "17 rue Gambey, 75011 Paris"), located where its sales were recorded (else its street's). Ignored when lat and lng are given. |
| lat | number | – | Latitude (WGS84). |
| limit | integer | – | Addresses returned, nearest first (default 25, at most 100). |
| lng | number | – | Longitude (WGS84). |
| place | string | – | City, city start or postcode (e.g. "Carnac", "Paris 11e", "75011"); with address, the place it is in. Ignored when lat and lng are given. |
| radius_m | integer | – | Radius in metres (default 1000, at most 5000). |
| sun | string | – | Only addresses that see the sun set (sunset) or rise (sunrise) into the sea; default any. |
No output schema declared.
No examples provided.
street_prices Prices street by street (France) ~292
The streets around a place with their recorded sales (DVF) and median price per m² over the last 5 years, the most expensive first, or ranked by how their median moved: the latest 24 months against the 24 before (falling or rising first; only streets with at least 8 sales with a floor area in each period have a change). Each street with 5 sales or more has a page on the site (url).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address with its postcode or city (e.g. "17 rue Gambey, 75011 Paris"), located where its sales were recorded (else its street's). Ignored when lat and lng are given. |
| lat | number | – | Latitude (WGS84). |
| limit | integer | – | Streets returned (default 25, at most 100). |
| lng | number | – | Longitude (WGS84). |
| order | string | – | price_desc (default), price_asc, falling (largest fall first), rising, or sales (the most sold first). |
| place | string | – | City, city start or postcode (e.g. "Carnac", "Paris 11e", "75011"); with address, the place it is in. Ignored when lat and lng are given. |
| radius_m | integer | – | Radius in metres (default 1000, at most 3000). |
No output schema declared.
No examples provided.
How do I install the CaLesVaut MCP server?
CaLesVaut is a hosted endpoint at https://calesvaut.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 · calesvaut.fr
claude mcp add --transport http fr-calesvaut-calesvaut 'https://calesvaut.fr/mcp'
What is the CaLesVaut MCP server?
CaLesVaut is an MCP server listed in the public MCP registry as fr.calesvaut/calesvaut. Is this listing too expensive? French property sales (DVF), crime, rents, risks, schools. This page covers its hosted endpoint (https://calesvaut.fr/mcp).
Is the CaLesVaut MCP server safe to use?
CaLesVaut scores 68 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 CaLesVaut MCP server expose?
CaLesVaut exposes 10 tools: find_place, property_prices, sales_at_address, recent_sales, crime_stats, and 5 more. Their descriptions and schemas cost roughly 2,796 tokens of context every time the server is loaded.
Does the CaLesVaut MCP server require authentication?
No. We connected to CaLesVaut without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CaLesVaut MCP server still maintained?
CaLesVaut is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.