
Zillow Leads Property Data
io.github.kmatata由 GitHub 帳號 kmatata 發布v1.0.8更新於 Oct 24, 2026
MCP server for the zillow-leads-property-data actor: Zillow leads with agent contacts and history.
概覽
本機 MCP 伺服器,呼叫 Zillow Leads & Property Data 的 Apify actor,回傳含房仲聯絡資訊、價格與稅費歷史及風險標記的 Zillow 房源資料。
- 可以做什麼
- 以 catalog 模式執行 Zillow 潛在客戶 actor,快速取得某都會區已快取的充實快照。
- 以 custom_search 或 recent_activity 模式下單即時蒐集並取回房源結果。
- 取得基本欄位(地址、價格、房廳數、狀態、面積),或含房仲/仲介公司聯絡資訊、價格與 20 年以上稅費歷史、法拍訊號、學校、HOA 與 resoFacts 的充實資料。
- 在多次下單之間沿用 zpids 與 MLS ID,避免為同一筆資料重複付費。
- 適用情境
- 適合房地產潛在客戶開發與房源調查:需要助理抓取帶房仲聯絡資訊及長期價格、稅費歷史的 Zillow 房源資料,可使用快取快照或即時蒐集訂單。
- 執行需求
- 以本機 stdio 程序在使用者電腦上執行(僅桌面端)。它呼叫 Apify actor,因此需要 Apify 帳號與 Apify API 憑證,actor 依事件計費。需要連線至 Apify 與 Zillow 的網路。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Zillow Leads Property Data,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
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:
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. Seesample_listings.csvfor 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 inlistings, 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 / custom_search / recent_activity) are documented on the actor's own README.
Dedup across repeat orders
Every delivery writes a DEDUP_UPDATE 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/zillow_leads_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
This repo is documentation and samples only — it doesn't run the actor
itself. For a specific order that isn't behaving as expected, check that
run's key-value store STATUS record first (the actor writes a plain-English
reason there for any zero-row or partial result), then open an issue here or
reach out via the actor's Apify Store page.
來源:README.md,提交 01fa450
工具
0版本歷史
1- v1.0.8最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分