HouseData — Zillow data
dev.housedata/zillow · 1.0.0
Zillow data for agents: listings, records, Zestimate history, market stats. 19 tools, pay per call.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://mcp.housedata.dev/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 19 tools.
- Protocol
- 2025-06-18
- Calls itself
- housedata-zillow 1.0.0
- Handshake time
- 1255 ms
- HTTP status
- 200
The tools it lists (19, as of 7 hours ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
zillow_search_listingsListings for a place typed as on Zillow — a city (Austin, TX), a ZIP, a neighborhood or a county — for sale, for rent or recently sold. One row per listing with its zpid, address, price, beds, baths, living area, days on Zillow and Zestimate; up to 40 per page and 1,000 per search (page x pageSize). Rentals come back as buildings (resultType propertyGroup, with a buildingId) and single homes (property). Sort daysOn ascending for newest first.
zillow_autocomplete_placesThe regions Zillow knows for a partial place name — cities, ZIPs, neighborhoods, counties — each with its region id, type and centre. What a search box needs before zillow_search_listings, and the way to a regionId.
zillow_regionA place name resolved to Zillow's region — id, type, parent state and city, centre and the exact bounding rectangle search uses — or a region id described. Give location or regionId.
zillow_propertyThe record for any zpid, listed or off market — every zpid has one. Compact: the headline (status, price, Zestimate, rent Zestimate, address, coordinates, beds, baths, living area, year built, home type, lot, HOA, days on Zillow, hero photo). expand true: everything — 23 facts, price and tax history, schools with ratings, listing agent and broker, MLS, walk/transit/bike scores, nearby homes, open houses, description and the photo gallery (~17 KB).
zillow_property_factsThe facts for one home: beds, baths, living area, lot, year built, home type, parking, heating and cooling, HOA, price per square foot, and the rest of Zillow's fact sheet — with the current status and price.
zillow_price_historyEvery listing, price cut, pending, sale and delisting Zillow records for a home, newest first, with the price, the change and the source.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
dev.housedata/zillow, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 13 days ago. The registry entry · housedata.dev