Casafari Area Insights
Server Details
Property price trends and market stats by area. Sign up free at platform.casafari.com.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 43.6% over 18 days
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- ChatGPT
- –
- Claude
- Casafari Area Insights
TDQS
Scored across 9 tools
Each tool has a well-defined analytical output (bedrooms, price bands, heatmap, time series, operations), and the detailed descriptions clarify parameter and location semantics. The only real overlap is that both get_price_distribution and get_time_on_market_distribution group listings by asking-price bands, which could cause occasional misselection, and time_series_data versus time_series_operations requires reading descriptions to distinguish raw series from computed metrics.
All names are snake_case and the analytics tools consistently use the area-insights_get_<metric> pattern. Minor deviations are the two unprefixed tools (account_status, locations_search) and their noun-first phrasing, but overall the convention is predictable.
Nine tools is well-scoped for an area-insights server: two free utility tools, one required location resolver, and six complementary analytics endpoints. Each tool earns its place with no obvious redundancy.
The surface covers the full analytics lifecycle: location resolution, several distribution views, heatmap, raw time series and derived operations, plus account/date utilities. Gaps are minor, such as no dedicated listing-level or comparison-across-areas tool, but core market-analysis workflows are covered.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
6 tool updates
- Changed
area-insights_get_bedrooms_distribution2 fields changed- changed
Input schema / properties / request_data / properties / conditions / descriptionPrevious value: -"Property conditions, as returned by the [GET /api/v1/references/conditions](/#operation/<conditions>) endpoint."New value: +"Property conditions: one or more of used, ruin, very-good, new and other." - changed
Input schema / properties / request_data / properties / custom_location_boundary / properties / circle / properties / distance / descriptionPrevious value: -"Maximum distance in meters from the requested `target_point` to the properties."New value: +"Circle radius in metres (not kilometres) from `target_point`: 50 to 50,000."
- Changed
area-insights_get_heatmap1 field changed- changed
Input schema / properties / request_data / properties / conditions / descriptionPrevious value: -"Property conditions, as returned by the [GET /api/v1/references/conditions](/#operation/<conditions>) endpoint."New value: +"Property conditions: one or more of used, ruin, very-good, new and other."
- Changed
area-insights_get_price_distribution2 fields changed- changed
Input schema / properties / request_data / properties / conditions / descriptionPrevious value: -"Property conditions, as returned by the [GET /api/v1/references/conditions](/#operation/<conditions>) endpoint."New value: +"Property conditions: one or more of used, ruin, very-good, new and other." - changed
Input schema / properties / request_data / properties / custom_location_boundary / properties / circle / properties / distance / descriptionPrevious value: -"Maximum distance in meters from the requested `target_point` to the properties."New value: +"Circle radius in metres (not kilometres) from `target_point`: 50 to 50,000."
- Changed
area-insights_get_time_on_market_distribution2 fields changed- changed
Input schema / properties / request_data / properties / conditions / descriptionPrevious value: -"Property conditions, as returned by the [GET /api/v1/references/conditions](/#operation/<conditions>) endpoint."New value: +"Property conditions: one or more of used, ruin, very-good, new and other." - changed
Input schema / properties / request_data / properties / custom_location_boundary / properties / circle / properties / distance / descriptionPrevious value: -"Maximum distance in meters from the requested `target_point` to the properties."New value: +"Circle radius in metres (not kilometres) from `target_point`: 50 to 50,000."
- Changed
area-insights_get_time_series_data4 fields changed- changed
Input schema / properties / request_data / descriptionPrevious value: -"One analytical segment defining a specific filter or location boundary.\nAlias (name) is generated automatically on the server based on the location definition."New value: +"One segment: the location boundary, the figure, the dates and the filters. `alias` is required." - changed
Input schema / properties / request_data / properties / alias / descriptionPrevious value: -"Alias (name) of the segment that was analyzed."New value: +"Required: any short label you choose for this segment, such as the place name. It is echoed back in the answer." - changed
Input schema / properties / request_data / properties / conditions / descriptionPrevious value: -"Property conditions, as returned by the [GET /api/v1/references/conditions](/#operation/<conditions>) endpoint."New value: +"Property conditions: one or more of used, ruin, very-good, new and other." - changed
Input schema / properties / request_data / properties / custom_location_boundary / properties / circle / properties / distance / descriptionPrevious value: -"Maximum distance in meters from the requested `target_point` to the properties."New value: +"Circle radius in metres (not kilometres) from `target_point`: 50 to 50,000."
- Changed
area-insights_get_time_series_operations5 fields changed- changed
Input schema / properties / request_data / descriptionPrevious value: -"Schema for MCP time-series analytical requests.\n\n### Concept\nThis schema defines *what* to analyze (via `filter`), *where* to analyze (via `segment`),\nand *which operations* to compute (via `operations`).\n\n- The `filter` contains **shared analytical parameters** defining the general query context.\n- The `segment` represents a **specific analytical subset** (e.g., a district, city, or region),\n which inherits all values from `filter` but can override a few (e.g., location boundary).\n\nThis logic ensures a consistent analytical context while allowing\na single location-specific override — suitable for focused analytical requests\nwhere only one boundary or subset is being analyzed."New value: +"What to compute (`operations`) over which data (`segment`). Everything that defines the data goes in `segment`: location boundary, `data_point`, `date_interval`, dates, property type and filters. There is no separate `filter`." - changed
Input schema / properties / request_data / properties / segment / descriptionPrevious value: -"Analytical segment representing a boundary or subset of data. Inherits all fields from `filter` but may redefine location-specific ones (such as `custom_location_boundary` or `alias`)."New value: +"Everything that defines the data: location boundary, `data_point`, `date_interval`, `date_range`, `type_group`, `business_type` and filters. `alias` is required." - changed
Input schema / properties / request_data / properties / segment / properties / alias / descriptionPrevious value: -"Alias (name) of the segment that was analyzed."New value: +"Required: any short label you choose for this segment, such as the place name. It is echoed back in the answer." - changed
Input schema / properties / request_data / properties / segment / properties / conditions / descriptionPrevious value: -"Property conditions, as returned by the [GET /api/v1/references/conditions](/#operation/<conditions>) endpoint."New value: +"Property conditions: one or more of used, ruin, very-good, new and other." - changed
Input schema / properties / request_data / properties / segment / properties / custom_location_boundary / properties / circle / properties / distance / descriptionPrevious value: -"Maximum distance in meters from the requested `target_point` to the properties."New value: +"Circle radius in metres (not kilometres) from `target_point`: 50 to 50,000."
1 tool update
- Changed
locations_search2 fields changed- changed
Input schema / properties / country / descriptionPrevious value: -"ISO 3166-1 alpha-2 country code to restrict the search to."New value: +"ISO 3166-1 alpha-2 country code to restrict the search to. Pass it when you know it; with postcode it must be ES, FR or PT." - changed
Input schema / properties / postcode / descriptionPrevious value: -"Find the places a postcode covers, smallest area first (28019, 1950-102). One postcode matches several places. Postcode coverage: Spain fully, France partly, Portugal only parts of Lisbon; other countries are not covered."New value: +"Find the places a postcode covers, smallest area first (28019, 1950-102). One postcode matches several places. Postcodes: Spain, France (partly) and Portugal (parts of Lisbon) only; other countries have none, and country with postcode for one answers 400. Pass `country` when you know it."
2 tool updates
- Changed
area-insights_get_price_distribution3 fields changed- removed
Output schema / properties / result / items / properties / is_mean / descriptionRemoved value: -"Indicates whether the mean value is within this distribution unit." - removed
Output schema / properties / result / items / properties / lower_bound / descriptionRemoved value: -"The lower price bound of the distribution unit." - removed
Output schema / properties / result / items / properties / upper_bound / descriptionRemoved value: -"The upper price bound of the distribution unit."
- Changed
area-insights_get_time_on_market_distribution2 fields changed- removed
Output schema / properties / result / items / properties / lower_bound / descriptionRemoved value: -"The lower price bound of the distribution unit." - removed
Output schema / properties / result / items / properties / upper_bound / descriptionRemoved value: -"The upper price bound of the distribution unit."
9 tool updates
- First observed
account_status - First observed
area-insights_get_bedrooms_distribution - First observed
area-insights_get_current_datetime - First observed
area-insights_get_heatmap - First observed
area-insights_get_price_distribution - First observed
area-insights_get_time_on_market_distribution - First observed
area-insights_get_time_series_data - First observed
area-insights_get_time_series_operations - First observed
locations_search
Publisher details
- Operator
- Casafari · Publisher source
- Operator website
- https://www.casafari.com · Publisher source
- Vendor relationship
- First-party · Publisher source
- Trust center
- Not available
- Restrictions
- Requires a Casafari API and MCP Platform account: self-serve at https://platform.casafari.com/console/, Free plan with no card. Calls use units from the account's balance (place lookups and account_status are free); more units are bought in the console. Sign-in is OAuth 2.1 in the browser, with no custom OAuth app or API key needed. AgentGraph AI covers Germany and is for verified businesses only; Claro AI covers commercial premises in Spain and Germany and allows 4 searches on the Free plan. Data covers European property markets; coverage varies by country. · Publisher source
Related MCP Connectors
Comparables and valuations for European homes. Sign up free at platform.casafari.com.
Agency and agent analysis, verified businesses only. Sign up at platform.casafari.com.
Place names to Casafari location ids, free. Sign up at platform.casafari.com.
Property listings in Portugal: search, market stats, comparables, neighbourhoods.
Related MCP Servers
- AlicenseAqualityCmaintenanceUK property area intelligence: validated trajectory scores, gentrification early-warning and area screening for 2,292 England & Wales postcode districts, from 30+ government data sources.7MIT
- AlicenseAqualityDmaintenanceSearch comparable property sales across 16 global markets with 43M+ government-sourced transactions. Tools: search comps by location, get area statistics and trends, list available markets. Covers UK, France, Singapore, NYC, Chicago, Dubai, and 10 more cities.34MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to query real Polish real-estate transaction prices for flats, houses, and building plots from the official notarial registry. It returns median price per square meter, price ranges, room breakdowns, market type, yearly trends, and recent sales within a radius of any Polish address, street, town, or coordinates.4569 npmMIT
- AlicenseNot gradedqualityCmaintenanceAccess 17M+ geocoded French property transactions (DVF), 22M+ DPE energy ratings, and 20M+ building records via MCP or REST API. Search transactions, market stats, comparables, price trends, rental yield, flip detection, and more.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.