NestDaddy

Houski Property Data

io.github.Houski/property-data · v0.1.16

Property data for 220M+ homes in North America, Europe and South Korea: search, stats and values.

MCP Score How we grade

C
71 / 100

From what our daily checks can see without credentials, last checked 22 Nov 2026.

Reliability
Answered 6 of 6 daily checks.
30 / 30
Speed
Typical response 544 ms.
8 / 20
Tool docs
11 of 12 tools have a full description; 103 of 103 inputs have a description.
24 / 25
Stability
16 tool rewrites in 30 days (description or inputs changed, or removed).
0 / 15
Listing
Missing an icon.
9 / 10

How to raise the grade

  • Answer initialize faster: under 150 ms earns full Speed points (yours: 544 ms).
  • Give every tool a description of at least 80 characters: what it does and when to use it.
  • Change tool descriptions and inputs rarely, and with a new version: agents trust stable tools.
  • Add an icon to your server.json in the official MCP registry.
Fixed something? Run the same check now. The grade updates at once.

Connect Remote server

Terminal
claude mcp add --transport http property-data https://www.houski.ca/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "property-data": {
      "url": "https://www.houski.ca/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "property-data": {
      "type": "http",
      "url": "https://www.houski.ca/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://www.houski.ca/mcp

Tools 12 found in our last check

  • aggregate_endpoint

    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 b…

  • auth_endpoint

    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.

  • avm_endpoint

    No description provided.

  • field_detail

    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 i…

  • field_list

    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, accep…

  • geocoding_endpoint

    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…

  • location_endpoint

    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_a…

  • map_endpoint

    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…

  • predict_endpoint

    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 te…

  • properties_endpoint

    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…

  • search_api_documentation

    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.

  • search_endpoint

    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.

Tool changes seen by our daily check

  • 19 Nov 2026

    Inputs changed: aggregate_endpoint, location_endpoint, properties_endpoint. Description changed: aggregate_endpoint, geocoding_endpoint, location_endpoint, map_endpoint, properties_endpoint.

  • 18 Nov 2026

    Description changed: aggregate_endpoint, auth_endpoint, field_detail, geocoding_endpoint, map_endpoint, predict_endpoint, properties_endpoint, search_endpoint.

Renames and new inputs are usually routine. A changed description changes what your agent is told the tool does, and can carry new instructions: review it before you rely on the tool again.

Details

Endpointhttps://www.houski.ca/mcp (Streamable HTTP)
First published17 Nov 2026
Last updated17 Nov 2026
Registry nameio.github.Houski/property-data

More search and web servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.