Houski Property Data
REMOTE · WWW.HOUSKI.CA
Property data for 220M+ homes in North America, Europe and South Korea: search, stats and values.
Available components
Last scanned (23 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability56
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 6598 tokens (~549/item across 12 items; 12 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 92% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “aggregate_endpoint” rewrote its description, which is the text the model reads security
- Tool “geocoding_endpoint” rewrote its description, which is the text the model reads security
- Tool “location_endpoint” rewrote its description, which is the text the model reads security
- Tool “map_endpoint” rewrote its description, which is the text the model reads security
- Tool “properties_endpoint” rewrote its description, which is the text the model reads security
- Schema quality: 497 → 549 ▼ functional
- “aggregate_endpoint” reworded the description of “country_abbreviation” cosmetic
- “location_endpoint” reworded the description of “filters” cosmetic
- “properties_endpoint” reworded the description of “country_abbreviation” cosmetic
- 19 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “aggregate_endpoint” rewrote its description, which is the text the model reads security
- Tool “auth_endpoint” rewrote its description, which is the text the model reads security
- Tool “field_detail” rewrote its description, which is the text the model reads security
- Tool “geocoding_endpoint” rewrote its description, which is the text the model reads security
- Tool “map_endpoint” rewrote its description, which is the text the model reads security
- Tool “predict_endpoint” rewrote its description, which is the text the model reads security
- Tool “properties_endpoint” rewrote its description, which is the text the model reads security
- Tool “search_endpoint” rewrote its description, which is the text the model reads security
- 18 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “auth_endpoint” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 63
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 21 Nov 2026 · Probed https://www.houski.ca/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.houski.ca | CN=YE2,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5b1f36a86f657488a03bcfb50fd8b110a52 |
| SANs: api.houski.ca, houski.ca, mon.houski.ca, www.houski.ca | ||||||
| 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 www.houski.ca. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ca. | DS published | 26384 | 13 | Verified |
| houski.ca. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.houski.ca/mcp | Verified | 200 | |
| http (plaintext) | http://www.houski.ca/mcp | HTTPS enforced | 301 | https://www.houski.ca/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 →
aggregate_endpoint ~819
Get statistical aggregations for market analysis. Billed per aggregation returned. Aggregations: count, sum, mean, median, mode, min, max, quantile-10, quantile-25, quantile-40, quantile-60, quantile-75, quantile-80, quantile-85, quantile-90, quantile-95, quantile-99. Text and boolean fields only support count and mode, and only fields field_detail marks aggregatable are accepted. count counts the properties that hold a value for the field, so a count per country measures how well a field is covered there. Ask for several statistics in one call with the aggregations array instead of one call each. Every statistic must name exactly one country, with country_abbreviation, or something narrower inside one country, on the call or on its own entry, and different entries may name different countries. A bounding box or a polygon alone is not enough, and a call with a statistic that names no place, or more than one country, is refused with a 400.
| Name | Type | Req | Description |
|---|---|---|---|
| aggregation | string|null | – | Aggregation type for the single-statistic form: count, sum, mean, median, mode, min, max, quantile-10, quantile-25, quantile-40, quantile-60, quantile-75, quantile-80, quantile-85, quantile-90, quant… |
| aggregations | array|null | – | Several statistics in one request, instead of one call each. Each entry gets its own field and aggregation, and inherits this call's location and filters unless it sets its own. Do not also set field. |
| api_key | string | yes | API key for authentication |
| bbox_ne_lat | number|null | – | Bounding box northeast latitude. All four bbox values are required together. |
| bbox_ne_lng | number|null | – | Bounding box northeast longitude. All four bbox values are required together. |
| bbox_sw_lat | number|null | – | Bounding box southwest latitude. All four bbox values are required together. |
| bbox_sw_lng | number|null | – | Bounding box southwest longitude. All four bbox values are required together. |
| city | string|null | – | City name. Requires country_abbreviation and province_abbreviation, and the request is refused with a 400 error if either is missing. |
| community | string|null | – | Community/neighborhood name. Requires country_abbreviation, province_abbreviation and city. |
| country_abbreviation | string|null | – | Country abbreviation as location_endpoint returns it (for example "CA"). Any letter case is accepted. Every statistic needs a place, so pass it here or on each entry of aggregations. |
| exclude | string|null | – | Source classes to leave out of the aggregation, comma separated: "inferred" leaves out every value Houski worked out, and "inferred,observed" keeps only values from a linked public record. Applies to… |
| field | string|null | – | Field to aggregate for a single statistic. Use field_list to discover available fields. Leave this out when using aggregations. |
| filters | array|null | – | Filters array. Format: "field_operator=value", with the value as plain text and not URL encoded. Use search_api_documentation for reference. |
| polygon | string|null | – | Polygon coordinates "lat_lng,lat_lng,lat_lng", latitude and longitude joined by an underscore. Maximum 100 points, simplify a shape that has more. |
| price_quote | boolean|null | – | Return the cost of this request without billing it or returning data |
| province_abbreviation | string|null | – | Province, state or region abbreviation as location_endpoint returns it (for example "AB"). Requires country_abbreviation. |
No output schema declared.
No examples provided.
auth_endpoint ~73
Check that an API key exists and is enabled. Does not bill per call. Returns api_key_authorized boolean. It does not check the key's maximum monthly spend or the unlimited plan's daily allowance, so another tool can still refuse a key that passes here.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API key to validate |
No output schema declared.
No examples provided.
avm_endpoint ~102
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API key for authentication |
| overrides | – | – | What-if changes to the property before valuing it, for scenario testing (a finished basement, an extra bathroom). Anything left out keeps the property's real value. |
| price_quote | boolean|null | – | Return the cost of this request without billing it or returning data |
| property_id | string | yes | Property ID, one per call. Every call is billed at the price in this tool's description. |
No output schema declared.
No examples provided.
field_detail ~94
Describe fields by name: type, accepted filter values, its source column if it has one, filtered, aggregated or predicted, which expand set it belongs to, its price per home returned, and its full description. Does not bill per call. Coverage differs by country, and the server instructions say how to check it cheaply with location_endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | yes | Comma-separated list of field names to get details for |
No output schema declared.
No examples provided.
field_list ~123
List the name of every public property data field, one per line. Does not bill per call. Pass filter to list only the names that contain a piece of text, for example score_, demographic_, assessment, permit or expand_listing. Follow with field_detail for each field's type, accepted filter values, aggregation support, expand set and price per value returned.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string|null | – | Optional text to match inside field names, for example "score_", "demographic_", "assessment", "permit" or "expand_listing". Leave it out to list every field. |
No output schema declared.
No examples provided.
geocoding_endpoint ~484
Find properties near coordinates (reverse geocoding). Billed per field, per home returned. Required: latitude, longitude. Optional: radius (km), shape (circle/square). This endpoint has no country, province, city, community or address parameters. To narrow by place, put filters such as country_abbreviation_eq=CA or city_eq=Calgary in filters, spelled exactly as location_endpoint returns them, letter case included. With no such filter the point and radius may cover no more homes than one country holds, and a filter that names more than one country is refused with a 400. For active or marketable properties, add has_expand_listings_eq=true to filters, which is far cheaper than expanding listings just to filter on their presence.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API key for authentication |
| exclude | string|null | – | Source classes to leave out, comma separated, such as "inferred" or "inferred,observed". Checks the selected fields that have a source column, keeps a property when one of them keeps its value, and e… |
| expand | string|null | – | Comma-separated. Values: "listings", "listings_rent", "permits", "assessments". Each attached record is a flat charge. To filter to properties that HAVE a set, use the has_expand_* boolean filters in… |
| filter_expand_match | string|null | – | "any" or "all". Use only when filtering on values inside expanded records. |
| filters | array|null | – | Filters array. Format: "field_operator=value", with the value as plain text and not URL encoded. Use search_api_documentation for reference. |
| latitude | number | yes | Center latitude (e.g., 51.0447) |
| longitude | number | yes | Center longitude (e.g., -114.0719) |
| page | integer|null | – | Page number for pagination |
| price_quote | boolean|null | – | Return the cost of this request without billing it or returning data |
| radius | number|null | – | Search radius in kilometers |
| results_per_page | integer|null | – | Results per page |
| select | string|null | – | Comma-separated fields to return, or "all" |
| shape | string|null | – | Search shape: "circle" (default) or "square" |
No output schema declared.
No examples provided.
location_endpoint ~640
Get the places Houski holds property data for, as a hierarchy of countries, provinces (or states or regions), cities and communities, with links and slugs. Billed per location returned, a small fraction of a cent each. This is the source of every country_abbreviation, province_abbreviation, city and community the other tools take. There is no paging and every matching location comes back, so scope every call: resolution=country and resolution=province are small, while resolution=city or community with no country_abbreviation and province_abbreviation returns every city of every country in one very large response. Naming a level requires naming its parents, and the endpoint returns a 400 saying so if you skip one. filters keeps only the places where at least one property matches, which is the cheapest way to check coverage. A call with filters must name exactly one country, with country_abbreviation, or something narrower inside one country, or it is refused with a 400: country_abbreviation=ca with resolution=country and filters=["parcel_number_regex=."] returns Canada only when it holds parcel numbers. Several countries take one call each. A call with no filters needs no place.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API key for authentication |
| city | string|null | – | City name. Requires country_abbreviation and province_abbreviation, and the endpoint returns a 400 if either is missing. |
| community | string|null | – | Community/neighborhood name. Requires country_abbreviation, province_abbreviation and city, and the endpoint returns a 400 if any is missing. |
| country_abbreviation | string|null | – | Country abbreviation (for example "CA"). Pass it with province_abbreviation on anything finer than resolution=province, or the response covers the whole country. |
| filters | array|null | – | Filters that keep only the locations holding at least one matching property, in the "field_operator=value" form. "<field>_regex=." keeps the places where some property has a value for that field, whi… |
| flat | boolean|null | – | Return flat format instead of nested (default: false). Flat is roughly four times larger, because each row repeats the whole country and province block instead of nesting under it, and carries a null… |
| price_quote | boolean|null | – | Return the cost of this request without billing it or returning data |
| province_abbreviation | string|null | – | Province, state or region abbreviation (for example "AB"). Requires country_abbreviation. The two together keep a resolution=city call to one province instead of every city of the country. |
| resolution | string|null | – | Depth: "country", "province", "city", or "community" (default). This is the main size lever. With no country_abbreviation and province_abbreviation, stay on "country" or "province". |
No output schema declared.
No examples provided.
map_endpoint ~689
Get map data: pins, clusters, or heatmaps. Billed per cluster or heatmap cell returned, or per field, per home returned for pins. Scope it with all four bbox coordinates or a polygon. With no place filter, the box or polygon may cover no more homes than one country holds. A call with neither must carry a filter on one country, such as country_abbreviation_eq=CA, or on a narrower place inside one country. A call that names no place, covers more than one country's homes, or filters on more than one country is refused with a 400, so several countries take one call each. A heatmap needs all four bbox coordinates, and a heatmap scoped by a polygon alone is refused. Modes: cluster=true, heatmap=true. There is no cap on how many properties a request may match, so set abort_over yourself if you want a request to give up past a certain number. For maps of active inventory, add has_expand_listings_eq=true to filters so listing-less parcels don't pad results.
| Name | Type | Req | Description |
|---|---|---|---|
| abort_over | integer|null | – | Abort if results exceed this count (cost protection) |
| api_key | string | yes | API key for authentication |
| bbox_ne_lat | number|null | – | Bounding box northeast latitude |
| bbox_ne_lng | number|null | – | Bounding box northeast longitude |
| bbox_sw_lat | number|null | – | Bounding box southwest latitude |
| bbox_sw_lng | number|null | – | Bounding box southwest longitude |
| cluster | boolean|null | – | Force clustering (default: false) |
| cluster_over | integer|null | – | Auto-cluster when results exceed this count |
| exclude | string|null | – | Source classes to leave out, comma separated, such as "inferred" or "inferred,observed". Checks the selected fields that have a source column and the heatmap field, and a heatmap of a field uses only… |
| filters | array|null | – | Filters array. Format: "field_operator=value", with the value as plain text and not URL encoded. Use search_api_documentation for reference. |
| heatmap | boolean|null | – | Enable heatmap mode (default: false) |
| heatmap_aggregation_field | string|null | – | Field for heatmap intensity (e.g., "estimate_list_price"). Without this, uses density. |
| heatmap_aggregation_invert_intensity | boolean|null | – | Invert intensity (true = lower values show higher intensity, good for affordability) |
| heatmap_aggregation_type | string|null | – | Heatmap aggregation: "mean", "median", or "sum" |
| heatmap_cell_limit | integer|null | – | Max heatmap cells (default: 1000, max: 10000) |
| page | integer|null | – | Page number for pagination, pins only (default: 1) |
| polygon | string|null | – | Polygon coordinates "lat_lng,lat_lng,lat_lng", an alternative to bbox for pins and clusters. A heatmap needs all four bbox values and is refused with a polygon alone. |
| price_quote | boolean|null | – | Return the cost of this request without billing it or returning data |
| results_per_page | integer|null | – | Results per page (for pins only) |
| select | string|null | – | Comma-separated fields to return |
No output schema declared.
No examples provided.
predict_endpoint ~274
Predict property values over time. Billed per predicted field, once for each date and each property. Required: property_id, start_date, fields. Find the property_id first with search_endpoint or properties_endpoint. Supports batch requests and parameter overrides for scenario testing.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API key for authentication |
| fields | string | yes | Fields to predict: "estimate_sale_price", "estimate_list_price", "estimate_rent_monthly" |
| last | integer|null | – | Periods before start_date to include. A range reaching before 2021-01-01 is refused |
| next | integer|null | – | Periods after start_date to include. A range reaching past today is refused, because the models do not forecast |
| overrides | – | – | What-if changes to the property before predicting, for scenario testing. Anything left out keeps the property's real value. |
| period | string|null | – | Time granularity: "day", "week", "month" (default), "year" |
| price_quote | boolean|null | – | Return the cost of this request without billing it or returning data |
| property_id | string | yes | Property ID(s), comma-separated for batch requests |
| start_date | string | yes | Reference date in YYYY-MM-DD format, from 2021-01-01 to today |
No output schema declared.
No examples provided.
properties_endpoint ~1,313
Retrieve property data (hundreds of fields) with filtering, sorting, and expansion. Billed per field, per home returned: each selected field's price for each home that has a value for it, so a field with no value for a home is not billed. Always set select= to limit fields. For comparables, 'good' properties, or active inventory, add has_expand_listings_eq=true to filters: a fast indexed boolean filter that excludes the long tail of listing-less parcels (use has_expand_listings_rent_eq=true for rentals). Use expand=listings,permits,assessments only when you actually need the related records, not just to filter on their existence (has_expand_permits_eq=true and has_expand_assessments_eq=true cover that). Take place names and abbreviations from location_endpoint. Every call must name exactly one country, with country_abbreviation, or something narrower inside one country, such as a province, a city, or a property_id_eq or property_id_in filter. A bounding box or a polygon alone is not enough, and a call that names no place, or more than one country, is refused with a 400. Several countries take one call each. When select names a field with a source column, pass exclude=inferred unless the user wants inferred values too or the call looks up one named property. Set price_quote=true first when the row count is unknown. See search_api_documentation for full filter syntax.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string|null | – | Address for a single property lookup. Letter case and punctuation do not matter, but abbreviations are not rewritten, so write road types in full as the address field does ("Place", not "Pl"). Requir… |
| api_key | string | yes | API key for authentication |
| bbox_ne_lat | number|null | – | Bounding box northeast latitude. All four bbox values are required together. |
| bbox_ne_lng | number|null | – | Bounding box northeast longitude. All four bbox values are required together. |
| bbox_sw_lat | number|null | – | Bounding box southwest latitude. All four bbox values are required together. |
| bbox_sw_lng | number|null | – | Bounding box southwest longitude. All four bbox values are required together. |
| city | string|null | – | City name as location_endpoint returns it (for example "Calgary"). Letter case, accents and punctuation do not matter. Requires country_abbreviation and province_abbreviation, and the request is refu… |
| community | string|null | – | Community/neighborhood name. Letter case, accents and punctuation do not matter. Requires country_abbreviation, province_abbreviation and city, and the request is refused with a 400 error if any is m… |
| community_in | string|null | – | Several community names, comma separated. This is a plain filter on the community name, so it compares each name exactly, letter case included, and spelled as location_endpoint returns it. It needs n… |
| country_abbreviation | string|null | – | Country abbreviation as location_endpoint returns it (for example "CA", "US", "GB" or "KR"). Any letter case is accepted. Pass it on every call that does not name a narrower place with a filter such… |
| exclude | string|null | – | Source classes to leave out, comma separated: "inferred" leaves out every value Houski worked out, and "inferred,observed" keeps only values from a linked public record. Checks the selected fields th… |
| expand | string|null | – | Comma-separated. Values: "listings", "listings_rent", "permits", "assessments". Each attached record is a flat charge, so only include when you need the related records themselves. To filter to prope… |
| filter_expand_match | string|null | – | "any" or "all". Use this only when filtering on values inside expanded records (for example expand_permit_content_regex). To filter on mere presence of a set, use the has_expand_* boolean filters in… |
| filters | array|null | – | Filters array. Format: "field_operator=value", with the value as plain text and not URL encoded. Operators: _eq, _neq, _gte, _lte, _gt, _lt, _in, _regex, _nregex (rows that do not match the regex). T… |
| page | integer|null | – | Page number for pagination (default: 1) |
| polygon | string|null | – | Polygon coordinates "lat_lng,lat_lng,lat_lng", latitude and longitude joined by an underscore. Maximum 100 points, simplify a shape that has more. |
| price_quote | boolean|null | – | Return the cost of this request without billing it or returning data |
| province_abbreviation | string|null | – | Province, state or region abbreviation as location_endpoint returns it (for example "AB" in Canada). Any letter case is accepted. Requires country_abbreviation. |
| results_per_page | integer|null | – | Results per page (default: 6, max: 1000) |
| select | string|null | – | Comma-separated fields to return, or "all". Use field_list to discover fields. |
| sort_by | string|null | – | Sort field. Format: "field_sort=asc" or "field_sort=desc" |
No output schema declared.
No examples provided.
search_api_documentation ~83
Access API documentation pages for filter syntax, field references, and endpoint details. Does not bill per call. Pass an unknown page to get the full list of pages back.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | yes | Documentation page to read, for example "filter", "properties" or "pricing". Pass an unknown value to get the full list of pages back in the error. |
No output schema declared.
No examples provided.
search_endpoint ~266
Find property_id using fuzzy address matching. Billed per field, per home returned. Handles typos, abbreviations, partial addresses. Pass country_abbreviation to keep every match in one country. Use returned property_id with other endpoints for detailed data.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API key for authentication |
| country_abbreviation | string|null | – | Only return matches from one country, by its country_abbreviation as location_endpoint returns it (for example "GB"). Default: every country. A query that names a province, a state, or a postal code… |
| exclude | string|null | – | Source classes to leave out, comma separated, such as "inferred" or "inferred,observed". Checks the selected fields that have a source column, keeps a match when one of them keeps its value, and empt… |
| max_results | integer|null | – | Max results (default: 10, max: 25) |
| price_quote | boolean|null | – | Return the cost of this request without billing it or returning data |
| query | string | yes | Address query. Handles partial addresses, building names, typos. Include city for better accuracy. |
| select | string|null | – | Comma-separated fields to return |
No output schema declared.
No examples provided.
How do I install the Houski Property Data MCP server?
Houski Property Data is a hosted endpoint at https://www.houski.ca/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 · www.houski.ca
claude mcp add --transport http houski-property-data 'https://www.houski.ca/mcp'
What is the Houski Property Data MCP server?
Houski Property Data is an MCP server listed in the public MCP registry as io.github.Houski/property-data. Property data for 220M+ homes in North America, Europe and South Korea: search, stats and values. This page covers its hosted endpoint (https://www.houski.ca/mcp).
Is the Houski Property Data MCP server safe to use?
Houski Property Data scores 65 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 Houski Property Data MCP server expose?
Houski Property Data exposes 12 tools: aggregate_endpoint, auth_endpoint, avm_endpoint, field_detail, field_list, and 7 more. Their descriptions and schemas cost roughly 4,960 tokens of context every time the server is loaded.
Does the Houski Property Data MCP server require authentication?
No. We connected to Houski Property Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Houski Property Data MCP server still maintained?
Houski Property Data is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Houski Property Data MCP server?
VerifyMCP ran 12 checks on Houski Property Data, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Houski Property Data: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.