Zillow Leads Property Data MCP server
io.github.kmatata/zillow-leads-property-data·v1.0.8MCP server for the zillow-leads-property-data actor: Zillow leads with agent contacts and history.
0 stars
Reviews
Write oneNobody has reviewed Zillow Leads Property Data yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Zillow Leads Property Data tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 69 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Zillow Leads Property Data compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 63/100
- higher than 19% of 4,460 AI and agents servers
Install Zillow Leads Property Data in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Zillow Leads Property Data repository's README, as published. We do not edit it. Read it on GitHub
zillow-leads-property-data
Code samples, a sample dataset, and a full workflow notebook for the Zillow Leads & Property Data Apify actor.
The actor pulls Zillow listings enriched with agent/broker contact info, full price-history timelines, 20yr+ tax history, foreclosure/distress flags, schools, and the resoFacts long tail (heating/cooling/construction). Pay-per-event pricing, no subscription: $0.70 per 1,000 bare rows, $1.20 per 1,000 enriched rows.
- Actor: https://apify.com/germane_binoculars/zillow-leads-property-data
- Architecture writeup: Predictable web scraping with web extensions — why this actor runs on a real browser session instead of a proxy farm, and what that buys you against Zillow's PerimeterX + AWS WAF.
Try it in 30 seconds, no signup beyond an Apify account
The actor's catalog mode returns a cached, already-enriched snapshot instantly, no bounding box, no wait:
{ "mode": "catalog", "metro": "Chicago" }Run it from the Apify Console or via apify-client (see examples/ below).
What's in this repo
Field reference
Two depths, listings (bare) and enriched (the default):
- listings: address, price, beds/baths, status, lot/living area, listing-type flags — whatever Zillow's own search API returns, no detail-page fetch involved. See sample_listings.csv for the shape (a subset of the columns shown there — the sample above is enriched-depth, listings-depth rows omit everything past the bare fields).
- enriched (default): everything in listings, plus agent/broker contact (name, phone, email, brokerage, MLS attribution), full price-history and 20yr+ tax-history timelines, foreclosure/distress signals, assigned + nearby schools, HOA fees, and the resoFacts long tail (heating/cooling/parking/construction).
Full field list, pricing table, and every input mode (catalog / customsearch / recentactivity) are documented on the actor's own README.
Dedup across repeat orders
Every delivery writes a DEDUPUPDATE record to the run's key-value store: the union of the zpids and MLS IDs you already had plus everything just shipped. Feed those two arrays back into your next order's dedupZpids/dedupMlsIds fields and you're never charged for the same row twice. See notebook/zillowleads_workflow.ipynb for a worked example.
Use it from an AI agent (MCP)
This actor is callable as a tool via Apify's hosted MCP server (https://mcp.apify.com) or the local @apify/actors-mcp-server, no manual input-form filling required — catalog mode (the default) is a good agent smoke test since it returns cached rows in seconds with no polling loop needed. See the actor's own README for the full agent-facing input schema and the fire/poll/fetch pattern for a live-collection order.
Questions / issues
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-11-01downgradeB → Cscore 63
Zillow Leads Property Data: common questions
- Is Zillow Leads Property Data MCP server safe?
- With care: it is graded C, so read the findings first (63/100). Read the Zillow Leads Property Data safety report
- Does Zillow Leads Property Data need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Zillow Leads Property Data maintained?
- The last commit was 73 days ago (2026-08-23). The latest release is v1.0.8.